Create CODE_OF_CONDUCT.md: a political tool to refer to prior following its rules and guidelines
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Review issue #1719 and the deleted CODE_OF_CONDUCT.md from commit fb4bdc0ce223039bcbffe51c1d8af53d9fe99e7e. Follow the discussion and prior suggestions before drafting; this is done when the community agrees on the content and a CODE_OF_CONDUCT.md is added.
Written by the indexing model from the issue text.
Description
#1719 initial commit was such an attempt. Recent events under Heads matrix channel, where multiple usernames having the same writing style, asking irrelevent questions over days and not respecting many of its channel requests to use threads, and stay focus on topic now justifies revisiting and creating such code of conduct file to refer to.
Today was the fist banning of such user. I acted with patience with all past occurences of what appears to be trolling, while old usernames are replaced by newer usernames and I have no personal experience dealing with trolling. My intuition is that banning one will make two come. Unfortunately, the channel has only two moderators and only one of them is active: me. So not sure how to deal with this in a sustainable way, so this issue is an attempt to track pervious and now current suggestions, which I will organize on this OP post after discussions with the community. Expect multiple editions.
Some history:
- #1719 was initially introducing a code of conduct, but received pushbacks.
- Such CODE_OF_CONDUCT was removed from #1719 in commit https://github.com/linuxboot/heads/commit/fb4bdc0ce223039bcbffe51c1d8af53d9fe99e7e, where the the deleted content can be read at https://github.com/linuxboot/heads/blob/138a41db179e8e11b542a7ddf47b120dcacfd536/CODE_OF_CONDUCT.md
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 6
Getting set up
- No 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 linuxboot/heads
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
help wanted security SMM upstream
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 76/100
EchoTools/nevr-runtime#110 ·
Maintainers usually reply within 1 day
-
Device Details tables: FS/SF columns contradict each other (nfet_01v8 Vt row, pfet_01v8 Idsat row)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google/skywater-pdk#450 ·
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
databendlabs/databend-docs#3511 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chingu-voyages/V62-tier3-team-33#285 ·
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lirantal/discoprint#36 ·
Maintainers usually reply within 1 day