-
Notifications
You must be signed in to change notification settings - Fork 135
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
Transfer stduhpf/caritat into the nodejs org #805
Comments
No objections from TSC members and the issue has been open for more than 72 hours, so the transfer is accepted. I'm going to proceed with the plan. @mhdawson IIRC you have access to the bot account, could you take care of the NPM token creation please?
|
@aduh95 can you add some of the missing boilderplate files ? I think we need a contributing.md with the DCO, one for Code of conduct and the licence should likely update to say "and collaborators" as we have for other reapos. I'll try to get to looking at the token in the early part of this week. |
Hum I followed the recommendation in admin/transfer-repo-into-the-org.md Lines 11 to 22 in 130c4e8
+1 for the license file, I'll send a PR. |
@mhdawson friendly ping, I would love to be able to finish the transfer of the npm package. |
@aduh95 token added. |
Thanks, I've confirmed it works. The transfer is complete now. |
I suggest to transfer https://github.com/stduhpf/caritat into the nodejs GitHub organisation, and to create the
@nodejs/caritat
team to maintain it.The goal of Caritat is to propose a robust voting solution that's integrated with the tools Node.js devs use. The TSC is ready to use it as its de facto voting solution, other teams are of course welcome to use it as well.
@stduhpf can you please 👍 to confirm you're OK with that plan? If you are, please transfer the repo to my GitHub account so I can transfer it to the org.
Refs: nodejs/TSC#1165
/cc @nodejs/tsc
The text was updated successfully, but these errors were encountered: