-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
👍 |
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. |
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. |
@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. |
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. |
@Trasiva there is a moderation repo that's used for handling with trolls directly - its goal was not to make these decisions in. |
@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. |
I see a couple of problems with a public moderation repo:
To clarify: Only issues dealing with specific users should go to the private repo. all other issues should go here, no exceptions. |
@MadaraUchiha I think removing room owners should be an exception |
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. |
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. |
@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. |
@loktar00 For example, find the repo discussing their issue and troll it, or flood it with spam. |
Flood it with fake GH user comments and other stuff, this is standard in the node repo for example. |
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? |
@loktar00 and I agree - I'm for using |
@benjamingr I can live with that. I think that makes sense. |
Why cant RO votes / etc be locked as Contributor only ? And have RO's as contributors to this repo ? |
That would also disallow any comments from others |
Closing because innactive |
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.
The text was updated successfully, but these errors were encountered: