From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-trustees@lists.gentoo.org
Subject: Re: [gentoo-trustees] copyright stuff
Date: Mon, 27 Jun 2005 22:17:59 +0200 [thread overview]
Message-ID: <20050627201759.GA9776@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0506271234120.5498@shell.osuosl.org>
[-- Attachment #1: Type: text/plain, Size: 2836 bytes --]
On Mon, Jun 27, 2005 at 12:37:26PM -0700, Deedra Waters wrote:
> I want to start this out as a small discussion to start with and take it
> to core once i get a general idea of how people feel.
>
> What i want to know from you all is do we really want to have/deal with
> the copyright stuff?
>
> My feeling is that while copyrights are/can be a good thing, i'm
> starting to think that with the major differences that's in our
> developer base, that we're not going to get a complete copyright doc
> that everyone can and will be able to handle. Some countries can't sign
> over copyrights, while we have devs that are under the legal age to sign
> documents.
True about the age, but not true about not being able to transfer
copyrights. We are talking about transferrable rights here, not moral
rights.
I still feel that a copyright assignment is the best option if we can not
have the copyright available for both parties (i.e. both the developer /and/
the foundation can take action against copyright violations). Having dual
copyrights is more troublesome than full copyright assignment, since full
copyright assignment is probably listed in all relevant laws (Copyright Act
in the USA, Auteursrecht in Belgium, etc.) while dual copyright is more
something exotic.
Another possibility is an exclusive license. With an exclusive license, the
Foundation can protect the code (take appropriate measures, ...) while the
original author still retains the copyright. The drawback is that the
original author can not use the code beyond what the Foundation and the
contract (= the license) sais ("exclusive" license).
But, back to the why's: I do feel that we need to have this protection.
With the copyright (or exclusive license) in the Foundation's hands,
Gentoo's code is completely contained within the project. We are then able
to protect ourselves in case of copyright violations.
Unless I am mistaken, copyright violations are the only reason why we would
want copyright assignment (it is not the Foundation's intention to change
license; as a matter of fact, we explicitly made clear that we will never
change license). Yet copyright violations are a big issue.
One frequent violation is removing the creditation given on the code (or
documentation). That may seem small, but for a free software/documentation
contribution, it is very important to the contributor. What good is the
code/documentation to the contributor if no-one knows he did it?
Other violations are for instance modifications without making the changes
open (case of GPL), using the code/documentation as part of a different,
non-free work, etc.
Wkr,
Sven Vermeulen
--
Documentation project leader - Gentoo Foundation Trustee
The Gentoo Project <<< http://www.gentoo.org >>>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-27 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 19:37 [gentoo-trustees] copyright stuff Deedra Waters
2005-06-27 20:17 ` Sven Vermeulen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 21:58 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
2005-07-13 16:31 ` Grant Goodyear
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=20050627201759.GA9776@gentoo.org \
--to=swift@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