From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-trustees@lists.gentoo.org, gentoo-core@lists.gentoo.org
Subject: Re: [gentoo-trustees] copyright assignment doc
Date: Tue, 29 Jun 2004 20:44:51 -0400 [thread overview]
Message-ID: <20040630004451.GF25039@time.flatmonk.org> (raw)
In-Reply-To: <20040629181316.GH18023@mail.lieber.org>
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
Kurt Lieber wrote: [Tue Jun 29 2004, 02:13:16PM EDT]
> * It claims ownership of developer hard drives "...or computer media
> relating to the Work.")
> * It says "Gentoo Technologies" instead of "Gentoo Foundation"
> * It is completely unenforceable for any user (non-dev) that submits
> something to bugzilla and/or submissions@gentoo.org. (we're not
> requiring them to sign this doc, so it's not enforceable)
We just need some integration with bugzilla, and get rid of
submissions@gentoo.org. The integration with bugzilla should include
a notice on the page when making an attachment that the submitter is
assigning coprights over to Gentoo.
I don't know how to do this otherwise. When somebody submits an
ebuild, we can't have them getting upset at Gentoo and claiming we ran
off with their stuff. Also we don't want them licensing ebuilds to
us... we really want to own the copyright on stuff in th tree so that
we have future rights.
> * Because we allow the storage things like kernel patches, etc. for which
> we do not own the copyright, in CVS (in the files/ directories), it shows
> that we're selectively enforcing the copyright assignment. In the past,
> this has often resulted in the entire document being tossed in court.
Gonna have to talk to a lawyer about that one.
> * It is questionable whether or not we have any legal right to enforce
> copyright claims for non-US devs. They're not US citizens, so it's not
> clear if they're subject to US copyright restrictions/assignments.
Well, that doesn't change the fact that we should attempt to get
copyright assignment even from non-U.S. devs. *shrug*
> * We selectively enforce who must sign it.
No comment.
> * [minor] http://www.gentoo.org/proj/en/devrel/copyright/index.xml needs to
> be updated to remove Daniel from the text.
Right.
I think Deedra had a good point. There's only so much we can do to
make this thing foolproof without the help of a lawyer. Following the
touch ups that we can make, that's probably the best route. (Raises
the question: how do we *pay* lawyer fees?)
Regards,
Aron
--
Aron Griffis
Gentoo Linux Developer
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-30 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 18:13 [gentoo-trustees] copyright assignment doc Kurt Lieber
2004-06-29 22:21 ` Deedra Waters
2004-06-30 0:44 ` Aron Griffis [this message]
2004-06-30 19:57 ` Paul de Vrieze
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=20040630004451.GF25039@time.flatmonk.org \
--to=agriffis@gentoo.org \
--cc=gentoo-core@lists.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