public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul <set@pobox.com>
To: Jon Portnoy <avenj@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Why should copyright assignment be a requirement?
Date: Thu, 21 Aug 2003 01:16:37 -0400	[thread overview]
Message-ID: <20030821051637.GF26885@squish.home.loc> (raw)
In-Reply-To: <20030821041723.GA2653@cerberus.oppresses.us>

Jon Portnoy <avenj@gentoo.org>, on Thu Aug 21, 2003 [12:17:23 AM] said:

> 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.
> 
> -- 
> Jon Portnoy
> avenj/irc.freenode.net

	Hi;

	Thankyou for your kind, swift response;

	Maybe its my paranoia, but while I _might_ be willing
to assign copyright to the FSF, Im not sure a company with
a distribution deserves such trust. Witness Caldera...

	Once you have the GPL, you have a license. I could
relicense an ebuild to, say some *BSD based thing, or some
commercial spin-off if I wanted (if I still hold copyright),
but that doesnt affect "Gentoo Technologies, Inc." right
to use the ebuild under the GPL. It just affects their ability
to completely control the 'intellectual property'.

	In short, Im hearing that its protective leverage
for Gentoo Technologies, Inc., an entity whose status I am not
currently sure of...

Paul
set@pobox.com

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-08-21  5:17 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   ` Paul [this message]
2003-08-21  5:46     ` [gentoo-dev] " 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=20030821051637.GF26885@squish.home.loc \
    --to=set@pobox.com \
    --cc=avenj@gentoo.org \
    --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