public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: Jon Portnoy <avenj@gentoo.org>
Cc: Troy Dack <tad@gentoo.org>, gentoo-dev@gentoo.org, rms@gnu.org
Subject: Re: [gentoo-dev] Why should copyright assignment be a requirement?
Date: Thu, 21 Aug 2003 01:00:40 -0600	[thread overview]
Message-ID: <20030821070040.GA4889@inventor.gentoo.org> (raw)
In-Reply-To: <20030821050925.GA3277@cerberus.oppresses.us>

[-- Attachment #1: Type: text/plain, Size: 3062 bytes --]

On Thu, Aug 21, 2003 at 01:09:25AM -0400, Jon Portnoy wrote:
> > Would it not be possible for copyright to be assigned to Gentoo and the
> > author of the ebuild?
> 
> That's what we needed information from Daniel's lawyer about.

I've been trying to get people to keep their names in the copyright line for
over a year, but no one has really started doing it. To my knowledge, it is
better to have multiple official copyright holders for GPL code than just a
single copyright holder. I would like all our ebuilds to have a copyright
like this:

# Copyright 2003 Gentoo Technologies, Joe User, and others (see cvs
# changelog.) Distributed under the GPL version 2.

I don't see why this would be a problem for anyone, and makes a lot more
sense than what we are doing now. 

What we are doing now began way back when we figured out that slapping a
"Copyright 2000 Gentoo Technologies, Inc." allowed us to comply with the GPL
and get back to coding. That's all there is to our current "policy," folks.
I am very much hoping that people will start using shared copyrights soon.
I think it's very bad to continue using the single "Copyright Gentoo" one,
and hope that some developers will start doing this. This is one trend that
I can't start, since all the work I do is under the Gentoo Technologies,
Inc. name. While I know that I'm not going to rip Gentoo off, the primary
benefit to me is that it quells those who enjoy being paranoid about my
intentions.

The rules should be:

ebuilds should be copyright Gentoo Technologies, Inc. *and* the original
author/submitter, with a note for all additional cvs committers. What this
does is prevent Gentoo or the original committer or later contributors from
changing the license away from the GPL 2 unless all copyright holders agree.
This basically makes it practically impossible for code to be hijacked from
our tree, or from our users (by me presumably, after going on some kind of
evil kick.) This seems near-ideal. It would be helpful if a GPL and
copyright expert could review and comment.

> > I believe that this has been discussed previously on this list (when I get
> > a chance I'll search my archive) and that there was an agreement reached
> > between Gentoo and an educational institution on this very matter.
> 
> Was that agreement actually reached? I have been away from development 
> and not very involved for a couple weeks.

I need to contact them; haven't had time to follow up after LWE. After
thinking a bit about this, it's probably best that I ask Richard Stallman
what he recommends since he is likely to be much more versed in the ins and
outs of this kind of thing than the typical IP lawyer who is not very
familiar with the GPL. I'll cc this email to Richard and see what he says.

Richard, your input would certainly be welcome, and I can forward all
replies you send me to the gentoo-dev list (gentoo-dev is subscriber post
only.)

Best Regards,

-- 
Daniel Robbins
Chief Architect, Gentoo Linux
http://www.gentoo.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-21  6:58 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 [this message]
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
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=20030821070040.GA4889@inventor.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=avenj@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=rms@gnu.org \
    --cc=tad@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