License?

[jpeg]

Is Cody available under a particular open source license? I have been looking for information about this on both your website and this GitHub repository but have been unable to find licensing information.

Cody is fully open source. You can copy it, read the code, modify it, use it however you want. There is no fee, licence price.

The above from your website homepage is the closest I could find as a sort of custom license, however that simply isn't good enough for my purposes. If Cody is already licensed under a particular open source license you may want to make it more obvious (such as adding it to the README.md and/or adding a license file in the root project directory) otherwise you may want to look into the common open source licenses and consider using one of them. Unfortunately a small blurb appearing solely on your website rather than in the project repository and therefore which could simply disappear at any time isn't going to be good enough for my purposes so I am forced to pass on Cody for now.

[jcoppieters]

Jason,

Could you please help me out?

What kind of licence would be the most liberal? But that would still allow people to fork the project and make changes for their own purposes.

Many thanks,

Johan Coppieters, Brugge.

Sent from my iPad.

On 13 Oct 2014, at 18:57, Jason Gassel notifications@github.com wrote:

Is Cody available under a particular open source license? I have been looking for information about this on both your website and this GitHub repository but have been unable to find licensing information.

Cody is fully open source. You can copy it, read the code, modify it, use it however you want. There is no fee, licence price. The above from your website homepage is the closest I could find as a sort of custom license, however that simply isn't good enough for my purposes. If Cody is already licensed under a particular open source license you may want to make it more obvious (such as adding it to the README.md and/or adding a license file in the root project directory) otherwise you may want to look into the common open source licenses and consider using one of them. Unfortunately a small blurb appearing solely on your website rather than in the project repository and therefore which could simply disappear at any time isn't going to be good enough for my purposes so I am forced to pass on Cody for now.

— Reply to this email directly or view it on GitHub.

[jpeg]

Depends on what you mean by liberal. But if you mean the most permissive then generally of the common open source licenses the MIT and BSD licenses would be your most likely choices. They both boil down to essentially "you can do whatever you want with this code" with some basic protections for you and your copyright.

MIT License BSD 2-Clause License BSD 3-Clause License

Comparison of common OSS licenses

You may also be interested in checking out GitHub's article on open source licensing.

[ticup]

I also suggest MIT. It's a very "liberal" license and people commonly like adopting software under it. There is a quite comprehensive guide by the git people: http://choosealicense.com/ It's is not as scary as it might sound ;)

[jcoppieters]

OK, thanks guys! I've added a LICENSE file + a mention in the README file.