Skip to content
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

Adapt a Code of Conduct. #488

Open
tkwidmer opened this issue Jul 19, 2018 · 10 comments
Open

Adapt a Code of Conduct. #488

tkwidmer opened this issue Jul 19, 2018 · 10 comments

Comments

@tkwidmer
Copy link
Contributor

We are being included in Github's Social Impact Collection. But they are asking us to add a code of conduct. This is something we should have probably already done.

Github's overall document about Code of Conducts: https://opensource.guide/code-of-conduct/

Contributor Covenant: https://www.contributor-covenant.org/version/1/4/code-of-conduct.md

The contributor Covenant is a drag and drop code of conduct we can start using until we want to make any changes to it.

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 19, 2018

Edit to add: Thanks for tagging me on this! I'd be glad to add my 2 cents and help make this happen.

Sounds good to add a code of conduct.

Assuming we put a lot of thought into picking or making one, I think off the top of my head ours should:

  • Read similarly to how we already actually feel about contributions and contributors* (or where the code of conduct and our status quo differs, where we reasonably aspire for our outlook to be, toward contributors and contributions)
  • Be encouraging and welcoming
  • Be helpful when we need to give a reason for moderating contributions or helpful when explaining to folks why we'd like them to reconsider or change their behavior (so, clear and easy to understand and reasonable rules in the code of conduct. And not so vague that people would dispute that they're even breaking the rules.)

I think there are a lot of good ones out there, so this shouldn't be too hard IMO.


Laying out my personal thought a bit:

Realistically I think a Code of Conduct is mostly a backstop for when relying on basic generosity and common sense as a maintainer/moderator breaks down and it's unclear how to respond or proceed. [Edit to add: This is because in my view most activity is going to fall in line with the Code of Conduct organically without needing to expressly invoke it in those given situations. Most people will mean well and behave well irrespective of the Code of Conduct.] It also dissolves arguments based on trolls saying moderation is too severe, unfair (especially "unfairly targeted" at them) or over-reactive -- it sets the tone and the bar for everybody fairly. (And idealistically, it really does encourage a thoughtful and proactive and positive approach to moderation/maintainership/contributions, and make everyone feel secure in the way the community/social aspect of a project will play out.)

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 19, 2018

As a tiny additional, personal comment: I like Mozilla a lot, and I think their culture is great. Pasting their code of conduct for reference purposes...

Community Participation Guidelines (Kinda huge and more specific to a large corporation with lots of passionate fans and contributors, but I like what's there.)

Bugzilla Etiquette (Their code of conduct on their issue/bug tracker site)

I am assuming outright the other ones linked above are more appropriate for our needs, but I'll be checking those out now to see, and I'm already familiar with the Mozilla ones. Just wanted to bring these up since I am a fan of Mozilla's culture.

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 19, 2018

I do think the Contributor Covenant is really good. It might not be adjusted for the exact tone or spirit of this project, but it's solid and sets the right general expectations and such without, as far as I can see, leaving anything out.

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 19, 2018

Example commit (on its own branch at the moment) adding the Contributor Covenant without changes: 66a6471

(Well, no changes other than putting in our specific contact email.)

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 23, 2018

Hi @tkwidmer,

Do we have a time frame that we should do this by?

And if any other project members (or contributors more generally) have thoughts, those are certainly welcome. It is easy enough to change this later, if we have ideas and improvements later on. So if we need to apply this in order to be available to the GitHub collection, we can change to a better code later down the line. -- (if there is a better code to change to).

@tkwidmer
Copy link
Contributor Author

@DeeDeeG Just got a timeframe from Github. We need to address this within the week.

I think it's pretty easy and straightforward to change this later if we want to improve on it. My proposal is we add the Contributor Covenant pretty much as is for now from your commit here 66a6471. This will allow us to be added to the Github Collection again and then we can change the code at a later date once more people have had the chance to give some input (@mi-wood and others).

Can you open a PR to merge that commit? And add a link to it in the README and CONTRIBUTING?

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 25, 2018

Can you open a PR to merge that commit? And add a link to it in the README and CONTRIBUTING?

Sure. Will do this evening.

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 25, 2018

Other things came up, so while I will be able to add the code of conduct to README.md and CONTRIBUTING.md later, I unfortunately can not finish that up this evening. Expecting to get a chance in the next couple of days. If anyone wants to do this before I get to it, that's totally fine also. Regards.

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 27, 2018

There are PRs for this now.

#490, #491.

@DeeDeeG
Copy link
Contributor

DeeDeeG commented Jul 29, 2018

This was auto-closed by PR #490, but will keep open for now. This is a good place for any feedback or suggestions from contributors/the community.

@DeeDeeG DeeDeeG reopened this Jul 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants