Skip to content
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

Pulling CommComm's i18n repo into nodejs/ #51

Closed
obensource opened this issue Jan 19, 2018 · 10 comments
Closed

Pulling CommComm's i18n repo into nodejs/ #51

obensource opened this issue Jan 19, 2018 · 10 comments

Comments

@obensource
Copy link
Member

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! 🙌

@bnb
Copy link
Contributor

bnb commented Jan 19, 2018

Thanks for creating the MVP repo!

@Trott any ideas on what's involved in moving the repo? 😄

@Trott
Copy link
Member

Trott commented Jan 20, 2018

@Trott any ideas on what's involved in moving the repo? 😄

@bnb Step one is to wait at least 72 hours:

Any organization member may request the creation of a new repository within the Node.js Foundation GitHub Organization by opening an issue in the Node.js admin repository. Provided there are no objections from any TSC or CommComm members, such requests are approved automatically after 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.

@obensource
Copy link
Member Author

obensource commented Jan 20, 2018

@Trott sounds good! Thanks a bunch for the info! 🙌

Stoked to swing back around to this in 72 hours with y'all! :D

@obensource
Copy link
Member Author

@Trott @bnb it looks like this issue has passed the 72 hour consensus gathering period. I think I should be good to go for pulling it in if y'all wouldn't mind giving a 👍 :)

@bnb
Copy link
Contributor

bnb commented Jan 24, 2018

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.

@obensource
Copy link
Member Author

@bnb based on what @Trott said, I was under the impression that any 'org memeber' can do it as long we observe the stipulations he outlined. No harm in me trying I guess. I'll give it a shot, and let you know if it doesn't work. :)

@bnb
Copy link
Contributor

bnb commented Jan 24, 2018

Ahh, I totally misread that! Thanks for clarifying. Let us know how it goes!

@obensource
Copy link
Member Author

@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?

screen shot 2018-01-23 at 8 23 42 pm

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

@obensource
Copy link
Member Author

@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! 🎉🎉🎉

@obensource
Copy link
Member Author

Woop woop! We're live!💥

Closing this issue. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants