Community Guidelines update #1528

Merged
Jade merged 6 commits from jade/community-guidelines into main 2026-03-29 18:25:40 +00:00
Owner
No description provided.
docs: Replace Contributor Covenant with community guidelines
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Failing after 53s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m3s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m44s
abe9944082
@ -8,3 +5,1 @@
These guidelines apply to all Continuwuity spaces, including our Matrix rooms and any other
community channels that reference them. We've written these guidelines to help us all create an
environment where everyone feels safe and respected.
Our project aims to make Matrix more accessible and inclusive for everyone. To that end, we are dedicated to fostering a positive, supportive, safe and welcoming environment for everyone: our community.
Contributor

everyone: our community.

This reads a little odd to me? Just a nitpick anyways.

> everyone: our community. This reads a little odd to me? Just a nitpick anyways.
Author
Owner

That was meant to read as our community being the environment we are fostering. I'll have a look to see if i can improve it in a bit

That was meant to read as our community being the environment we are fostering. I'll have a look to see if i can improve it in a bit
Contributor

It comes across more like you are saying everyone is our community :p

It comes across more like you are saying everyone is our community :p
Contributor

Arguably also "more accessible and inclusive for everyone. ... safe and welcoming for everyone". Ending the sentence with "everyone" twice is a bit weird?

Arguably also "more accessible and inclusive for everyone. ... safe and welcoming for everyone". Ending the sentence with "everyone" twice is a bit weird?
Contributor

s/for everyone: our community./for our community

Less redundant, and better scope, imo

s/for everyone: our community./for our community Less redundant, and better scope, imo
Jade marked this conversation as resolved
@ -32,1 +27,3 @@
ensure your messages can be easily understood by all. Avoid placing the burden of education on
ensure your messages can be easily understood by all.
4. **Be Considerate and Proactive**: Not everyone has the same time, resource and experience.
Contributor

Not everyone has the same time, resource and experience.

I am struggling to identify what you mean by this. I assume something along the lines of "Not everyone has the same amount of time, resources, or experience to spare." but in any case, this could use some rewording.

> *Not everyone has the same time, resource and experience.* I am struggling to identify what you mean by this. I assume something along the lines of "Not everyone has the same amount of time, resources, or experience to spare." but in any case, this could use some rewording.
Author
Owner

This is meant to be about both sealioning and those that react poorly when not given free support or feature development - in general those that ask for other people's time and energy in an inconsiderate way and are surprsed when they don't get more of it.

This is meant to be about both sealioning and those that react poorly when not given free support or feature development - in general those that ask for other people's time and energy in an inconsiderate way and are surprsed when they don't get more of it.
Contributor

That makes sense :) thank you for clarifying. It may be worth being more direct, then.

That makes sense :) thank you for clarifying. It may be worth being more direct, then.
@ -33,0 +27,4 @@
ensure your messages can be easily understood by all.
4. **Be Considerate and Proactive**: Not everyone has the same time, resource and experience.
Don't expect others to give up their time and labour for you - instead, be thankful for what you have already been given.
Contributor

(just a nick) Imo you could remove the "instead" and replace with a semicolon. Makes it two actionable commandments rather than one

(just a nick) Imo you could remove the "instead" and replace with a semicolon. Makes it two actionable commandments rather than one
Owner

Is this blocked on anything @Jade?

Is this blocked on anything @Jade?
Author
Owner

Just phrasing tweaks per review comments. Also fixing the merge conflict

Just phrasing tweaks per review comments. Also fixing the merge conflict
Jade force-pushed jade/community-guidelines from abe9944082
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Failing after 53s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m3s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m44s
to e5cfc503d8
Some checks failed
Check Changelog / Check for changelog (pull_request_target) Successful in 9s
Documentation / Build and Deploy Documentation (pull_request) Failing after 52s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m3s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
2026-03-29 18:21:12 +00:00
Compare
docs: Fix email link
Some checks failed
Check Changelog / Check for changelog (pull_request_target) Successful in 12s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m19s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m58s
Documentation / Build and Deploy Documentation (push) Successful in 1m25s
Checks / Prek / Pre-commit & Formatting (push) Successful in 3m7s
Checks / Prek / Clippy and Cargo Tests (push) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 12m23s
Release Docker Image / Build linux-amd64 (release) (push) Successful in 13m16s
Release Docker Image / Build linux-arm64 (release) (push) Successful in 11m7s
Release Docker Image / Create Multi-arch Release Manifest (push) Successful in 28s
Release Docker Image / Build linux-amd64 (max-perf) (push) Successful in 36m4s
Release Docker Image / Build linux-arm64 (max-perf) (push) Successful in 30m56s
Release Docker Image / Create Max-Perf Manifest (push) Successful in 21s
8b72c5eb11
Jade merged commit 8b72c5eb11 into main 2026-03-29 18:25:40 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1528
No description provided.