On 9/9/07, Darx Kies <[EMAIL PROTECTED]> wrote:
> On the other side MPL allows everyone to just rip off the code, and use
> it in other contexts without even giving anything back to the SharpOS project
> and the open source community and that is for me not acceptable.

Well personally that isn't that important to me, but i understand your pov.

> My suggestion would be to choose GPL and/or LGPL and assign the
> copyright to the SharpOS team as the AOT already does.
> That gives the team/board the right to sell the code, to help the project
> and the buyer is not bound by GPL.

Well i'm really not a fan of GPL, but i would be okay with LGPL.
I also think that using different licenses for different parts will
just complicate things and won't really be any better than having one
type of license..
Having multiple licenses at the same time would be okay to me, but it
seems a bit odd because everybody would always choose the less
restrictive license.
As for giving the team/board the right to sell the code, i'm fine with
that if we're talking pieces of code here and there, but if we're
talking about the whole project as a whole then maybe we should have
some sort of restrictions?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

Reply via email to