I don't understand why TPF is having so much difficulty with this. In other language communities this is (seemingly) a solved problem.
See for example Rust's Code of Conduct policy.
Then there's the Contributor Covenant (by none other than our dear Coraline),
which has been adopted by many open source communities ... but not Perl. :-/
| [reply] |
For cheap thrills, I just did a Super Search for Code of Conduct at Perl Monks:
AFAICT, vroom didn't pursue this topic further after Nov 2000. Is that right?
I've almost certainly missed other useful PM references, so if anyone knows of other Perl Monks Code of Conduct
references, please let me know
so I can update Organizational Culture (Part V): Behavior.
| [reply] |
| [reply] |
Grunging around for some prior art...
From the Slashdot FAQ:
"Slashdot discussions are and should be robust; only cry "Abuse!" for comments that are utterly without redeeming value: spam, racist ranting, etc. For everything else, use the other moderation options.
Reported comments will be reviewed and moderated by the editors, if appropriate."
"If a single user is moderated down several times in a short span, a temporary ban will be imposed on that user -- a cooling off period, if you will."
From the Slashdot Terms of Use:
The user, and not Slashdot Media, is entirely responsible for all content that the user uploads, posts, emails, or otherwise transmits via the site.
No user shall transmit content or otherwise conduct or participate in any activities on the site which, in the judgment of Slashdot Media, is likely to be prohibited by law in any applicable jurisdiction...
Slashdot Media reserves the right, in its sole and absolute discretion,
to refuse or delete any content at any time, [and]
to refuse or delete any content that it reasonably considers to violate this agreement or be otherwise illegal or does not fulfill the purpose.
By posting content to any area of the site, you grant us non-exclusive, royalty-free, perpetual, irrevocable right to link to, reproduce, distribute, adapt, create derivative works of, publicly display, or otherwise use such content...
You retain ownership of any copyrights in any content you submit.
The Perl5porters (p5p) mailing list has a Standards of Conduct policy.
(Ricardo Signes' original draft SoC was posted
in perl.standards.of.conduct.discuss, which saw a grand total of 7 messages, all in July 2014.)
irc.perl.org has a pretty nice SoC document.
The Mojolicious developer community has a fairly extensive Code of Conduct policy.
(This is linked in Is there a place on PM outlining community policy, which in turn is linked in Spirit of the Monastery. The latter has interesting comments regarding the Rule of St. Benedict.)
I reckon we are the only monastery ever to have a dungeon staffed with 16,000 zombies.
| [reply] |
Her partner was the guy publishing packages with racist names. Reports got deleted by the powers that be, until screenshots were posted in public | [reply] |
Again, I'm depressed
read fiction instead?
| [reply] |