broken link (and other issues) on the _contribute.html_ page

[Zvi Gilboa]

Greetings,

On the _/contribute/.html_//page (http://gcc.gnu.org/contribute.html), 
the link to the script that should help check conformance with GNU 
coding style is broken (the root "trunk" is unknown, etc.)


Note also that the section "Legal Prerequisites" comes before "Coding 
Standards."  Likely to be understood as a reflection of the 
organization's priorities, some potential contributors (myself included) 
might consider this to be a bit problematic.


More on that note: the first paragraph reads: "We strongly encourage 
individuals as well as organizations to contribute...," yet it does not 
say /why/ the GCC encourages that, or what the overall benefits (to 
society, the contributing individual, etc.) would be. In my humble 
opinion, the mission should never go out of sight, and nothing should be 
taken for granted...


Last but not least: in that first sentence, there should be /_no comma/_ 
after GCC.  And there should probably /_be_/ a comma before "as well 
as," although that would be a matter of a judgment call, rather than a 
strict grammatical rule.


Thank you for looking at this!  I look forward to your response.

Sincerely yours,
Zvi Gilboa

_contribute.html_: missing information regarding feedback procedure

[Zvi Gilboa]

Greetings,

At the very bottom of the above page 
(http://gcc.gnu.org/contribute.html), there is no indication of GCC only 
accepting *plain text* messages.  As most mail clients nowadays default 
to a combined text/html format, this leaves users with the unpleasant 
experience of having their messages initially rejected by the server. 
Note that most users would simply assume that the "server is not 
working," and won't go into the trouble of reading the full text of the 
MAILER DAEMON's response, where the actual description of the problem is 
hidden somewhere in the middle of the second paragraph.  Worse than 
that, as the message is sent by mail-dae...@sourceware.org --- an entity 
that does not show any relation to the GNU or GCC -- some users might 
even fail to notice that the message had never been received, and thus 
falsely believe that the organization had simply chosen to ignore them.


Best regards,
Zvi Gilboa