Add a Contributor/Member Code of Conduct
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
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DevBetterCom/DevBetterWeb
-
Remove duplicate Vimeo DI registration; use NimblePros.Vimeo AddVimeoServices and upgrade packageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DevBetterCom/DevBetterWeb#1486 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
DevBetterCom/DevBetterWeb#1472 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
DevBetterCom/DevBetterWeb#1393 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DevBetterCom/DevBetterWeb#1392 ·
Maintainers usually reply within 1 day
-
.NET enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
DevBetterCom/DevBetterWeb#1380 ·
Maintainers usually reply within 1 day
All issues in DevBetterCom/DevBetterWeb
Similar issues
-
area-NavigationView bug needs-triage team-Controls
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/microsoft-ui-xaml#12671 · 3 comments ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Improve time codes: status hint doesn't mention the new Shift+F7 / Shift+F8 "to check" navigationOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
SubtitleEdit/subtitleedit#16943 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elsa-workflows/elsa-core#9273 ·
Maintainers usually reply within 1 day