Obsolete
Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
Beside the relevant candidate ones previously mentioned by @Matthias, Chromium also has this one ([1]) below. It is the one linked from Monorail's New issue submission form that you likely noticed already:
[1]https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md
[1]
ma...@gmail.com <ma...@gmail.com> #3
Examples
Contributor Covenant:https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
Apache:https://www.apache.org/foundation/policies/conduct.html
Eclipse:https://wiki.eclipse.org/Eclipse_Code_of_Conduct
Linux kernel:https://www.kernel.org/doc/html/latest/process/code-of-conduct.html
Google OpenSource:https://opensource.google.com/docs/releasing/template/CODE_OF_CONDUCT/
golang:https://blog.golang.org/conduct-2018
Ubuntu:https://ubuntu.com/community/code-of-conduct
CNCF:https://github.com/cncf/foundation/blob/master/code-of-conduct.md
opensourcedesign:https://opensourcedesign.net/code-of-conduct/
Discussions, research
https://internethealthreport.org/2019/codes-of-conduct-in-open-source-communities/
TODO group:https://github.com/todogroup/opencodeofconduct
OSI:https://opensource.org/codeofconduct
research paper:https://www.win.tue.nl/~aserebre/SANER2017.pdf
Arguments against:
https://sandfox.me/misc/rejecting-contributor-covenant.html
https://itsfoss.com/linux-code-of-conduct/
https://dancerscode.com/2018/07/25/why-the-open-code-of-conduct-isnt-for-me/
Contributor Covenant:
Apache:
Eclipse:
Linux kernel:
Google OpenSource:
golang:
Ubuntu:
CNCF:
opensourcedesign:
Discussions, research
TODO group:
OSI:
research paper:
Arguments against:
ma...@gmail.com <ma...@gmail.com> #4
Now that https://crbug.com/gerrit/10972 is done or being reviewed, I now propose to formally start this very one.
-So that we could maybe consider reviewing this during our next /upcoming meetup.
Would you recommend any specific CoC above, in particular, for our CM review @Matthias?
(Thanks for this.)
-So that we could maybe consider reviewing this during our next /upcoming meetup.
Would you recommend any specific CoC above, in particular, for our CM review @Matthias?
(Thanks for this.)
ek...@google.com <ek...@google.com> #5
[Empty comment from Monorail migration]
is...@google.com <is...@google.com> #6
1. @Matthias to order the above list(s).
2. Hereby CMs to get familiar with its top.
3. CMs to agree on which Code to recommend.
4. CMs to agree with the ESC on that proposal.
5. CMs and ESC to agree with the maintainers.
6. CMs to agree/share with the whole community.
2. Hereby CMs to get familiar with its top.
3. CMs to agree on which Code to recommend.
4. CMs to agree with the ESC on that proposal.
5. CMs and ESC to agree with the maintainers.
6. CMs to agree/share with the whole community.
Description
[1]