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

Transparency with private issues. #29

Closed
loktar00 opened this issue Mar 8, 2016 · 20 comments
Closed

Transparency with private issues. #29

loktar00 opened this issue Mar 8, 2016 · 20 comments

Comments

@loktar00
Copy link

loktar00 commented Mar 8, 2016

We are a public chat, and I don't think any decisions made behind "closed doors" should stay that way. I understand the comfort of talking privately, but ultimately our discussions and proposed changes have a public impact to the room.

I vote anything private once resolved by the owners, become public and allow other room members to comment if they so wish.

@benjamingr brings up a good point when it comes to private repos not allowing this, so I'm not sure on the technical side how we can make this happen, but I think it would go a long way in showing we are a kinder gentler JS room.

@loktar00 loktar00 changed the title Transparency Transparency with private issues. Mar 8, 2016
@Cerbrus
Copy link

Cerbrus commented Mar 8, 2016

👍

@benjamingr
Copy link
Contributor

I'm for having all decisions that are not about trolls and moderation directly in this repo directly and in the public from the get go.

No need to make these decisions "behind closed doors" anyway.

@loktar00
Copy link
Author

loktar00 commented Mar 8, 2016

I feel moderation issues and troll issues could be public as well. Why not? What does it hurt if user Bobmarlynoscopx69 sees we are talking about them. They then get the chance to defend themselves if they feel its warranted.

We still control ultimate access regardless in the room and on GH.

@benjamingr
Copy link
Contributor

@loktar00 because someone like the Turkish Nazi gravatar dude would abuse it. That was the point - to not have actual trolls abuse it. I would not have opened that jhawins issue in /moderation personally.

@Trasiva
Copy link

Trasiva commented Mar 8, 2016

I thought that was the exact purpose of this repo was for transparency? If there's some secret repo where RO votes are being done...that goes against everything we voted on when we set this up.

@benjamingr
Copy link
Contributor

@Trasiva there is a moderation repo that's used for handling with trolls directly - its goal was not to make these decisions in.

@Trasiva
Copy link

Trasiva commented Mar 8, 2016

@benjamingr Ah, okay. I'll just duck my head then. I didn't realize we had a separate repo for that sort of thing. Makes sense though.

@MadaraUchiha
Copy link
Contributor

I see a couple of problems with a public moderation repo:

  1. Trolls - anyone can comment, and when we're discussing people with inherently bad behavior, we don't want them involved to troll the conversation.
  2. Users don't like it when their mistakes/bad behavior is publicized (even though they made it public by behaving badly in a chat room). We don't unneeded attention from SO management, and we don't want to look like we're harassing specific users, even if they deserve it.

To clarify: Only issues dealing with specific users should go to the private repo. all other issues should go here, no exceptions.

@benjamingr
Copy link
Contributor

@MadaraUchiha I think removing room owners should be an exception

@Trasiva
Copy link

Trasiva commented Mar 8, 2016

I agree, the RO removal was where I had a problem. Trolls and whatnot it makes sense to make them unable to add their crap to the discussion.

@MadaraUchiha
Copy link
Contributor

If all room owners agree to discuss issues with other room owners here, I don't have any objections. I personally don't mind public discussion targeted at me, and I own all of my actions.

That sounds like a separate issue though, feel free to open it.

@loktar00
Copy link
Author

loktar00 commented Mar 8, 2016

@benjamingr how would someone abuse it? I'm failing to see that I guess.

We have also talked about regulars in the secret repo. Just sayin. Stuff should stay public.

@MadaraUchiha
Copy link
Contributor

@loktar00 For example, find the repo discussing their issue and troll it, or flood it with spam.

@benjamingr
Copy link
Contributor

@benjamingr how would someone abuse it? I'm failing to see that I guess.

Flood it with fake GH user comments and other stuff, this is standard in the node repo for example.

@loktar00
Copy link
Author

loktar00 commented Mar 8, 2016

Why don't we handle that issue if it comes up, and not preemptively put everything behind a walled garden?

Whats to stop a troll today from doing the same thing at this very moment?

@benjamingr
Copy link
Contributor

@loktar00 and I agree - I'm for using /moderation only for trolls from this point on.

@loktar00
Copy link
Author

loktar00 commented Mar 8, 2016

@benjamingr I can live with that. I think that makes sense.

@darkyen
Copy link
Member

darkyen commented Mar 11, 2016

Why cant RO votes / etc be locked as Contributor only ? And have RO's as contributors to this repo ?

@ThiefMaster
Copy link

That would also disallow any comments from others

@RUJodan
Copy link

RUJodan commented Apr 18, 2016

Closing because innactive

@RUJodan RUJodan closed this as completed Apr 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants