* Clarify Go copyright license agreement @ 2010-12-03 19:04 Ian Lance Taylor 2010-12-03 19:35 ` Mike Stump ` (2 more replies) 0 siblings, 3 replies; 8+ messages in thread From: Ian Lance Taylor @ 2010-12-03 19:04 UTC (permalink / raw) To: gcc-patches [-- Attachment #1: Type: text/plain, Size: 454 bytes --] Making changes to the Go frontend does not actually require a copyright assignment to Google. I misstated this in the README change I committed yesterday. It currently requires a copyright license agreement. I committed this patch to correct and clarify my wording. I agree that this situation is less than ideal. This is the compromise which the gcc steering committee came up with. Perhaps we can come up with something better. I hope so. Ian [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: foo.patch --] [-- Type: text/x-diff, Size: 1935 bytes --] diff -r 0f6903c0e43d go/README --- a/go/README Thu Dec 02 15:21:35 2010 -0800 +++ b/go/README Fri Dec 03 11:00:18 2010 -0800 @@ -38,13 +38,11 @@ To contribute patches to the files in this directory, please see http://golang.org/doc/gccgo_contribute.html . -Changes to these files require a copyright assignment to Google. This -is required to permit the changes to be copied to the gcc repository, -as Google has a copyright assignment with the Free Software -Foundation. - -If you are the copyright holder, you will need to agree to the -individual contributor license agreement at +These master copy of these files is hosted at +http://code.google.com/p/gofrontend . Changes to these files require +signing a Google copyright license agreement. If you are the +copyright holder, you will need to agree to the individual contributor +license agreement at http://code.google.com/legal/individual-cla-v1.0.html. This agreement can be completed online. diff -r 0f6903c0e43d libgo/README --- a/libgo/README Thu Dec 02 15:21:35 2010 -0800 +++ b/libgo/README Fri Dec 03 11:00:18 2010 -0800 @@ -28,13 +28,11 @@ To contribute patches to the files in this directory, please see http://golang.org/doc/gccgo_contribute.html . -Changes to these files require a copyright assignment to Google. This -is required to permit the changes to be copied to the gcc repository, -as Google has a copyright assignment with the Free Software -Foundation. - -If you are the copyright holder, you will need to agree to the -individual contributor license agreement at +These master copy of these files is hosted at +http://code.google.com/p/gofrontend . Changes to these files require +signing a Google copyright license agreement. If you are the +copyright holder, you will need to agree to the individual contributor +license agreement at http://code.google.com/legal/individual-cla-v1.0.html. This agreement can be completed online. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Clarify Go copyright license agreement 2010-12-03 19:04 Clarify Go copyright license agreement Ian Lance Taylor @ 2010-12-03 19:35 ` Mike Stump 2010-12-03 20:42 ` Alexandre Oliva 2010-12-03 20:30 ` Alexandre Oliva 2010-12-03 21:08 ` Andreas Schwab 2 siblings, 1 reply; 8+ messages in thread From: Mike Stump @ 2010-12-03 19:35 UTC (permalink / raw) To: Ian Lance Taylor; +Cc: gcc-patches On Dec 3, 2010, at 11:04 AM, Ian Lance Taylor wrote: > Making changes to the Go frontend does not actually require a copyright > assignment to Google. I misstated this in the README change I committed > yesterday. It currently requires a copyright license agreement. I > committed this patch to correct and clarify my wording. > > I agree that this situation is less than ideal. This is the compromise > which the gcc steering committee came up with. Perhaps we can come up > with something better. I hope so. Well, technically, I'd prefer the FSF allow us to contribute to the GO software by having it grant the rights in our contributions. This way, all people that contribute to gcc today, get a free pass from having to do any paper work at all. Technically, you could just bidirectionally merge bits out of the FSF tree into the other tree as well. Now, I realize that would be _hard_ as an FSF lawyer would have to read and agree to contribute to the GO software, but for developers, it would be the most natural. Sorry for mentioning it in advance. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Clarify Go copyright license agreement 2010-12-03 19:35 ` Mike Stump @ 2010-12-03 20:42 ` Alexandre Oliva 2010-12-04 14:58 ` Florian Weimer 0 siblings, 1 reply; 8+ messages in thread From: Alexandre Oliva @ 2010-12-03 20:42 UTC (permalink / raw) To: Mike Stump, brett; +Cc: Ian Lance Taylor, gcc-patches On Dec 3, 2010, Mike Stump <mikestump@comcast.net> wrote: > Well, technically, I'd prefer the FSF allow us to contribute to the GO > software by having it grant the rights in our contributions. This > way, all people that contribute to gcc today, get a free pass from > having to do any paper work at all. Technically, you could just > bidirectionally merge bits out of the FSF tree into the other tree as > well. Now, I realize that would be _hard_ as an FSF lawyer would have > to read and agree to contribute to the GO software, but for > developers, it would be the most natural. I'm not even sure the FSF *could* do that, given my recollection of the wording in the copyright assignments it has received. IIRC, in return for the assignment, the FSF promises to ensure that any distribution of the work or of works based on it, under the FSF control, ought to be in ways that respect users' freedom over the code. So, offering the code to Google in a way that permitted distribution under non-Free terms, like Google's license agreement permits, might amount to breaking the promise. I don't have easy access to the exact wording of FSF's copyright assignments to check ATM, and even if I did, IANAL, but it's one concern to keep in mind. Now, if Google were to make a commitment compatible with the obligations the FSF is under per the copyright assignments it has received, we might get the no-additional-paperwork arrangement that at least you, Basille and I would prefer. -- Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ You must be the change you wish to see in the world. -- Gandhi Be Free! -- http://FSFLA.org/ FSF Latin America board member Free Software Evangelist Red Hat Brazil Compiler Engineer ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Clarify Go copyright license agreement 2010-12-03 20:42 ` Alexandre Oliva @ 2010-12-04 14:58 ` Florian Weimer 2010-12-04 22:11 ` Paolo Bonzini 0 siblings, 1 reply; 8+ messages in thread From: Florian Weimer @ 2010-12-04 14:58 UTC (permalink / raw) To: Alexandre Oliva; +Cc: Mike Stump, brett, Ian Lance Taylor, gcc-patches * Alexandre Oliva: > I'm not even sure the FSF *could* do that, given my recollection of the > wording in the copyright assignments it has received. IIRC, in return > for the assignment, the FSF promises to ensure that any distribution of > the work or of works based on it, under the FSF control, ought to be in > ways that respect users' freedom over the code. I interpret the contract in such a way that it does not rule out non-copyleft licenses. The FSF does guarantee that the version it ships is free, but nothing beyond that. (In addition, in the GCC context, it is fairly important to some contributors that a copyleft compiler license does not propagate to the generated binaries, but that's not in the contract, either.) I think for symmetry reasons, the FSF should license the front end under a non-copyleft license directly. Licensing asymmetry has turned into a problem for too many software projects. 8-( Furthermore, now that Go is part of GCC, I'm not sure if someone who has signed an assignment contract with the FSF covering GCC can actually license the code to Google (or vice versa). ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Clarify Go copyright license agreement 2010-12-04 14:58 ` Florian Weimer @ 2010-12-04 22:11 ` Paolo Bonzini 0 siblings, 0 replies; 8+ messages in thread From: Paolo Bonzini @ 2010-12-04 22:11 UTC (permalink / raw) To: Florian Weimer Cc: Alexandre Oliva, Mike Stump, brett, Ian Lance Taylor, gcc-patches On 12/04/2010 03:58 PM, Florian Weimer wrote: > Furthermore, now that Go is part of GCC, I'm not sure if someone who > has signed an assignment contract with the FSF covering GCC can > actually license the code to Google (or vice versa). Yes, that is allowed by the license grantback that is part of the FSF copyright assignment. Paolo ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Clarify Go copyright license agreement 2010-12-03 19:04 Clarify Go copyright license agreement Ian Lance Taylor 2010-12-03 19:35 ` Mike Stump @ 2010-12-03 20:30 ` Alexandre Oliva 2010-12-03 20:41 ` Ian Lance Taylor 2010-12-03 21:08 ` Andreas Schwab 2 siblings, 1 reply; 8+ messages in thread From: Alexandre Oliva @ 2010-12-03 20:30 UTC (permalink / raw) To: Ian Lance Taylor; +Cc: gcc-patches On Dec 3, 2010, Ian Lance Taylor <iant@google.com> wrote: > It currently requires a copyright license agreement. IIRC the agreement is a patent license as well, so describing it as a copyright license agreement isn't accurate either. I think just “license agreement” would be fine. > I committed this patch to correct and clarify my wording. Thanks for the improvement so far. -- Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/ You must be the change you wish to see in the world. -- Gandhi Be Free! -- http://FSFLA.org/ FSF Latin America board member Free Software Evangelist Red Hat Brazil Compiler Engineer ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Clarify Go copyright license agreement 2010-12-03 20:30 ` Alexandre Oliva @ 2010-12-03 20:41 ` Ian Lance Taylor 0 siblings, 0 replies; 8+ messages in thread From: Ian Lance Taylor @ 2010-12-03 20:41 UTC (permalink / raw) To: Alexandre Oliva; +Cc: gcc-patches [-- Attachment #1: Type: text/plain, Size: 403 bytes --] Alexandre Oliva <aoliva@redhat.com> writes: > On Dec 3, 2010, Ian Lance Taylor <iant@google.com> wrote: > >> It currently requires a copyright license agreement. > > IIRC the agreement is a patent license as well, so describing it as a > copyright license agreement isn't accurate either. I think just > “license agreement” would be fine. Thanks. I committed the following. Ian [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: foo.patch --] [-- Type: text/x-diff, Size: 1119 bytes --] diff -r 21dfe2499e5d go/README --- a/go/README Fri Dec 03 12:36:11 2010 -0800 +++ b/go/README Fri Dec 03 12:40:10 2010 -0800 @@ -40,7 +40,7 @@ The master copy of these files is hosted at http://code.google.com/p/gofrontend . Changes to these files require -signing a Google copyright license agreement. If you are the +signing a Google contributor license agreement. If you are the copyright holder, you will need to agree to the individual contributor license agreement at http://code.google.com/legal/individual-cla-v1.0.html. This agreement diff -r 21dfe2499e5d libgo/README --- a/libgo/README Fri Dec 03 12:36:11 2010 -0800 +++ b/libgo/README Fri Dec 03 12:40:10 2010 -0800 @@ -30,7 +30,7 @@ The master copy of these files is hosted at http://code.google.com/p/gofrontend . Changes to these files require -signing a Google copyright license agreement. If you are the +signing a Google contributor license agreement. If you are the copyright holder, you will need to agree to the individual contributor license agreement at http://code.google.com/legal/individual-cla-v1.0.html. This agreement ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Clarify Go copyright license agreement 2010-12-03 19:04 Clarify Go copyright license agreement Ian Lance Taylor 2010-12-03 19:35 ` Mike Stump 2010-12-03 20:30 ` Alexandre Oliva @ 2010-12-03 21:08 ` Andreas Schwab 2 siblings, 0 replies; 8+ messages in thread From: Andreas Schwab @ 2010-12-03 21:08 UTC (permalink / raw) To: Ian Lance Taylor; +Cc: gcc-patches Ian Lance Taylor <iant@google.com> writes: > diff -r 0f6903c0e43d go/README > --- a/go/README Thu Dec 02 15:21:35 2010 -0800 > +++ b/go/README Fri Dec 03 11:00:18 2010 -0800 > @@ -38,13 +38,11 @@ > To contribute patches to the files in this directory, please see > http://golang.org/doc/gccgo_contribute.html . > > -Changes to these files require a copyright assignment to Google. This > -is required to permit the changes to be copied to the gcc repository, > -as Google has a copyright assignment with the Free Software > -Foundation. > - > -If you are the copyright holder, you will need to agree to the > -individual contributor license agreement at > +These master copy of these files is hosted at > +http://code.google.com/p/gofrontend . Changes to these files require > +signing a Google copyright license agreement. If you are the > +copyright holder, you will need to agree to the individual contributor > +license agreement at > http://code.google.com/legal/individual-cla-v1.0.html. This agreement > can be completed online. I'd suggest to put URLs inside <> throughout. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-12-04 22:11 UTC | newest] Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-12-03 19:04 Clarify Go copyright license agreement Ian Lance Taylor 2010-12-03 19:35 ` Mike Stump 2010-12-03 20:42 ` Alexandre Oliva 2010-12-04 14:58 ` Florian Weimer 2010-12-04 22:11 ` Paolo Bonzini 2010-12-03 20:30 ` Alexandre Oliva 2010-12-03 20:41 ` Ian Lance Taylor 2010-12-03 21:08 ` Andreas Schwab
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).