-
Notifications
You must be signed in to change notification settings - Fork 8
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
Contributor Code of Conduct #13
Comments
I agree with their language. And I like the consistency of adopting a standard CoC instead of reinventing the wheel. |
After first read, I'd want to stay away from language like "...with dramatically low participation." Because it's not false, but it's too easily read as putting the blame on our choice, rather than on whether participation even feels possible. |
(Fwiw, submitted a PR for them to change that line.) But otherwise agree re: adopting it as a shared standard. If we have modifications, we can suggest them to the community that uses the CoC before committing to forking something for ourselves. |
If I'm not mistaken, the wording we're considering adopting is http://contributor-covenant.org/version/1/4/, so it doesn't talk about "dramatically low participation". Sorry if I'm telling you something you already know @bradleyfields :) I think we should adopt this CoC, and consider supplementing it as well since this is not a typical open source project. But I think putting this into place as soon as possible would be great.
This clause seems like it would allow people to (for example) publicly tweet horrible things as long as it's from their personal account. If people agree that this type of scenario would be unacceptable for this group, maybe we can at least further define "Representation of a project" for our case. |
Oh, sorry. Realize now it wasn't clear whether I was talking about the CoC itself or the text on http://contributor-covenant.org/ that introduces it. Also agree that that clause could use some work. Though, I'd suggest that there shouldn't be a project representation requirement at all. (Maybe that's your point too, @cottser.) |
@bradleyfields @cottser It raises questions for me:
It seems easier to establish some guidelines for this before a situation arises rather than in the midst of one. |
How about changing the start of the clause to this?
And then adding something after that paragraph—something that speaks to conduct not done as representation of the community or project. E.g., someone, via their personal social account, could publicly behave in a way that violates the CoC's spirit. It'd start something like:
Could borrow from Twitter's reporting mechanism for examples. |
I agree that this covenant isn't perfect as is. I also would like to adopt something sooner rather than later. https://drupaldiversity.github.io/get-involved/ endorses the 1/4 version as our CoC. I'm marking this as closed only because we have a CoC now, but I don't think the conversation has to end on tweaking it or adding to it as our needs change and as situations inevitably arise. I'm also not sure quite where this stuff should live, so perhaps when the time comes to revive this, we can do it as a PR on the website. Thanks @bradleyfields @cottser @rubyji for weighing in on this. |
Reopening this for comment in light of recent issues... |
Opensource.com has a great article on tips for increasing diversity in open source projects. The article recommends the Contributors Covenant. There are a lot of really good reasons to use it and not a lot of down sides. I think that this document would have covered the recent kerfuffle. Understand, you can always extend this document with project specific amendments. In addition to the Contributor's Covenant, you are expected to.... https://opensource.com/life/16/3/creating-welcoming-and-inclusive-open-source-space |
I've added PRs against each project to add a CODE_OF_CONDUCT.txt file that just copies the text from the existing drupaldiversity site. |
Added CODE_OF_CONDUCT.txt file per #13.
Since a code of conduct has been added to each repo - thank you @damienmckenna - can we close this issue for now @drnikki ? |
Can we get behind using http://contributor-covenant.org/ or would we like to modify/enhance it for our purposes?
The text was updated successfully, but these errors were encountered: