command-and-conquer icon indicating copy to clipboard operation
command-and-conquer copied to clipboard

Code license is not clear

Open johnl opened this issue 13 years ago • 3 comments

I cannot find any mention of what license the code is released under and there are no copyright notices. mit license is nice, but you might consider the gpl too. Up to you of course, but it should be made clear to others!

johnl avatar Jan 23 '12 22:01 johnl

I'm going to hold off on specifying a license for a little bit to see where this project is headed.

For now, I'd say basic common sense and decency license :) ... i.e.:

Free for people to read, learn and play with. Attribute source if you're doing something different with it. (A link back to this project and my original site would be great). Don't call it your original work if all you've done is change a couple of fonts and titles. Don't do anything you wouldn't like done to your work. If you feel the need to ask about something because even you find it gray, chances are it isn't acceptable

adityaravishankar avatar Jan 24 '12 11:01 adityaravishankar

I'd urge you to choose a license, to make it clear. Without a clear license, people can't use this code for much. They can't know that you won't revoke your permission later, they can't submit patches to you (if they do, who does the patch belong to, you or them?) and if you get bored, distracted, or otherwise cannot be involved in the project any more it's status is forever uncertain!

Your terms 1, 2 and 2 are covered by most licenses (though most don't let you enforce a link). term 4 is a tricky one - most licenses let you do nearly anything with the code.

I'd suggest the AGPL v3 as a first step in your case - it'll mean that anyone making any changes to your code has to re-release it under the AGPL. People could resell your code, but they'd always have to provide the source.

http://en.wikipedia.org/wiki/Affero_General_Public_License

It does mean that you cannot revoke the permission at a later stage though - so bear that in mind (you can of course re-release it under a different license at any time, as you own the copyright!).

I suspect you don't own the copyrights to the the graphics and sounds, so you'll have to exclude those from the license of course :)

Sorry if I sound preachy! I just know that this kind of thing can get in a bit of a mess further down the line - better to clarify it asap!

johnl avatar Jan 24 '12 12:01 johnl

The problems is I need to take the time to read up on the licenses and the details before I decide.

I wanted to share the code so people learned from it, and possibly gave me their feedback, but I haven't had a chance to think about how I want to handle things like commercial use of the code.

adityaravishankar avatar Jan 24 '12 12:01 adityaravishankar