From: Lloyd D Budd <lloyd@foolswisdom.com>
To: Luke-Jr <luke-jr@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Why should copyright assignment be a requirement?
Date: Fri, 22 Aug 2003 09:20:23 -0400 [thread overview]
Message-ID: <1061558422.26085.94.camel@localhost> (raw)
In-Reply-To: <200308220115.32507.luke-jr@gentoo.org>
On Thu, 2003-08-21 at 21:15, Luke-Jr wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> But, as was pointed out by someone else, if one were to choose not to assign a
> dual copyright to Gentoo and the license was violated, nothing would stop
> them from doing so later on... right?
Except the copyright owner(s) ;-) but otherwise right.
The discussion in the context of ebuilds seems contrived as it seems
that most often there is little/no copyrightable work involved.
> On Friday 22 August 2003 12:47 am, Lloyd D Budd wrote:
> > IMNAL, but the "standard reason" for SOLE ownership, or ("dual, but not
> > shared copyright") is to enable legal pursuit of license violators. The
> > interesting side effect is that a copyright owner can license
> > distribution, or other rights, under additional licenses.
> >
> > On Thu, 2003-08-21 at 20:35, Luke-Jr wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > I must have read the thread incorrectly at some point, then. I thought
> > > the purpose of Gentoo (co-)owning the copyright was the prevent the
> > > creator from making it proprietary. What exactly does it achive to have
> > > Gentoo (co-)own copyrights on them? I have no objection to the idea, but
> > > I see no actual *reason* why it should be required...
> > >
> > > On Thursday 21 August 2003 06:00 pm, Jon Portnoy wrote:
> > > > On Thu, Aug 21, 2003 at 01:49:25PM +0000, Luke-Jr wrote:
> > > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > > Hash: SHA1
> > > > >
> > > > > Even if the owner were to change the license, they could not change
> > > > > it on ebuilds already released under the GPL.
> > > >
> > > > I'm aware, thank you. I don't need to have the basics of copyright law
> > > > explained to me.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-22 13:25 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 [this message]
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=1061558422.26085.94.camel@localhost \
--to=lloyd@foolswisdom.com \
--cc=gentoo-dev@gentoo.org \
--cc=luke-jr@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