-
-
Notifications
You must be signed in to change notification settings - Fork 19k
Move captains and committers to another repo #6396
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
base: master
Are you sure you want to change the base?
Conversation
Cool, although these changes were previously blocked because we didn't want to maintain that list here since it was unmanageable (see #6087, #6033), maybe the process should even be through creating an issue and waiting, perhaps 7 days, to be accepted or rejected , as was partially done with the committers on the website (see #6057). I wouldn't want to be unable to get write permissions just because of that small detail of maintaining the list. |
You are absolutely right @bjohansebas. I just updated the PR to reflect this 👍 |
This is now ready to be merged, I updated the links 👍 |
NO MERGE BEFORE expressjs/.github#18
This PR reflects that the active repo list and initiatives have been moved to another repository.