From: Anthony Gorecki <anthony@ectrolinux.com>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Copyright assignment and ownership (again)
Date: Sun, 27 Feb 2005 18:02:57 -0800 [thread overview]
Message-ID: <200502271803.01417.anthony@ectrolinux.com> (raw)
In-Reply-To: <20050227171341.64708a0b@snowdrop>
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
On Sunday, February 27, 2005 9:13 am, Ciaran McCreesh wrote:
> How about we recognise that individual ebuilds aren't worth anything
> and that the tree *as a whole* should be copyrighted as a single work?
This seems like a sensible idea, presuming the developers make certain that
the ebuilds which are committed to the tree are licensed under the GPL. I do,
however, believe that the original author of a newly contributed ebuild
deserves at least to have his name mentioned as such in the file.
--
Anthony Gorecki
Ectro-Linux Foundation
[-- Attachment #2: Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2005-02-28 2:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 13:02 [gentoo-dev] Copyright assignment and ownership (again) Anthony Gorecki
2005-02-26 15:58 ` [gentoo-dev] gcc-4.0.0_alpha20050213 fails Andres Järv
2005-02-26 16:37 ` Stephen P. Becker
2005-02-26 17:50 ` Andres Järv
2005-02-26 17:58 ` Stephen P. Becker
2005-02-27 23:53 ` Luca Barbato
2005-02-27 12:35 ` [gentoo-dev] Copyright assignment and ownership (again) Jon Portnoy
2005-02-27 17:04 ` Joshua Brindle
2005-02-27 17:13 ` Ciaran McCreesh
2005-02-27 17:18 ` Simon Stelling
2005-02-27 17:21 ` Ciaran McCreesh
2005-02-27 23:05 ` Georgi Georgiev
2005-02-28 10:47 ` Simon Stelling
2005-02-28 11:02 ` Krzysiek Pawlik
2005-02-28 2:02 ` Anthony Gorecki [this message]
2005-02-28 5:11 ` Donnie Berkholz
2005-02-28 13:14 ` Chris Gianelloni
2005-02-28 12:44 ` Georgi Georgiev
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=200502271803.01417.anthony@ectrolinux.com \
--to=anthony@ectrolinux.com \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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