From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20090401204616.GE16666@tuxbookpro.rit.edu> References: <49D35353.7020400@aspector.com> <3e1162e60904010748w2d0aac8v307089b295f39ca4@mail.gmail.com> <49D382A2.9040001@aspector.com> <3e1162e60904010920l1f78e32dx2eb0e4c51dc237a7@mail.gmail.com> <49D39B0F.2030508@aspector.com> <1238608248.22573.19384.camel@work> <49D3C83C.9040608@aspector.com> <20090401201908.GC2577@home.power> <20090401204218.GD16666@tuxbookpro.rit.edu> <20090401204616.GE16666@tuxbookpro.rit.edu> Date: Wed, 1 Apr 2009 23:11:28 +0200 Message-ID: <5d375e920904011411j6584501va540d7720de772d5@mail.gmail.com> From: Uriel To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] J9P/StyxLib Topicbox-Message-UUID: d05637e2-ead4-11e9-9d60-3106f5b1d025 Actually the GPL doesn't do what you guys claim it to do, it doesn't require people to share back with you changes to your code, it only requires them to release their changes if they *redistribute* their code. Anyway, licenses are an annoyance and a waste of everyone's time and resources. I agree with Alex that the best is Public Domain, or at least BSD/MIT/ISC-style license, which is as close as you can get to Public Domain while retaining copyright. Peace uriel On Wed, Apr 1, 2009 at 10:46 PM, J.R. Mauro wrote: > On Wed, Apr 01, 2009 at 04:42:18PM -0400, J.R. Mauro wrote: >> On Wed, Apr 01, 2009 at 11:19:08PM +0300, Alex Efros wrote: >> > Hi! >> > >> > On Wed, Apr 01, 2009 at 10:02:04PM +0200, Bernd R. Fix wrote: >> > > 2.) You have an OS project with a different, incompatible license >> > > =C2=A0 =C2=A0 and want to include a GPL project or base some work on= it. >> > > >> > > =C2=A0 =C2=A0 I am sure that this problem occurred many times in the= past; maybe >> > > =C2=A0 =C2=A0 there even exists a 'best practice' approach how to de= al with this. >> > > >> > > To be honest: I don't think that the first case is an argument again= st >> > > the GPL - not for me. I am more worried about the second case. >> > > >> > > So my question to you licensing experts: is there a better license t= hat >> > > follows my basic statement (see above) and allows better "integratio= n" >> > > into other OS licenses? If I have a better license model, I am certa= inly >> > > willing to change to it. >> > >> > For libraries it usually solved using LGPL instead of GPL. >> > >> > >> > P.S. As for me, I'd like to try to make world a little better, and don= 't >> > bother much about reusing my code in commercial projects or even remov= ing >> > my name from sources - so I use Public Domain for all my applications = and >> > libraries. >> > >> > GPL is a virus, designed to war against commercial software. That's no= t my war. >> >> Though this is certainly rms's intention, I'm not aware of a license tha= t >> guarantees you get modifications to your source code back, and that is i= mportant >> to me as well. I don't really want people to improve on my ideas without= helping >> me in the process, and there are a lot of people will do just that. >> >> So while the "forcible sharing" of the GPL is kind of fascist, I don't s= ee any >> other way to have the guarantee that improvements to your code by others= are made >> available to you. >> >> > >> > -- >> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = WBR, Alex. >> > > > D'oh. I *do* know a license that does this: the Vim License. You aren't f= orced > to distribute source code, but if the original author wants to get it, yo= u have > to provide it free of charge. Similar to the GPL, but less nasty and less > idealistic. > >