-
Notifications
You must be signed in to change notification settings - Fork 133
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
Delete/Archive collaboration
repo
#204
Comments
Might want to archive the inclusivity repo too for the same reason. Might also be worthwhile either removing or updating the membership for the @ nodejs/collaboration and @ nodejs/inclusivity teams too. (The collaboration one especially, as it is often what comes up when one is trying to @-mention nodejs/collaborators instead.) |
Lets hold off inclusivity for now...it's possible it will be reused. More info: nodejs/community-committee#13. +1 on archiving this repo. |
Let's not get into the habit of deleting any repos. Let's mark it archived and just let it be. |
I have updated the collaboration repo to mark it inactive |
I think the spirit of this effort is now taken over by the Community Committee. Every little bit of cleanup helps new folks.
The text was updated successfully, but these errors were encountered: