Skip to content
New issue

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

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

Already on GitHub? # to your account

doc: cover moderation of IRC, mail, and slack channels #122

Closed
wants to merge 1 commit into from

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented Jul 31, 2016

the moderation policy currently does not explicitly cover officially supported communications channels such as IRC, Slack, Email or Conference Calls. This is a first pass at covering such channels.

/cc @nodejs/tsc

@Fishrock123
Copy link
Contributor

The existing moderation policy does not work well for IRC for the various reasons which I have previously stated in nodejs/inclusivity#138

@jasnell
Copy link
Member Author

jasnell commented Jul 31, 2016

As I said, this is a first pass. Feel free to suggest additional edits that would improve the applicability for IRC.

@Fishrock123
Copy link
Contributor

Fwiw attempting to enforce this policy on irc would be extremely impractical and I refuse to do it for #node-dev.

@jasnell
Copy link
Member Author

jasnell commented Aug 1, 2016

@Fishrock123: Do you have specific recommendations on how the moderation policy can be improved to adequately cover IRC (in your opinion). Specific recommendations would be far more useful than a refusal to enforce a policy that we both agree is currently inadequate.

@Fishrock123
Copy link
Contributor

Fishrock123 commented Aug 1, 2016

An irc specific policy that includes the following (and other things I am probably forgetting):

  • Who OPs are
    • proper OP permissions on freenode
  • How to time people out (properly, including a history message)
    • Temporary timeouts
  • when to just kick people
  • irc specific offences
    • such as people joining/leaving rapidly
    • excessive use of channel notifications
  • how to check the access logs

@jasnell
Copy link
Member Author

jasnell commented Aug 1, 2016

I will work up some proposed language based on http://nodeirc.info/, http://blog.izs.me/post/30036893703/policy-on-trolling and https://gist.github.com/maxogden/8610086 to begin addressing the IRC specific requirements.

That said, many of the same requirements likely also apply to Slack channels, and other official communications channels may also have a number of channel specific requirements. I will see what I can do to begin addressing those as well.

@Fishrock123
Copy link
Contributor

Untagging until progress is made

@jasnell
Copy link
Member Author

jasnell commented Aug 11, 2016

+1 .. thank you, I'd meant to do so but forgot. Appreciate it.

@jasnell
Copy link
Member Author

jasnell commented Feb 1, 2017

Closing this in favor of the ongoing community work group direction.

@jasnell jasnell closed this Feb 1, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants