-
Notifications
You must be signed in to change notification settings - Fork 143
Pulling CommComm's i18n repo into nodejs/ #51
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Thanks for creating the MVP repo! @Trott any ideas on what's involved in moving the repo? 😄 |
@bnb Step one is to wait at least 72 hours:
After that, I think as long as the current owner is an org member, they can transfer it over. Guess we'll find out in 72-ish hours and figure out what to do if that doesn't work. |
@Trott sounds good! Thanks a bunch for the info! 🙌 Stoked to swing back around to this in 72 hours with y'all! :D |
It does indeed. I believe the current owner of the repo needs to be an owner of the Node.js org. So myself, @Trott or someone could do it if the repo was transferred to us? Not 100% sure if I'm understanding that process correctly. |
Ahh, I totally misread that! Thanks for clarifying. Let us know how it goes! |
@bnb no worries! Having no trouble doing it right now, but I'm not sure about this and which teams I should give access to it? I'll add the ones I think are relevant, and can always add more later–I guess I'm just most worried about people getting possible email/notification noise :P |
@bnb sweet–should be live momentarily. I only gave access to the CommunityCommittee for now since this is a CommComm WG repo, if anyone from another team wants team access for it let me know! :D Thanks all! 🎉🎉🎉 |
Woop woop! We're live!💥 Closing this issue. 👍 |
The current Node.js i18n initiative owned by CommComm is seeking to officially establish our working group. Our MVP repo can be found here, and we'd like to pull it into nodejs/ to keep things moving. 🎉
I'm not sure what tasks are required in order to transfer this, your help is greatly appreciated! 🙌
The text was updated successfully, but these errors were encountered: