-
Notifications
You must be signed in to change notification settings - Fork 220
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
Add Mozilla Code of Conduct #4864
Add Mozilla Code of Conduct #4864
Conversation
_(Message COC002)_
We've already got one: https://github.com/mozilla-services/socorro/blob/master/CODE_OF_CONDUCT.rst Thank you! |
Will,
FYI, you'll get nagged every time you rerun, as the official version is in
markdown. If you don't have a strong reason for keeping as
reStructuredText, please consider going with the markdown version.
…--Hal
On Wednesday, March 27, 2019 at 1:06:42 PM UTC-7, Will Kahn-Greene wrote:
Closed #4864 <#4864>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4864 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/At2KdrKz4s5wNaWlrzeEWPeNxkfdUec3ks5va89NgaJpZM4cOoOy>
.
|
That's kind of frustrating and unfortunate. |
@willkg - actually, I take it back. You'll need to change. The |
That surprises me since GitHub supports non-.md formats for other files also in that list and there are lots of other projects on GitHub that have .rst files. If projects are using .rst and Sphinx for documentation, it's easy to include .rst files elsewhere in the repository using the I'll look into it and if it turns out they really don't support |
So, it looks like it doesn't have to do with the .rst format but rather that the file is not one of the ones GitHub recognizes. django-badger has the CODE_OF_CONDUCT.md file, but it's also listed as not having one in the insights page:
Here's the most recent thing I found about that: If showing up in the insights tab is important, maybe we should use one of the ones they support? Maybe we should contact them and get ours added? |
@willkg that discussion should happen with mozilla-github-standards@m.c -- those folks would be the ones to take any such action or change policy. |
So, it looks like it doesn't have to do with the .rst format but rather that the file is not one of the ones GitHub recognizes. Right. And to make maintenance sustainable in future. |
@willkg @hwine can you CC me on the thread w/ moz-gh-stds or point me to any public discussions? My understanding is there are two issues:
The benefit of |
@hwine pointed me to the CoC bot script at: https://github.com/mozilla/github-org-scripts/blob/master/check_CoC.py edit: and the requirements are at https://wiki.mozilla.org/GitHub/Repository_Requirements and in https://github.com/mozilla/repo-templates |
@g-k fyi, script moved to https://github.com/mozilla/Mozilla-GitHub-Standards/ |
Reopening to land this. |
On second thought--I'm going to cherry-pick the commit and start a new branch and PR. |
As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:
If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to Mozilla-GitHub-Standards+CoC@mozilla.com.
(Message COC002)