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

Transfer to nodejs/build? #8

Closed
bnoordhuis opened this issue Jul 17, 2019 · 11 comments
Closed

Transfer to nodejs/build? #8

bnoordhuis opened this issue Jul 17, 2019 · 11 comments

Comments

@bnoordhuis
Copy link
Member

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.

@jbergstroem
Copy link
Member

jbergstroem commented Jul 25, 2019

Hi Johan, would you consider moving tap2junit to the nodejs organization?

Sorry, been on vacation. Sure - lets get it done.

  1. I'll transfer this repo ownership to nodejs/build team
  2. Who should I add to pypi? Couldn't find your username

@cclauss
Copy link
Collaborator

cclauss commented Sep 21, 2019

Bump on this one. #5 seems to be blocking Python 3 progress at nodejs/node#29451 (comment)

@sam-github
Copy link

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

@cclauss
Copy link
Collaborator

cclauss commented Sep 22, 2019

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?

@Trott
Copy link
Member

Trott commented Sep 22, 2019

I am willing to do the PyPI mechanics and be responsible for the repo but does the 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.

@cclauss
Copy link
Collaborator

cclauss commented Sep 22, 2019

Done at nodejs/admin#413

@cclauss
Copy link
Collaborator

cclauss commented Sep 22, 2019

Who should I add to pypi? Couldn't find your username

Please add cclauss

@sam-github
Copy link

@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 cclauss and initiate the xfer, I think that will allow us to press the "accept the transfer" button in a couple days. Thanks!

@jbergstroem
Copy link
Member

jbergstroem commented Sep 24, 2019

@sam-github will do.

Edit:

  • added cclauss as owner of tap2junit on pypi
  • transferred ownership of this repo to @nodejs/build team

@cclauss
Copy link
Collaborator

cclauss commented Sep 24, 2019

👍 I got a notice that I have been added as Owner to the PyPI project tap2junit by jbergstroem.

@sam-github
Copy link

@cclauss Great, @jbergstroem thanks!

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

5 participants