public inbox for gentoo-trustees@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] copyright stuff
Date: Wed, 13 Jul 2005 11:30:56 -0500	[thread overview]
Message-ID: <20050713163056.GM14373@bmb24.uth.tmc.edu> (raw)
In-Reply-To: <Pine.LNX.4.58.0507121452380.2378@shell.osuosl.org>

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

Deedra Waters wrote: [Tue Jul 12 2005, 04:58:56PM CDT]
> 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 should make life much simpler.  

> 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.

Seems reasonable.

> 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.

Although I think it's reasonable in principle, I would feel better if I
had a better idea of what exactly is involved.  Who would need to sign
some sort of co-ownership document?  Since we're still dealing with
copyright, does this method solve the problems with under-age or non-US
citizens who cannot turn over copyright?  

-g2boojum-
-- 
Grant Goodyear	
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0  9573 A6DC 7152 E0F6 5B76

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

  parent reply	other threads:[~2005-07-13 16:30 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
2005-07-13 16:30 ` Grant Goodyear [this message]
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=20050713163056.GM14373@bmb24.uth.tmc.edu \
    --to=g2boojum@gentoo.org \
    --cc=gentoo-trustees@lists.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