From 61dbc3401a1af9feb0bbcf782adddd867bc3110f Mon Sep 17 00:00:00 2001
From: Andrew Gerrand <adg@golang.org>
Date: Mon, 6 May 2013 15:02:56 -0700
Subject: [PATCH] doc: add FAQ entry about language changes

R=golang-dev, dsymonds, r
CC=golang-dev
https://golang.org/cl/9244043
---
 doc/go_faq.html | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/doc/go_faq.html b/doc/go_faq.html
index 63ad66c519..62a564b6bf 100644
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -454,6 +454,34 @@ as when hosting an untrusted program, the implementation could interlock
 map access.
 </p>
 
+<h3 id="language_changes">
+Will you accept my language change?</h3>
+
+<p>
+People often suggest improvements to the language—the
+<a href="http://groups.google.com/group/golang-nuts">mailing list</a>
+contains a rich history of such discussions—but very few of these changes have
+been accepted.
+</p>
+
+<p>
+Although Go is an open source project, the language and libraries are protected
+by a <a href="/doc/go1compat.html">compatibility promise</a> that prevents
+changes that break existing programs.
+If your proposal violates the Go 1 specification we cannot even entertain the
+idea, regardless of its merit.
+A future major release of Go may be incompatible with Go 1, but we're not ready
+to start talking about what that might be.
+</p>
+
+<p>
+Even if your proposal is compatible with the Go 1 spec, it may be
+not be in the spirit of Go's design goals.
+The article <i><a href="http://talks.golang.org/2012/splash.article">Go
+at Google: Language Design in the Service of Software Engineering</a></i>
+explains Go's origins and the motivation behind its design.
+</p>
+
 <h2 id="types">Types</h2>
 
 <h3 id="Is_Go_an_object-oriented_language">
-- 
2.48.1