Code of Conduct Rewrite

[aimaismog]

This has been a project that has been proposed internally several times, but was formally started after our meeting back in October. Most of the progress was done this month, however.
By this point, almost everything should be done by now. Thus, the goal is to release this by January 1st, 2026.

The goals for this rewrite are as currently followed:

• Patch any noticeable holes in the rules and add or expand rules as necessary
• Merge or completely remove repeated rules, contradictory statements, and things that go against our values
• Slim down and clarify the Code of Conduct
  • Helps makes things easier to read
  • Some things like LQ were not previously defined
  • Rules like Mutual Respect (now 1.2) were too large
  • Grey areas should not be present

Section 3 is likely to be completely redone and renamed to Special Cases. Anything removed is to be moved to other documents or put into section 4, which will be Extensions.
Internal discussions should move to here somewhat soon.

[aimaismog]

Further changes likely to be in next revision, waiting on reviews.

[coderabbitai]

Actionable comments posted: 7

♻️ Duplicate comments (4)

code_of_conduct/sections/3.toml (1)

104-105: Format the bare URL as a markdown link.

This issue was already flagged in a previous review. The appeals URL should be formatted as a proper markdown link for consistency.

Suggested fix

-Appeals currently are managed via Wick and can be accessed at https://appeals.wickbot.com/. You will need to use our server ID (1172245377395728464) to submit an appeal.
+Appeals currently are managed via Wick and can be accessed at [appeals.wickbot.com](https://appeals.wickbot.com/). You will need to use our server ID (1172245377395728464) to submit an appeal.

code_of_conduct/sections/2.toml (1)

42-42: Minor punctuation inconsistency.

This was already flagged in a previous review. Line 42 is missing a period at the end, while other bullet points in this list have periods.

Suggested fix

-* Do not encourage illegal actions or behavior
+* Do not encourage illegal actions or behavior.

README.md (2)

23-24: Broken anchor links due to special characters.

This was already flagged in a previous review. The anchor links contain special characters that won't resolve correctly:

• Line 23: #13-controversial,-sensitive-and-unfit-topics (comma)
• Line 24: #14-respecting-authority-&-rules (ampersand)

The fix should be applied in the template file code_of_conduct/templates/README.md.jinja to sanitize anchor links by removing commas and ampersands.

---

258-258: Bare URL should be formatted as a markdown link.

This was already flagged in a previous review. Since the README is generated from 3.toml, fixing the source file will resolve this.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b99a46c and eed1481.

📒 Files selected for processing (5)

• README.md
• code_of_conduct/sections/1.toml
• code_of_conduct/sections/2.toml
• code_of_conduct/sections/3.toml
• code_of_conduct/templates/README.md.jinja

🚧 Files skipped from review as they are similar to previous changes (1)

• code_of_conduct/templates/README.md.jinja

🧰 Additional context used

🪛 LanguageTool

README.md

[style] ~73-~73: ‘on the basis of’ might be wordy. Consider a shorter alternative.
Context: ...rs should also avoid disparaging others on the basis of their choices, be it their choice of op...

(EN_WORDINESS_PREMIUM_ON_THE_BASIS_OF)

---

[style] ~96-~96: This phrase might be unnecessarily wordy.
Context: ...ation but the mentioning of said topic. Our aim is not to suppress free speech but to keep...

(MY_HOPE_IS)

---

[style] ~147-~147: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ox members, or make attempts at such. * Do not share, request access to, or distri...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~148-~148: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...tware, media, or copyrighted content. * Do not discuss or promote software crackin...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~149-~149: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...y methods of copyright circumvention. * Do not encourage illegal actions or behavi...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~155-~155: Consider replacing this phrase with the adverb “naturally” to avoid wordiness.
Context: ...d projects are only permitted if shared in a natural manner. Communities should only be promoted i...

(IN_A_X_MANNER)

---

[style] ~167-~167: ‘Any and all’ might be wordy. Consider a shorter alternative.
Context: ...icket. Otherwise, ping the %wheel role. Any and all problems are discussed as a group among...

(EN_WORDINESS_PREMIUM_ANY_AND_ALL)

---

[style] ~174-~174: This phrase is redundant. Consider using “outside”.
Context: ...in this document or misusing the server outside of what is listed, the community may reque...

(OUTSIDE_OF)

---

[style] ~179-~179: This phrasing can be wordy.
Context: ...l changes and actions within the server as well as all moderator actions such as punishmen...

(AS_WELL_AS_AND)

---

[grammar] ~194-~194: Use a hyphen to join words.
Context: ...t by a member. #### Automod Basic auto moderation will exist in this server to ...

(QB_NEW_EN_HYPHEN)

---

[grammar] ~208-~208: Ensure spelling is correct
Context: ...answer their ticket after 48 hours. * Snippetban * Snippetbans are a punishment that can be temporary ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[style] ~228-~228: Consider using a more concise synonym.
Context: ... Problematic behavior can be defined by a variety of factors. This includes, but not limited...

(A_VARIETY_OF)

🪛 markdownlint-cli2 (0.18.1)

README.md

21-21: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

22-22: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

23-23: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

23-23: Link fragments should be valid

(MD051, link-fragments)

---

24-24: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

24-24: Link fragments should be valid

(MD051, link-fragments)

---

26-26: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

27-27: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

28-28: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

29-29: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

31-31: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

32-32: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

---

258-258: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (7)

code_of_conduct/sections/3.toml (2)

1-9: LGTM on title and Reporting rule.

The title rename to "Special Cases" and the updated Reporting guidance are clear. The distinction between ticket creation for non-urgent issues vs. pinging %wheel for urgent matters provides actionable guidance for members.

---

11-15: LGTM on Accountability rule.

The rename from "Consistency" to "Accountability" better reflects the rule's intent, and the scope expansion to include staff is appropriate.

code_of_conduct/sections/2.toml (2)

10-32: LGTM on Server Conduct consolidation.

The restructured Server Conduct rule with subsections (2.2.a Chat Quality, 2.2.b Voice Channels, 2.2.c Channel Use) provides clear, organized guidance. The definition of "LQ" (low quality) addresses a previously undefined term mentioned in the PR objectives.

---

46-55: LGTM on Advertising rule.

The updated advertising guidance is clearer, with explicit examples (Arch, Debian, Fedora) and a reference to the Projects forum for artificial promotion.

README.md (1)

265-269: LGTM on Notice section updates.

The clarification that section numbers may change over time and that citing a section doesn't imply its subsections is helpful for avoiding confusion during moderation.

code_of_conduct/sections/1.toml (2)

4-16: LGTM on SFW Policy restructuring.

The renamed "Appropriate Conduct and SFW Policy" with subsections 1.1.a and 1.1.b provides clearer structure. The expanded definition of NSFW and explicit prohibition on profile-based content (About Me, banner, status, guild tag) addresses potential grey areas.

---

54-65: Verify that minor safety rules have been intentionally relocated or will be addressed.

A previous review flagged that critical safety rules concerning minors (prohibitions on grooming, predatory behavior, age requirements) were removed from section 1.2. The AI summary confirms the deletion of the entire "Concerns of Age and Appropriate Conduct" section.

Please confirm one of the following:

1. This content has been moved to Discord's ToS/Community Guidelines reference (line 46 of README mentions "If something major is missing, it's likely within Discord's ToS")
2. This content will be added to the "Extensions" document mentioned in the PR objectives
3. This was an intentional policy decision

If relying on Discord's ToS, consider adding an explicit note that minor safety protections are enforced per Discord's policies.