mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jeff millar" <wa1hco@adelphia.net>
To: "Andre Hedrick" <andre@linux-ide.org>,
	"Dean McEwan" <dean.mcewan@eudoramail.com>
Cc: <linux-kernel@vger.kernel.org>, <abramo.bagnara@libero.it>,
	"Richard Stallman" <rms@gnu.org>
Subject: Re: [OFFTOPIC] RMS and reactions to him (YAWN)
Date: Wed, 15 Jan 2003 20:41:57 -0500	[thread overview]
Message-ID: <022001c2bd00$777a7940$6a01a8c0@wa1hco> (raw)
In-Reply-To: <Pine.LNX.4.10.10301150548030.23438-100000@master.linux-ide.org>

Andre...

Who wrote that?  It's clear and I can understand it!

;-)

jeff

----- Original Message -----
From: "Andre Hedrick" <andre@linux-ide.org>
To: "Dean McEwan" <dean.mcewan@eudoramail.com>
Cc: <linux-kernel@vger.kernel.org>; <abramo.bagnara@libero.it>; "Richard
Stallman" <rms@gnu.org>
Sent: Wednesday, January 15, 2003 9:21 AM
Subject: Re: [OFFTOPIC] RMS and reactions to him (YAWN)


>
> Dean,
>
> Have you ever pondered the question why some of the new code in 2.5 is
> coming up with a dual-license of OSL/GPL ?  Is it because OSL has some
> meaningful terms understood by the courts?  Is it because the folks at OSI
> understand a bigger picture?
>
> See I found it worthy enough to go and investigate.
>
> What I found, I like.
>
> So if the question was put before everyone to examine the OSL, is this a
> better and stronger license to protect the ideas of "free software" ?
>
> If the conclusions resulted a large positive movement towards OSL and away
> from GPL, what do you expect the reponse from RMS would be to the
> following:
>
> Richard, is there a way to make OSL and GPL compatable ?
> Richard, will you allow OSL and GPL to coexist ?
> Richard, can OSL superceed GPL ?
> Richard, can you agree there may be a better license than GPL ?
> Richard, if people want to develop under OSL, what are the results
> of the combined work?
> Richard, if GPL can be improved by the adoption of OSL ideas,
> what benefits are there to you idea to holding onto the
> past?
>
>
> My concern is that vision and ideas started by RMS, are being clouded.
> OSL could have some more bit added to it, requiring the return of the
> changes to the original author, or the offending party is required to pay
> an alteration royality fee.
>
> I do not know the what the best answer is today.
>
> However, I am willing to put my money down (if I ever make any now) to
> draft a licenses that empowers the community with a real legal strong hold
> to protect its interest of Open Source, and keeping it open.
>
> I like may other developers have/know/seen their work altered and not
> returned, yet without having a license with some teeth based in law
> already tried in courts, the personal risk is to great to pursue.
>
> If I am a bad person for wanting to empower the community with stonger
> license than GPL, IMHO is superior to GPL, then I will gladdy be a bad
> person.
>
> What we all hear is one person promoting one agenda with one idea, and the
> idea has clouded the vision.  If another idea can carry the original
> vision further and closer to achieving that of the visionary, why stop
> half way down the road ?
>
>
> Regards,
>
> Andre Hedrick
> LAD Storage Consulting Group
>
>
> I have had enough of the mud slinging.
> Oh, I think your address should be restored, regardless.
> Did you know you can remove GPL from your work, but you can not take back
> what is out there now?
>



  reply	other threads:[~2003-01-16  1:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 12:52 Dean McEwan
2003-01-15 14:21 ` Andre Hedrick
2003-01-16  1:41   ` jeff millar [this message]
2003-01-16 10:42   ` Rik van Riel

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='022001c2bd00$777a7940$6a01a8c0@wa1hco' \
    --to=wa1hco@adelphia.net \
    --cc=abramo.bagnara@libero.it \
    --cc=andre@linux-ide.org \
    --cc=dean.mcewan@eudoramail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rms@gnu.org \
    /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

all inboxes | Powered by JetHome®