README.md: contribution about discussion

Leaning on aspects of golang's contribution
(https://golang.org/doc/contribute.html)

Signed-off-by: Vincent Batts <vbatts@redhat.com>

Author: vbatts

README.md

@@ -54,21 +54,34 @@ With Standard Containers we can put an end to that embarrassment, by making INDU
 
 # Contributing
 
-Development happens on github for the spec.  Issues are used for bugs and actionable items and longer
-discussions can happen on the mailing list.  You can subscribe and join the mailing list on
-[google groups](https://groups.google.com/a/opencontainers.org/forum/#!forum/dev).
+Development happens on github for the spec.
+Issues are used for bugs and actionable items and longer discussions can happen on the [mailing list](#mailing-list).
 
-The specification and code is licensed under the Apache 2.0 license found in 
-the `LICENSE` file of this repository.  
+The specification and code is licensed under the Apache 2.0 license found in the `LICENSE` file of this repository.  
+
+## Mailing List
+
+You can subscribe and join the mailing list on [google groups](https://groups.google.com/a/opencontainers.org/forum/#!forum/dev).
 
 ## Weekly Call
 
 The contributors and maintainers of the project have a weekly meeting Wednesdays at 10:00 AM PST.
 The link to the call will be posted on the mailing list each week along with set topics for discussion.
 Everyone is welcome to participate in the call, although there can only be speaking members on the Google Hangout.
 Participants who don't get a speaking slot can watch the live broadcast on [this YouTube channel][youtube] and post feedback and questions on [the IRC channel](#irc).
-Everyone is welcome to propose additional topics, suggest other agenda alterations, or request a speaking slot via the mailing list.
-Minutes for the call will be posted to the mailing list for those who are unable to join the call.
+Everyone is welcome to propose additional topics, suggest other agenda alterations, or request a speaking slot via the [mailing list](#mailing-list).
+Minutes for the call will be posted to the [mailing list](#mailing-list) for those who are unable to join the call.
+
+## Discuss your design
+
+The project welcomes submissions, but please let everyone know what you are working on.
+
+Before undertaking a not-trivial change to this specification, send mail to the [mailing list](#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.
+It also guarantees that the design is sound before code is written; a github pull-request is not the place for high-level discussions.
+
+Typos and grammatical errors can go straight to a pull-request.
+If there is question, start on the [mailing-list](#mailing-list).
 
 ## IRC