Add a Contributor/Member Code of Conduct

Open
#1,099 2 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Start with the completed checklist in this issue, the publicly accessible Code of Conduct URL, and the read-me-first Discord channel reference. Announce the adoption to existing members through Discord and the next coaching call; the work is done when both announcements have been made and the issue checklist is updated.

Written by the indexing model from the issue text.

Description

As the group grows and matures it's important to ensure everyone including current and future members feel welcome. To that end I'm planning on adding an explicit Code of Conduct to the group.

I've been researching existing Codes of Conduct used by different communities, open source organizations, and conferences. This one appears to be a mature and well-established option that is designed for adoption by third parties (like devBetter).

https://www.contributor-covenant.org/version/2/1/code_of_conduct/

In terms of implementation steps, I'm looking at the following:

  • Adapt the text and update it as needed for our organization and points of contact (i.e. me).
  • Host the content on the website in a publicly accessible URL
  • Update the read-me-first channel in Discord to reference the CoC by URL
  • Announce the existence of the CoC and its adoption to all existing members via Discord and next coaching call

For future consideration:

  • Consider requiring members to state they've read and agree to abide by the CoC as part of onboarding

Other suggestions? Leave a comment below.

Dominant language
C#
Stars
157
Forks
59
Avg merge
3h 12m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DevBetterCom/DevBetterWeb

All issues in DevBetterCom/DevBetterWeb

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.