On Wed, Oct 16, 2002 at 03:51:17PM +0200, Christian Mayer wrote: > > If you want to change the licence you must ask every contributor. If one > doesn't answer or one rejects the change (you'll have to assume the > worst) you must roll these commits back before you change the license. > There's no other way to do it. > > Code that has grown over the time is thus quite impossible to convert to > a new license with out implementing it in a clean room. > > As this sounds like *very* much work to me and all of us have no spare > time (if they'd had they'd be improoving FGFS...) I can't see the FGFS > changing the license in the near future. > If a company needs a differnt licence they could do it if they have the > resources... (have a look at the Wine project as a reference)
IMO, changing licenses is one of those areas which end up being easier in practice than expected - if people see a good reason to change the license. If the reasons to change the license aren't strong enough you are much more likely to encounter resistance (and as has been discussed resistance would make changing the license very difficult). To date, I don't believe the reasons to change the license are strong enough to overcome any resistance. -- James (Jay) Treacy [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
