doc: update Code of Conduct wording and scope
doc: update Code of Conduct wording and scope

This change removes the punitive language and anonymous reporting mechanism
from the Code of Conduct document. Read on for the rationale.

More than a year has passed since the Go Code of Conduct was introduced.
In that time, there have been a small number (<30) of reports to the Working Group.
Some reports we handled well, with positive outcomes for all involved.
A few reports we handled badly, resulting in hurt feelings and a bad
experience for all involved.

On reflection, the reports that had positive outcomes were ones where the
Working Group took the role of advisor/facilitator, listening to complaints and
providing suggestions and advice to the parties involved.
The reports that had negative outcomes were ones where the subject of the
report felt threatened by the Working Group and Code of Conduct.

After some discussion among the Working Group, we saw that we are most
effective as facilitators, rather than disciplinarians. The various Go spaces
already have moderators; this change to the CoC acknowledges their authority
and places the group in a purely advisory role. If an incident is
reported to the group we may provide information to or make a
suggestion the moderators, but the Working Group need not (and should not) have
any authority to take disciplinary action.

In short, we want it to be clear that the Working Group are here to help
resolve conflict, period.

The second change made here is the removal of the anonymous reporting mechanism.
To date, the quality of anonymous reports has been low, and with no way to
reach out to the reporter for more information there is often very little we
can do in response. Removing this one-way reporting mechanism strengthens the
message that the Working Group are here to facilitate a constructive dialogue.

Change-Id: Iee52aff5446accd0dae0c937bb3aa89709ad5fb4
Reviewed-on: https://go-review.googlesource.com/37014
Reviewed-by: Andrew Gerrand <395a7d33bec8475c9b83b7d440f141bcbd994aa5@golang.org>
Reviewed-by: Russ Cox <5ad239cb8a44f659eaaee0aa1ea5b94947abe557@golang.org>

codestation/go,CAFxX/go,akutz/go,akutz/go,derekmarcotte/go,polyverse-security/go,polyverse-security/go,vsekhar/elastic-go,golang/go,cloudflare/go,cloudflare/go,Cofyc/go,codestation/go,josharian/go,cloudflare/go,akutz/go,vsekhar/elastic-go,codestation/go,CAFxX/go,cloudflare/go,nawawi/go,codestation/go,akutz/go,cloudflare/go,codestation/go,cloudflare/go,josharian/go,akutz/go,vsekhar/elastic-go,codestation/go,derekmarcotte/go,Cofyc/go,polyverse-security/go,golang/go,nawawi/go,Cofyc/go,golang/go,josharian/go,linux-on-ibm-z/go,nawawi/go,ImJasonH/go,golang/go,derekmarcotte/go,vsekhar/elastic-go,josharian/go,linux-on-ibm-z/go,nawawi/go,ImJasonH/go,derekmarcotte/go,derekmarcotte/go,polyverse-security/go,polyverse-security/go,linux-on-ibm-z/go,derekmarcotte/go,nawawi/go,linux-on-ibm-z/go,Cofyc/go,CAFxX/go,josharian/go,josharian/go,CAFxX/go,nawawi/go,nawawi/go,cloudflare/go,ImJasonH/go,CAFxX/go,nawawi/go,cloudflare/go,linux-on-ibm-z/go,derekmarcotte/go,ImJasonH/go,ImJasonH/go,CAFxX/go,vsekhar/elastic-go,christopher-henderson/Go,vsekhar/elastic-go,codestation/go,linux-on-ibm-z/go,Cofyc/go,linux-on-ibm-z/go,golang/go,polyverse-security/go,polyverse-security/go,derekmarcotte/go,ImJasonH/go,codestation/go,golang/go,akutz/go,akutz/go,akutz/go,ImJasonH/go,vsekhar/elastic-go,CAFxX/go,Cofyc/go,Cofyc/go,Cofyc/go,golang/go,ImJasonH/go,golang/go,linux-on-ibm-z/go,josharian/go,CAFxX/go,vsekhar/elastic-go,josharian/go,polyverse-security/go