-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
website: document the no-me-too policy #14888
Comments
I wrote this: https://github.com/golang/go/wiki/NoMeToo Thoughts? @ianlancetaylor @rsc ? |
@adg, should we link that from somewhere else? Although most people arriving at a github issue and me-tooing it will probably be arriving there from a direct link or search, so linking it from e.g. https://golang.org/doc/contribute.html might not be too effective. Still, can't hurt. We can also just let people of the policy by cc'ing them from this bug if/when we delete comments. |
I think we should do this, at least. But I don't see much point in documenting it elsewhere, because people who do this aren't going to read our contribution guidelines. |
I'd like advice on this text with regard to tone. I don't want it to come across as passive aggressive. |
The text you wrote on the wiki LGTM. |
@adg That wiki page currently says:
That is no longer true, it's now possible to sort issues by most reactions. E.g.: https://github.com/golang/go/issues?q=is%3Aopen+is%3Aissue+sort%3Areactions-%2B1-desc |
@shurcooL oh, that's great! I've replaced the paragraph you quoted with this text:
|
@adg and I realized our "no-me-too" policy has only ever been "documented" in the golang-dev mailing list. Let's make it more official.
The text was updated successfully, but these errors were encountered: