Curtis L. Olson wrote: > James A. Treacy writes: > >>You should get as close to 100% of the contributors to agree as you >>can get. Flightgear needs to be prepared to remove any code written by >>someone who disagrees or who couldn't be contacted and appears later >>on. >> >>FWIW, wine did this earlier this year and they got all but a handful >>of contributors to sign off on the change. The missing had made only >>small contributions that they could easily recode if the need arose. > > > Question: for a particular source file, if a person contributed a > minor patch or tweak to compile on a new platform, does that person > now have a "full" say in the future of that source, or are they giving > their changes to the author of that file to be placed under the > license terms chosen by the primary author. > > My sense is that if it is only minor changes that were contributed by > others, the primary author should be able to maintain complete > "ownership" over the copyright and license terms of that code.
Yep. That's my opinnion also. > FWIW, this issue arrises when we consider moving code from FlightGear > into SimGear. SimGear code is LGPL'd and FlightGear code is GPL'd so > a license change would be required. Hoever, if we attacked this piece > by piece, subsystem by subsytem, it would likely be doable. What's your reason for wanting to change the license anyway? Erik _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
