-
Notifications
You must be signed in to change notification settings - Fork 145
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
Sync/discussion with moderation team #509
Comments
Related discussion in on this PR - https://github.com/nodejs/moderation/pull/531 |
I don't have access to it Could someone write a minute about that issue, whenever it will be closed? |
The tldr is, we need to work out the details of how node’s moderation policy can apply to the pkgjs org also. Up until now, it’s been ad hoc (and not needed in pkgjs, thankfully), and just kind of worked because there’s a few node tsc and moderation members who have pkgjs owner access - but this meeting will help us have an official process. |
@nodejs/package-maintenance, @nodejs/moderation based on Doodle set meeting time to 4 ET on Monday Feb 7 Zoom for meeting - https://zoom.us/j/431077278 |
Ironically the fact that you can't see it is one of the issues to work out. The private moderation repo is a key tool for us, but people who aren't in the nodejs org can't see it. Do we find some other tool? Create an equivalent in the pkgjs org? Something else? (Those are rhetorical questions for now. Let's not try to come up with an answer in this issue. There are other things like that to talk about. It's just an example.) |
Session to discuss pkgjs repo with moderation team/provide context insight into contributors and content.
@nodejs/package-maintenance, @nodejs/moderation can you please fill in the doodle.
https://doodle.com/poll/9edfwrq62p62uu6g?utm_source=poll&utm_medium=link
The text was updated successfully, but these errors were encountered: