-
Notifications
You must be signed in to change notification settings - Fork 220
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
Lead Maintainer wanted #77
Comments
I'd love to fix issues, and add i18n support like the other standard workshoppers at here 🙋♂️ |
Lead maintainers are still welcomed btw 😃 I will add @pnn as a lead developer to maintain this workshop together since: |
🙌 |
🙋♂️ |
Since I know both of them on the above comments and their contributions, I've added the following members into the WELCOME 🎉 As a maintainer of a workshopper, please check the following repository as well: |
I reopened this because it's still very welcomed :) |
I am in :) |
Moving the workshoppers under the workshopper org umbrella means that there is no longer a signal of who the implicit "lead maintainer" (i.e., the original author) is. Following the example of the other workshoppers it would be awesome to have a small group of people who are invested in the future of how-to-npm to volunteer to join a
how-to-npm lead maintainers team
. We'll make a GitHub team to list the volunteers.The text was updated successfully, but these errors were encountered: