Don't know about the legal necessity, but I'd really prefer all the licensing details to be in one place instead of spread out and duplicated all over the code because they:
* needlessly bloat the source files * add zero information except (sometimes) author names, which can be listed elsewhere for accreditation * are more easily maintained in one single LICENSE
Finding out who originally wrote what (or who contributed to what) is harder than it sounds too, how far back in Spring's development would you want to go? Some sources have even undergone so many changes that they're unrecognizably different now, should the names of everyone significantly involved in their history be listed too? Or just those of the principal author(s), if they can be traced? IMHO a CREDITS file would be better suited for that purpose anyway.
in theory, the parts of the engine that could be easyly used in other places too, could have other licences, right? for example, if someone writes support for a new map format, and wants his stuff to be LGPL. would this work?: one LICENSE/COPYRIGHT file in spring source root (GPL V2+), and additional LICENSE/COPYRIGHT files in subfolders , eg. the ones in rts/lib, or rts/Map/SM3 if needed.
i dont think we have to remove license info from individual files, but i am also not totally against it. I am pro a clearer line though, eg defining a proposed file header comment format (the part that contains licence info and author and such).
Joined: 24 Jun 2007, 07:34 Location: 50┬░ 56' N, 11┬░ 35' O
hoijui: I think all parts of the engine should be GPL (except those from lib/). GPL is nonexclusive, so if you have written some awesome map format you can include it in spring under the GPL, and publish it elsewhere under any license you want.
Placing the license in the header is what the FSF would encourage, yes. However, the inclusion of the LICENSE.txt file is sufficient denotation, according to our lawyer.
OK, so there should be no need to add license headers, and I also would prefer it in a single file.
Whichever license you plan to use, the process involves adding two elements to each source file of your program: a copyright notice (such as ÔÇ£Copyright 1999 Terry JonesÔÇØ), and a statement of copying permission, saying that the program is distributed under the terms of the GNU General Public License (or the Lesser GPL).
This, together with the idea of the header to be a thing that can easily change (eg. someone using our code, he has to use our header or parts of it and will add stuff), i came up with:
/* Copyright 2010 John Doe <email@example.com> This file is part of the Spring RTS game engine, and is licensed under the GNU GPL v2 and later. See the file README.LICENSE for details. */
As i got it, we have to include a legal person to hold the copyright, and i guess the Spring community is not one, so we have to use our individual names.
README.LICENSE currently contains GPLv2 in .txt format. i would like to move it to either gpl-2.0.txt or Documentation/gpl-2.0.txt, add the same for v3, and then only link to these to files from within README.LICENSE.
i plan to make a branch with the transition to the new header (plus other related stuff, eg. as explained in here). once the transition is done, changing the header would be simple of course, but the initial enforcement will need lots of hand tweaking: is there a header already? if yes, what info of it is still needed, ...
As most of you probably noticed, most of the change has been done now. used this header:
/* This file is part of the Spring engine (GPL v2 or later), see LICENSE.html */
in all code under rts/, with the exception of most stuff under rts/lib/. stuff under AI/Wrappers/ and AI/Interfaces will also get it, but i want to do that with the pureint branch. As AI/Skirmish/ is not really integral stuff of the engine, i guess i will not change stuff there. An alternative would be, adding the header anyway, but replacing Spring engine with eg. AAI.
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum