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]
ma...@gmail.com <ma...@gmail.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.
da...@gmail.com <da...@gmail.com> #7
There's also the Citizen Code of Conduct at http://citizencodeofconduct.org/ , of which we're using a modified variant of an older version at coreboot (our CoC is at https://doc.coreboot.org/community/code_of_conduct.html ).
Our modifications mostly centered around
1) being explicit that the CoC must not be weaponized (a recurring fear was that it can be used to force eject people on pretenses. Apparently that's a common concern with the "Covenant" as well)
2) a different enumeration style of expected/forbidden behavior: Most CoC (at the time) seemed to adopt a style of listing what exactly is not acceptable and there was some opposition to that, primarily in the non-US segments of our community. Acceptance grew when we stated general principles (that are more abstract than in most CoCs and less clear cut) and examples (more concrete, similar to the enumerations in other CoCs, but designated as examples so they can't be mistaken for a closed set, arguably leaving everybody not mentioned there vulnerable).
3) To not use a mailing list as point of contact. Mailing lists have the issue that it's not apparent who's subscribed there (can be fixed by posting a list somewhere, but that needs to be maintained) and that past cases can be visible to future community managers (e.g. current folks are nice folks and I trust them to handle a complaint against person X, but unfortunately the following year X's best buddy ends up being community maintainer and gets to see all the juicy details in the complaint like witness statements that X gets to hear about and can use to retaliate).
Note that I wouldn't recommend adopting coreboot's CoC wholesale, as it's a compromise document that was made to work for us. However, since I was involved in that discussion I wanted to bring up both the option of adapting a CoC for your community, and some of the concerns raised and how we dealt with them.
Our modifications mostly centered around
1) being explicit that the CoC must not be weaponized (a recurring fear was that it can be used to force eject people on pretenses. Apparently that's a common concern with the "Covenant" as well)
2) a different enumeration style of expected/forbidden behavior: Most CoC (at the time) seemed to adopt a style of listing what exactly is not acceptable and there was some opposition to that, primarily in the non-US segments of our community. Acceptance grew when we stated general principles (that are more abstract than in most CoCs and less clear cut) and examples (more concrete, similar to the enumerations in other CoCs, but designated as examples so they can't be mistaken for a closed set, arguably leaving everybody not mentioned there vulnerable).
3) To not use a mailing list as point of contact. Mailing lists have the issue that it's not apparent who's subscribed there (can be fixed by posting a list somewhere, but that needs to be maintained) and that past cases can be visible to future community managers (e.g. current folks are nice folks and I trust them to handle a complaint against person X, but unfortunately the following year X's best buddy ends up being community maintainer and gets to see all the juicy details in the complaint like witness statements that X gets to hear about and can use to retaliate).
Note that I wouldn't recommend adopting coreboot's CoC wholesale, as it's a compromise document that was made to work for us. However, since I was involved in that discussion I wanted to bring up both the option of adapting a CoC for your community, and some of the concerns raised and how we dealt with them.
ek...@google.com <ek...@google.com> #8
is...@google.com <is...@google.com> #9
Based on Contributor Covenant: https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
- Google OpenSource:https://opensource.google.com/docs/releasing/template/CODE_OF_CONDUCT/
- Eclipse (proposed adoption of CoC 1.4):https://github.com/eclipse/.github/blob/39f8944218743bb7649d6fc43c1cf8be9e23b6da/CODE_OF_CONDUCT.md
- Linux kernel:https://www.kernel.org/doc/html/latest/process/code-of-conduct.html
-https://golang.org/conduct#scope
other CoCs:
- Apache:https://www.apache.org/foundation/policies/conduct.html
- CNCF:https://github.com/cncf/foundation/blob/master/code-of-conduct.md
- Ubuntu:https://ubuntu.com/community/code-of-conduct
- opensourcedesign:https://opensourcedesign.net/code-of-conduct/
- Google OpenSource:
- Eclipse (proposed adoption of CoC 1.4):
- Linux kernel:
-
other CoCs:
- Apache:
- CNCF:
- Ubuntu:
- opensourcedesign:
Description