public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kenneth Vestergaard Schmidt <charon@binarysolutions.dk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuild info: author, maintainer and copyrights
Date: Fri, 8 Feb 2002 15:06:01 +0100	[thread overview]
Message-ID: <20020208140601.GA937@silence> (raw)
In-Reply-To: <1013149597.15937.10.camel@uranus.u235.eyep.net>

On Fri, Feb 08, 2002 at 08:26:37AM +0200, Vitaly Kushneriuk wrote:
> > What _real_ difference does it make? The only difference is that
> > Gentoo Technologies, Inc. can't relicense it and make a closed-source
> > version. However, if it was possible for them, and if they did, everybody
> > could just ignore them and continue working on the last version released
> > under the GPL.
> The point is not that you can't fork the project. You'r right at that
> you always can, if it's licensed under GPL. The point is preserving
> the future "free" status of _all_ derivative works as well. If you don't
> care about that, you can just put all the work in "public domain".

But all of a sudden I have to trust you? You won't trust Gentoo, why should
anybody want to trust eachother then? If people keep the copyright to them-
selves, it would mean that small pieces of Gentoo could fall into proprie-
tary status. If the majority of people are so paranoid that they won't trust
Gentoo Technologies, Inc. with a few ebuilds, the only solution would be to
make a "Gentoo Social Contract" or some sorts, where it would be guaranteed
that Gentoo will always be Free Software. But if you can't make the leap of
faith and trust Daniel Robbins when he says Gentoo will always be Free, why
would you trust such a document?

Anyway, once I get around to contributing to this fine project, I won't have
any problem assigning my copyright to Gentoo. It's the least I can do in
return for getting such a nice distribution.

--
Best Regards
Kenneth Vestergaard Schmidt


  reply	other threads:[~2002-02-08 14:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-03  4:10 [gentoo-dev] Ebuild info: author, maintainer and copyrights Ilian Zarov
2002-02-03  5:37 ` Vitaly Kushneriuk
2002-02-07 16:12   ` Chris Houser
2002-02-07 17:08     ` Vitaly Kushneriuk
2002-02-07 19:22       ` Daniel Robbins
2002-02-07 19:46         ` mbutcher
2002-02-07 20:44           ` Vitaly Kushneriuk
2002-02-07 21:27             ` Daniel Robbins
2002-02-08  0:27             ` Kenneth Vestergaard Schmidt
2002-02-08  6:26               ` Vitaly Kushneriuk
2002-02-08 14:06                 ` Kenneth Vestergaard Schmidt [this message]
2002-02-08 18:36                   ` Vitaly Kushneriuk
2002-02-08 14:21                     ` Bob Phan
2002-02-07 20:48           ` Daniel Robbins
2002-02-07 20:43             ` mbutcher
  -- strict thread matches above, loose matches on Subject: below --
2002-02-08 14:21 Sean Mitchell

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=20020208140601.GA937@silence \
    --to=charon@binarysolutions.dk \
    --cc=gentoo-dev@gentoo.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