public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Basile Starynkevitch <basile@starynkevitch.net>, gcc@gcc.gnu.org
Subject: Re: Notes from the GROW'10 workshop panel (GCC research opportunities  	workshop)
Date: Wed, 14 Apr 2010 21:34:00 -0000	[thread overview]
Message-ID: <k2g6c33472e1004141404o560ce3abv7b3c2c9e0627ffba@mail.gmail.com> (raw)
In-Reply-To: <mcrvdbtrcda.fsf@dhcp-172-17-9-151.mtv.corp.google.com>

On 14 April 2010 22:46, Ian Lance Taylor <iant@google.com> wrote:
> Basile Starynkevitch <basile@starynkevitch.net> writes:
>
>> My point is that academics can quite easily contribute to GPL
>> software, but much harder obtain the necessary legal authorizations to
>> transfer copyright to FSF. My intuition is that if (in a different
>> past & a different world which did not happen) GCC was only GPLv2+
>> without the FSF copyright requirement -exactly as Linux kernel is,
>> things would have been much different.
>
> That is likely true, but it's something that we really don't want to
> change.  The FSF could and should make the copyright disclaimer much
> simpler--for example, you can do Google's copyright disclaimer on a
> web page (http://code.google.com/legal/individual-cla-v1.0.html).  But
> avoiding the copyright disclaimer entirely is what permitted, e.g.,
> the SCO debacle to occur.

Have you suggested this to the FSF with this specific example? The
Google's disclaimer is in fact much more complex that the FSF's one I
received, so doing it via web would be even simpler/easier.

And in fact, GCC will be better served if the FSF produced a copyright
disclaimer specific for GCC, because the first one I received was too
vague and general for my university to accept, once it was made more
specific, the university had no problem to sign it.

Could not the Steering Committee ask the FSF to make some progress on this?

Manuel.

  reply	other threads:[~2010-04-14 21:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 14:01 Dorit Nuzman
2010-04-11 18:27 ` Chris Lattner
2010-04-11 19:38   ` Grigori Fursin
2010-04-11 20:25     ` Chris Lattner
2010-04-11 20:58       ` Grigori Fursin
2010-04-14 14:34 ` Grigori Fursin
2010-04-14 14:58   ` Steven Bosscher
2010-04-14 15:21     ` Manuel López-Ibáñez
2010-04-14 15:30       ` Steven Bosscher
2010-04-14 15:36       ` Diego Novillo
2010-04-14 15:50         ` Nathan Froyd
2010-04-14 15:57           ` Richard Guenther
2010-04-14 19:19             ` Tom Tromey
2010-04-14 16:06           ` Diego Novillo
2010-04-14 18:30             ` Richard Guenther
2010-04-14 18:49           ` Toon Moene
2010-04-14 19:52             ` Basile Starynkevitch
2010-04-14 20:31               ` Toon Moene
2010-04-14 20:43               ` Toon Moene
2010-04-14 21:02               ` Ian Lance Taylor
2010-04-14 21:34                 ` Manuel López-Ibáñez [this message]
2010-04-15  8:26                 ` Basile Starynkevitch
2010-04-15  8:38                   ` Manuel López-Ibáñez
2010-04-15 12:03                     ` Basile Starynkevitch
2010-04-15 12:07                       ` Andrew Haley
2010-04-15 12:15                         ` Steven Bosscher
2010-04-15 12:17                           ` Andrew Haley
2010-04-22  9:18                       ` Laurent GUERBY
2010-04-14 21:04               ` Nathan Froyd
2010-04-14 19:42           ` Ian Lance Taylor
2010-04-14 15:44       ` Duncan Sands
2010-04-15  9:05   ` Manuel López-Ibáñez
2010-04-16 12:36     ` Grigori Fursin
2010-04-16 17:15       ` Manuel López-Ibáñez
2010-04-16 17:40         ` Grigori Fursin
2010-04-27 12:40         ` Grigori Fursin
2010-04-27 16:31           ` Manuel López-Ibáñez
2010-04-27 18:42             ` Grigori Fursin

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=k2g6c33472e1004141404o560ce3abv7b3c2c9e0627ffba@mail.gmail.com \
    --to=lopezibanez@gmail.com \
    --cc=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).