From: Deedra Waters <dmwaters@gentoo.org>
To: Donnie Berkholz <spyderous@gentoo.org>
Cc: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] copyright stuff
Date: Wed, 13 Jul 2005 08:41:35 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0507130839380.2378@shell.osuosl.org> (raw)
In-Reply-To: <1121254407.7209.7.camel@supernova.lan.local>
It lets gentoo retain full ownership of things while letting the devs
who write code etc own what they write. Call it a co-ownership so to
speak.
On Wed, 13 Jul 2005, Donnie Berkholz wrote:
> Date: Wed, 13 Jul 2005 04:33:27 -0700
> From: Donnie Berkholz <spyderous@gentoo.org>
> To: gentoo-trustees@lists.gentoo.org
> Subject: Re: [gentoo-trustees] copyright stuff
>
> On Tue, 2005-07-12 at 14:58 -0700, Deedra Waters wrote:
> > 1. We only worry about copyrighting code that gentoo actually owns,
> > mainly catalyst, portage, the installer and things like that.
> > Also any documentation that gentoo has written along with the utilities
> > that may have been written for portage etc etc.
>
> That makes sense to me, since the vast majority of ebuilds aren't really
> copyrightable anyway.
>
> > 2. it would be a co-ownership basically, meaning thatif i wrote
> > documentation or parts of documentation, i would retain the rights to
> > those docs, but gentoo owns the entire thing.
>
> I don't understand this. Could you clarify?
>
> > 3. only gentoo would have the ability to sue. This is more a legal
> > thing, but basically it's so that if we ever had to go into law to
> > defend the copyright, the other person can't force us to drag all of
> > our developers into court.
>
> I'm a little confused about what exactly you're proposing. Is it an
> exclusive license, assigning a share of the rights or something else
> altogether?
>
> Thanks,
> Donnie
>
--
Deedra Waters - Gentoo developer relations, accessibility and infrastructure -
dmwaters@gentoo.org
Gentoo linux: http://www.gentoo.org
--
gentoo-trustees@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-13 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 21:58 [gentoo-trustees] copyright stuff Deedra Waters
2005-07-13 10:43 ` Sven Vermeulen
2005-07-13 11:33 ` Donnie Berkholz
2005-07-13 15:41 ` Deedra Waters [this message]
2005-07-13 16:30 ` Grant Goodyear
2005-07-13 16:31 ` Grant Goodyear
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 19:37 Deedra Waters
2005-06-27 20:17 ` Sven Vermeulen
2005-06-27 20:21 ` Deedra Waters
2005-06-27 21:13 ` Sven Vermeulen
2005-06-28 1:57 ` Donnie Berkholz
2005-06-28 2:16 ` Donnie Berkholz
2005-06-28 2:29 ` Corey Shields
2005-06-28 2:33 ` Kumba
2005-06-28 3:26 ` Donnie Berkholz
2005-06-28 3:03 ` Deedra Waters
2005-06-28 3:27 ` Donnie Berkholz
2005-06-28 5:42 ` Daniel Robbins
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=Pine.LNX.4.58.0507130839380.2378@shell.osuosl.org \
--to=dmwaters@gentoo.org \
--cc=gentoo-trustees@lists.gentoo.org \
--cc=spyderous@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