Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review community guidelines #613

Open
Skud opened this issue Dec 24, 2014 · 2 comments
Open

Review community guidelines #613

Skud opened this issue Dec 24, 2014 · 2 comments

Comments

@Skud
Copy link
Contributor

Skud commented Dec 24, 2014

Since we first created our Community Guidelines, a number of open source (and related) projects have also created codes of conduct for their communities. Some of these may be better than ours, or have aspects we want to consider using.

History of our Community Guidelines: I decided we should have them very early on, so I wrote something, ran it past the people then active in the community, and posted it (original version: August 19th 2012; the project had kicked off at the end of July.) I took some inspiration from [Dreamwidth's diversity statement] and some from the Geek Feminism Anti-Harassment Policy and associated resources.

Criticism of current guidelines: personally the one thing that makes me twitch the most is the "be excellent to each other" at the end. Since first writing that, the phrase has come to be a shorthand example of how not to write a code of conduct. That is to say, a bad CoC says only "be excellent to each other", while a good one explains what that means, and also what bad behaviour is, how to report bad behaviour, and what the consequences are for behaving badly. Ours does all those things but then ends with "be excellent", which might be misconstrued or something. In any case it makes me uncomfortable now.

Anyway. At the very least I'd like to look at some other CoCs, see what is current "best practice", and bring our CGs into line with that if necessary.

Here are some to look into:

NB, CoCs based on Ubuntu's, which emphasise desirable positive behaviours ("be excellent to each other") without specifying undesirable negative behaviours, do not meet my current understanding of best practice; in practice, such CoCs are often used to tone police people who want to address negative behaviour. (These CoCs are mostly of an earlier generation, which didn't recognise harassment and marginalisation as systemic problems.)

Other background reading:

@pozorvlak
Copy link
Member

Initial thoughts, without having (yet) read any of the linked documents:

It's unfortunate that "be excellent to each other" has acquired that connotation, because I think it captures something important - beyond avoiding a specified list of disallowed negative behaviours and acting on a specified list of desired positive behaviours, we should strive to go above and beyond and be excellent to each other inventively, in ad-hoc ways that no pre-written list can hope to capture. It's good to include an explicit list of unacceptable behaviours and a parallel list of expected behaviours (as we do, though I dare say our lists could be improved upon), but we should make it clear that both lists are non-exhaustive, and should be followed in spirit rather than in letter.

@Skud Skud added this to the Backlog (test) milestone Jan 8, 2015
@Skud Skud modified the milestone: Backlog (test) Jan 16, 2015
@Skud Skud removed the when: soon label Jan 16, 2015
@Skud
Copy link
Contributor Author

Skud commented Mar 10, 2015

@Br3nda Br3nda added this to Backlog in Growstuff Apr 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Growstuff
  
Backlog
Development

No branches or pull requests

2 participants