From: Andrew Gerrand Date: Fri, 31 Jul 2015 01:43:57 +0000 (+1000) Subject: doc: link to proposal process from contribution guidelines X-Git-Tag: go1.5rc1~52 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=3c10bdd118cf59e3c2721723a628c3d49c703337;p=gostls13.git doc: link to proposal process from contribution guidelines Change-Id: I992cb1afeef498353d529238e508fa438d6c069c Reviewed-on: https://go-review.googlesource.com/12912 Reviewed-by: Russ Cox Reviewed-by: Rob Pike --- diff --git a/doc/contribute.html b/doc/contribute.html index c419557208..efe0f4a8b5 100644 --- a/doc/contribute.html +++ b/doc/contribute.html @@ -20,23 +20,24 @@ see Contributing to gccgo.)

The project welcomes submissions but please let everyone know what -you're working on if you want it to become part of the main repository. +you're working on if you want to change or add to the Go repositories.

-Before undertaking to write something new for the Go project, send -mail to the mailing -list to discuss what you plan to do. This gives everyone a -chance to validate the design, helps prevent duplication of effort, -and ensures that the idea fits inside the goals for the language -and tools. It also guarantees that the design is sound before code -is written; the code review tool is not the place for high-level -discussions. +Before undertaking to write something new for the Go project, +please file an issue +(or claim an existing issue). +Significant changes must go through the +change proposal process +before they can be accepted.

-In short, send mail before you code. -And don't start the discussion by mailing a change list! +This process gives everyone a chance to validate the design, +helps prevent duplication of effort, +and ensures that the idea fits inside the goals for the language and tools. +It also checks that the design is sound before code is written; +the code review tool is not the place for high-level discussions.

Testing redux