[gccgo] Add notes about contributing patches

[Ian Lance Taylor]

Basile Starynkevitch <basile@starynkevitch.net> writes:

> For me Basile, getting the legal papers was so painful that I will
> never do that again. So if I need any bureaucratic work (i.e. to get
> another legal signature from my employer) to be able to propose some
> patch to gcc/go/ or libgo/ I prefer to avoid proposing such patches.

Believe me, compared to the FSF process, it will be much much much
easier for you to sign the Google copyright assignment if you choose to
do so.  You can do it using a web form.

> So definitely, a clarification is welcome. Can people (like me) already
> covered by a copyright assignment to FSF send patches for gcc/go or
> libgo/ or should they avoid that? 
>
> Or is Google's goal to avoid any patch [to the gcc/go or libgo/ part of
> FSF GCC trunk] which is not covered by an extra legal document with
> Google?

As I mention in my reply to Alex, my goal (Google as such doesn't really
care) is to make it possible to use the Go frontend with compilers other
than gcc.  Therefore, yes, an extra legal document is required.

> I hope that legal rules to submit patches don't vary from one
> subdirectory of the GCC trunk to another.

I agree that that would be better but I don't see how to achieve all
these goals.

Ian