From: Latchesar Ionkov <lucho@ionkov.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] J9P/StyxLib
Date: Wed, 1 Apr 2009 14:47:29 -0600 [thread overview]
Message-ID: <f158dc670904011347m676123b7rdd62f9b5a4d629a2@mail.gmail.com> (raw)
In-Reply-To: <20090401204218.GD16666@tuxbookpro.rit.edu>
Are you sure there will be any improvements of your code if nobody
wants to use it because of the license?
Lucho
On Wed, Apr 1, 2009 at 2:42 PM, J.R. Mauro <jrm8005@gmail.com> 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
>> > and want to include a GPL project or base some work on it.
>> >
>> > I am sure that this problem occurred many times in the past; maybe
>> > there even exists a 'best practice' approach how to deal with this.
>> >
>> > To be honest: I don't think that the first case is an argument against
>> > 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 that
>> > follows my basic statement (see above) and allows better "integration"
>> > into other OS licenses? If I have a better license model, I am certainly
>> > 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 removing
>> 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 not my war.
>
> Though this is certainly rms's intention, I'm not aware of a license that
> guarantees you get modifications to your source code back, and that is important
> 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 see any
> other way to have the guarantee that improvements to your code by others are made
> available to you.
>
>>
>> --
>> WBR, Alex.
>>
>
>
next prev parent reply other threads:[~2009-04-01 20:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 11:43 Bernd R. Fix
2009-04-01 13:20 ` hiro
2009-04-01 14:48 ` David Leimbach
2009-04-01 15:05 ` Bernd R. Fix
2009-04-01 16:20 ` David Leimbach
2009-04-01 16:49 ` Bernd R. Fix
2009-04-01 17:28 ` David Leimbach
2009-04-01 17:50 ` Roman V Shaposhnik
2009-04-01 20:02 ` Bernd R. Fix
2009-04-01 20:19 ` Alex Efros
2009-04-01 20:42 ` J.R. Mauro
2009-04-01 20:46 ` J.R. Mauro
2009-04-01 21:11 ` Uriel
2009-04-01 21:33 ` J.R. Mauro
2009-04-01 22:01 ` hiro
2009-04-01 20:47 ` Latchesar Ionkov [this message]
2009-04-01 21:30 ` J.R. Mauro
2009-04-01 21:22 ` hiro
2009-04-01 21:06 ` Wes Kussmaul
2009-04-01 21:12 ` David Leimbach
2009-04-02 18:04 ` Roman V Shaposhnik
2009-04-03 1:09 ` Bernd R. Fix
2009-04-01 15:06 ` Roman V Shaposhnik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f158dc670904011347m676123b7rdd62f9b5a4d629a2@mail.gmail.com \
--to=lucho@ionkov.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).