| 1 |
I'd suggest the license. I suspect that as long as the terms are right, |
| 2 |
that people won't have problems with the license. Trying to maintain |
| 3 |
both a copyright, and a license would cause a lot of problems, and a |
| 4 |
copyright is much harder to handle since we would have to get anyone |
| 5 |
under 18 to get their parents to sign the thing etc etc etc. |
| 6 |
|
| 7 |
|
| 8 |
On Mon, 27 Jun 2005, Donnie Berkholz wrote: |
| 9 |
|
| 10 |
> Date: Mon, 27 Jun 2005 18:57:53 -0700 |
| 11 |
> From: Donnie Berkholz <spyderous@g.o> |
| 12 |
> To: Sven Vermeulen <swift@g.o> |
| 13 |
> Cc: gentoo-trustees@l.g.o |
| 14 |
> Subject: Re: [gentoo-trustees] copyright stuff |
| 15 |
> |
| 16 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 17 |
> Hash: SHA1 |
| 18 |
> |
| 19 |
> Sven Vermeulen wrote: |
| 20 |
> > I still feel that a copyright assignment is the best option if we can not |
| 21 |
> > have the copyright available for both parties (i.e. both the developer /and/ |
| 22 |
> > the foundation can take action against copyright violations). Having dual |
| 23 |
> > copyrights is more troublesome than full copyright assignment, since full |
| 24 |
> > copyright assignment is probably listed in all relevant laws (Copyright Act |
| 25 |
> > in the USA, Auteursrecht in Belgium, etc.) while dual copyright is more |
| 26 |
> > something exotic. |
| 27 |
> > |
| 28 |
> > Another possibility is an exclusive license. With an exclusive license, the |
| 29 |
> > Foundation can protect the code (take appropriate measures, ...) while the |
| 30 |
> > original author still retains the copyright. The drawback is that the |
| 31 |
> > original author can not use the code beyond what the Foundation and the |
| 32 |
> > contract (= the license) sais ("exclusive" license). |
| 33 |
> |
| 34 |
> How about this: By default, everybody signs off to one of the above. |
| 35 |
> Strong objectioners have the option of signing a nonexclusive license |
| 36 |
> instead. |
| 37 |
> |
| 38 |
> Thanks, |
| 39 |
> Donnie |
| 40 |
> -----BEGIN PGP SIGNATURE----- |
| 41 |
> Version: GnuPG v1.4.1 (GNU/Linux) |
| 42 |
> |
| 43 |
> iD8DBQFCwK6hXVaO67S1rtsRAuPLAJ0dEHApkA5kRjnfBrMhEM7XQulu5ACfdLED |
| 44 |
> RjIK0rgPDUKHjhbJ49sWw7c= |
| 45 |
> =e0lP |
| 46 |
> -----END PGP SIGNATURE----- |
| 47 |
> |
| 48 |
|
| 49 |
-- |
| 50 |
Deedra Waters - Gentoo developer relations, accessibility and infrastructure - |
| 51 |
dmwaters@g.o |
| 52 |
Gentoo linux: http://www.gentoo.org |
| 53 |
|
| 54 |
-- |
| 55 |
gentoo-trustees@g.o mailing list |
Archives