}
</style>
-<h2>About the Code of Conduct</h2>
+<h2 id="about">About the Code of Conduct</h2>
-<h3>Why have a Code of Conduct?</h3>
+<h3 id="why">Why have a Code of Conduct?</h3>
<p>
Online communities include people from many different backgrounds.
they disagree.
</p>
-<h3>Where does the Code of Conduct apply?</h3>
+<h3 id="spaces">Where does the Code of Conduct apply?</h3>
<p>
If you participate in or contribute to the Go ecosystem in any way,
moderators and/or working group (see below).
</p>
-<h2>Gopher values</h2>
+<h2 id="values">Gopher values</h2>
<p>
These are the values to which people in the Go community (“Gophers”) should aspire.
It is the responsibility of <i>all parties</i> to de-escalate conflict when it arises.
</p>
-<h2>Unwelcome behavior</h2>
+<h2 id="unwelcome_behavior">Unwelcome behavior</h2>
<p>
These actions are explicitly forbidden in Go spaces:
<li>Incitement to any of these.
</ul>
-<h2>Moderation</h2>
+<h2 id="moderation">Moderation</h2>
<p>
The Go spaces are not free speech venues; they are for discussion about Go.
below.
</p>
-<h2>Reporting issues</h2>
+<h2 id="reporting">Reporting issues</h2>
<p>
The Code of Conduct Working Group is a group of people that represent the Go
<a href="https://golang.org/s/proposal-process">change proposal process</a>.
</p>
-<h2>Summary</h2>
+<h2 id="summary">Summary</h2>
<ul>
<li>Treat everyone with respect and kindness.
<li>If you encounter an issue, please mail <a href="mailto:conduct@golang.org">conduct@golang.org</a>.
</ul>
-<h3>Acknowledgements</h3>
+<h3 id="acknowledgements">Acknowledgements</h3>
<p>
Parts of this document were derived from the Code of Conduct documents of the