-
Notifications
You must be signed in to change notification settings - Fork 39
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
Update Code of Conduct #309
Comments
I gave it a try but sitting for an hour got me practically nowhere, I'm no good at this.
No where is it mentioned that a person has a right to free speech. It is said that the congress (representing the people) has an OBLIGATION to not prohibit nor interfere with other people's freedom of expression. |
Fixed by mimblewimble/site#222 |
Replace old CoC with a link to the website with the updated code of conduct. Related: mimblewimble/site#222 mimblewimble/grin-pm#309
Replace old CoC with a link to the website with the updated code of conduct. Related: mimblewimble/site#222 mimblewimble/grin-pm#309
A recent forum thread led me to review mimblewimble/grin/CODE_OF_CONDUCT.md and consider feedback raised by
@Kurt
in thread. The code has not materially changed since 2017, and I think there is room to improve. Specifically, these are a some (unpolished) thoughts:Not sure who has access to grinmods@googlegroups.com these days, needs investigating.
Currently, it's called "Grin Code of Conduct". This is ambiguous as it's the name of the repository it is located in and covers, but also a wider project "Grin" which can have multiple communities, GitHub organizations, and codes of conduct. We should try to avoid this confusion if we can, potentially by only calling it "Code of Conduct".
Since the code of conduct covers more than just the
mimblewimble/grin
repo, (also/grin-wallet/
,/site
, keybase, etc), we might consider moving it under the grin.mw website instead and pointing to it from various repos and locations (including/grin-pm
).Contains references to Gitter and IRC, but not keybase, or forum. It might make sense to not actually name specific tools or communities explicitly as that may change in the future. Instead, scope should probably any place where contributors to the
/mimblewimble/
org are and are acting as contributors of/mimblewimble
or something like that. I.e. it's less about which chat room you are in, and more about whether you are presenting yourself as a/mimblewimble
contributor. If you do, then there are some expectations about how you are meant to be conducting yourself, and if you violate them, you may not be welcome as a contributor any more. This needs more thought behind it and better wording.Not sure actual detailed moderation actions and steps should be in the CoC, and might be better left to the moderators themselves to define.
The contributor covenant it is based on is v1.3, and has since been updated to v2.0. It makes sense to review and refresh to remain up to date.
Overall if we can make the text more condensed and focused, it might become easier to read and more powerful.
The text was updated successfully, but these errors were encountered: