Skip to content
This repository was archived by the owner on Nov 9, 2017. It is now read-only.

Moderation and Issue Management within WG #41

Closed
zkat opened this issue Nov 18, 2015 · 11 comments
Closed

Moderation and Issue Management within WG #41

zkat opened this issue Nov 18, 2015 · 11 comments

Comments

@zkat
Copy link
Contributor

zkat commented Nov 18, 2015

We've been seeing a lot of issues with moderation come up recently, and it's worth discussing some specifics, and strategies for managing some of them. A list off the top of my head that I would at least like to bring up:

  • Managing brigades and hostile actors
  • Preventing multiple directed responses to individuals? ("dogpiling")
  • Other strategies for reducing overall temperature of discussions
  • Scope of Issue and PR usage in nodejs/inclusivity -- how much discussion should happen there vs WG meetings?
@Fishrock123
Copy link
Contributor

Related to nodejs/TSC#16

@nebrius
Copy link
Contributor

nebrius commented Nov 24, 2015

I'm going to do some research into banning at the repo, not org, level and I'll report my findings here.

@nebrius
Copy link
Contributor

nebrius commented Nov 24, 2015

#57 has been filed to help address some of these issues

@nebrius
Copy link
Contributor

nebrius commented Nov 26, 2015

So here's the results of the banning research: it's currently not possible to block at the repository level, only at the org level. Further, only org owners can block. They noted the request for maintainers to be able to block at the repository level for future conversations.

@nebrius
Copy link
Contributor

nebrius commented Nov 30, 2015

Results of the investigation: there is not currently a way to ban at the repo level, and it's not possible for someone other than an owner to ban people at the org level. sad face

@ghost
Copy link

ghost commented Dec 3, 2015

now that nodejs/TSC#16 has landed, the question if we should adopt the moderation policy or employ our own one is coming up. thoughts?

@zkat
Copy link
Contributor Author

zkat commented Dec 12, 2015

These things were discussed in the 2015-11-14 WG meeting but I want to make sure we have issues set up for the concrete things we're planning on doing for each item before this is marked as closed.

@zkat zkat removed the agenda-item label Dec 12, 2015
@jasnell
Copy link
Member

jasnell commented Dec 12, 2015

@nebrius ... the team at GitHub is very open to receiving feature requests. It might be worthwhile sending in a feature request asking that users with admin rights to an org repository be given the ability to block at the individual repository level. You can use the form here to submit feature requests... just be sure to include some contextual detail as to why the feature would be helpful and how you envision it working.

@nebrius
Copy link
Contributor

nebrius commented Dec 14, 2015

thanks @jasnell! Feature request submitted :)

@nebrius
Copy link
Contributor

nebrius commented Apr 27, 2016

I filed #132 to address moderation on a broader scale. Do we think that program address the issues listed here as well? Or should we leave this issue open?

@nebrius
Copy link
Contributor

nebrius commented Jun 7, 2016

Closing in favor of #132, feel free to reopen if need be

@nebrius nebrius closed this as completed Jun 7, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants