From: Kurt Lieber <klieber@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: [gentoo-trustees] our copyright assignment form has a number of problems
Date: Wed, 23 Jun 2004 16:37:47 +0000 [thread overview]
Message-ID: <20040623163747.GS27818@mail.lieber.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2522 bytes --]
Having never read (or signed) the copyright form[1], I was directed to it
based on a conversation in -dev today. Taking a brief read through it,
it's likely the entire thing is unenforceable given the way we currently
develop.
The assignment states that anything which is "committed by Assignor to an
official Gentoo source code repository using a version control system such
as cvs, subversion or similar software;" has to have the copyright assigned
to Gentoo. It further states that "Assignor warrants that Assignor's
rights in the Work have not been previously assigned, mortgaged or
otherwise encumbered, and Assignor has full right, power and authority to
assign all such rights to Gentoo."
It makes no provisions for things like patches, which are committed to CVS
all the time, but for which the committer has no claim on the copyright.
There are also a number of images committed to the gentoo repository which
are used on the web site and which we have no copyright ownership of.
The best part is this phrase:
---------------------------------------------------------------------------
("Assignor") hereby releases and assigns to Gentoo all Assignor's copyrights,
ownership, and claims for the following items:
source code, object code, screen displays, icons,
documentation, user and developers manuals, authoring,
editing, sound, photography, graphics, animation, musical
composition or arrangement, design, artwork, or layout,
including any advertising, brochures, video, photographs,
films, or computer media relating to the Work.
---------------------------------------------------------------------------
The last phrase is the kicker; "or computer media relating to the work".
As written, we're asserting ownership over all our developer's hard drives.
The problem with all this is, where parts of contracts are found to be
unenforceable and/or overly broad, the courts often throw the entire thing
out. My IANAL opinion is that this copyright assignment form is
next-to-useless for us.
Additionally, given the way it's currently worded, there's no way I'm
agreeing to sign it and I certainly encourage everyone else to avoid
signing it as well.
Corey -- have you made any progress with the IU lawyers in getting them to
help us with our copyright/IP issues? We need to see about getting
alternate counsel to review this document and shore up its weaknesses.
--kurt
[1] http://www.gentoo.org/proj/en/devrel/copyright/assignment.txt
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-06-23 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 16:37 Kurt Lieber [this message]
2004-06-23 17:10 ` [gentoo-trustees] our copyright assignment form has a number of problems Nicholas Jones
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=20040623163747.GS27818@mail.lieber.org \
--to=klieber@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