>On Fri, 09 Nov 2001 01:03:23 -0500 >"Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx> wrote: > > >MP> Umm - be careful here. GPL != MIT. GPL code can not (and will not) be >MP> incorporated with >MP> OBOS. It would certainly be possible to bundle GPL licensed apps (as >MP> Be did). However, >MP> sharing code is a whole different matter. I don't think that you meant >MP> what I am warning >MP> against, Matthew (Matt?), but others might take your comment out of >MP> context, so I want >MP> to clarify that. :-) > >I might have missed something here, so please is there anywhere I can look >to know why MIT license instead of GPL? > >'s >Rafael http://open-beos.sourceforge.net/faqs.html The reason is this: if you take GPL code and change it, add to it, etc. and then distribute it, you have to release your source code as GPL as well. This is often referred to as the "viral" effect -- i.e. any code that touches GPL become GPL itself. We are shying away from this because there are many talented developers interested in commercial development who might avoid using/contributing to OpenBeOS if it was GPL. The MIT license, on the other hand, has no such requirements.