public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luke-Jr <luke-jr@gentoo.org>
To: Jon Portnoy <avenj@gentoo.org>, Paul <set@pobox.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why should copyright assignment be a requirement?
Date: Thu, 21 Aug 2003 13:19:31 +0000	[thread overview]
Message-ID: <200308211319.40637.luke-jr@gentoo.org> (raw)
In-Reply-To: <20030821041723.GA2653@cerberus.oppresses.us>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

IIRC, the only reason one would need to own the copyright would be if the 
copyright were to be changed. Once something is licensed under the GPL, the 
owner cannot change the license on the one they released, only on future 
releases they make.

On Thursday 21 August 2003 04:17 am, Jon Portnoy wrote:
> On Thu, Aug 21, 2003 at 12:09:17AM -0400, Paul wrote:
> > 	Hi;
> >
> > 	A long while back, I asked if it was a requirement
> > for ebuild submiters to assign copyright. I was told
> > no, GPL license was entirely sufficient. I think this has
> > changed, or was untrue.
> > 	Now, Ive already given up on the submission
> > process, but I _am_ curious about this policy, as I
> > havent yet given up on Gentoo itself.
> >
> > Paul
> > set@pobox.com
>
> I would be very interested in hearing your issues with ebuild
> submission, if you'd like to contact me privately about it.
>
> With regards to copyrights, it's necessary for us to own copyright on
> ebuilds in order to defend our intellectual property. If we (Gentoo
> Technologies) don't own copyright on ebuilds (and other pieces of
> Gentoo), we have no legal leg to stand on if someone (for example)
> attempts to put a more restrictive license on that piece of intellectual
> property.
>
> In short: if we don't own copyright, we can't defend ourselves.

- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/RMboZl/BHdU+lYMRApmAAJ9yqbRmqhIR+Z6VEbPSN6z9hR+n8wCdGRB0
ULXOD7KZPx7SqchsOlpJ/qc=
=R5V5
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-08-21 13:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21  4:09 [gentoo-dev] Why should copyright assignment be a requirement? Paul
2003-08-21  4:14 ` Mike Frysinger
2003-08-21  4:34   ` Jon Portnoy
2003-08-21  4:17 ` Jon Portnoy
2003-08-21  4:51   ` Troy Dack
2003-08-21  5:09     ` Jon Portnoy
2003-08-21  7:00       ` Daniel Robbins
2003-08-21 10:52         ` Paul de Vrieze
2003-08-21  5:11     ` Mike Gardiner
2003-08-21  7:04       ` [gentoo-dev] " Paul
2003-08-21  5:11     ` [gentoo-dev] " Mike Gardiner
2003-08-21  5:16   ` [gentoo-dev] " Paul
2003-08-21  5:46     ` Jon Portnoy
2003-08-21  6:41       ` Paul
2003-08-21  6:50         ` Jon Portnoy
2003-08-21  7:37           ` Paul
2003-08-21 10:14           ` Chris Bainbridge
2003-08-21 11:22             ` Chris Gianelloni
2003-08-21 17:56             ` Jon Portnoy
2003-08-21 18:48               ` Chris Bainbridge
2003-08-21 19:31                 ` Brian Jackson
2003-08-22  1:36                 ` Jon Portnoy
2003-08-22  4:45             ` [gentoo-dev] " Paul
2003-08-22 13:16               ` Chris Gianelloni
2003-08-21 10:16     ` [gentoo-dev] " Spider
2003-08-21  8:58   ` [gentoo-dev] " Sven Vermeulen
2003-08-21  9:04     ` Jon Portnoy
2003-08-21 13:49       ` Luke-Jr
2003-08-21 18:00         ` Jon Portnoy
2003-08-22  0:35           ` Luke-Jr
2003-08-22  0:47             ` Lloyd D Budd
2003-08-22  1:15               ` Luke-Jr
2003-08-22 13:20                 ` Lloyd D Budd
2003-08-21 13:19   ` Luke-Jr [this message]
2003-08-21 22:42     ` [gentoo-dev] copyright thread summary? Owen Gunden
2003-08-22  2:43       ` [gentoo-dev] Summary: "Why should copyright assignment be a requirement?" Alec Berryman

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=200308211319.40637.luke-jr@gentoo.org \
    --to=luke-jr@gentoo.org \
    --cc=avenj@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=set@pobox.com \
    /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