-
Notifications
You must be signed in to change notification settings - Fork 12
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 to nodejs/build? #8
Comments
Sorry, been on vacation. Sure - lets get it done.
|
Bump on this one. #5 seems to be blocking Python 3 progress at nodejs/node#29451 (comment) |
@bnoordhuis do you have a pypi account? @Trott @mhdawson @rvagg -- we use this, but to maintain it we'd need pypi accounts to publish it to -- or we could just vendor it into node perhaps? Its copyright status and code heritage is not clear to me, if that matters. Only one file has a copyright statement, and it's GPL, by Redhat. |
I am willing to do the PyPI mechanics and be responsible for the repo but does the Node.js TSC need to weigh in on creating the new repo especially given the copyright question? |
The policy for transferring a repo into the nodejs org is at https://github.com/nodejs/admin/blob/4f463ad194a48a7d73c1d94588903539819fcbe2/GITHUB_ORG_MANGEMENT_POLICY.md#repositories. In a nutshell: open an issue in the admin repository, wait 72 hours, transfer it in if no one opposes doing so. |
Done at nodejs/admin#413 |
Please add cclauss |
@jbergstroem On node.js side we have to wait about 2 more days to accept the repo, but if you could add pypi credentials for |
@sam-github will do. Edit:
|
👍 I got a notice that I have been added as Owner to the PyPI project tap2junit by jbergstroem. |
@cclauss Great, @jbergstroem thanks! |
Hi Johan, would you consider moving tap2junit to the nodejs organization?
I was looking at a couple of tap2junit failures on Node's CI but realized that I can't really make changes because there is no way to publish a new version.
The text was updated successfully, but these errors were encountered: