Move devour to its own GitHub Org
thegrandpoobah opened this issue · 13 comments
Hello, I am the current administrator of the TWG GitHub repository. Wondering who is the current maintainer of the devour project so that I can talk to them about moving this repository to its own GitHub org.
We would like to clean up our org a bit this year and want to make sure things end up on the right places.
Please let me know and we can make sure that whatever we plan in terms of cleanup, we account for your project.
Thanks,
@auvipy thoughts on the above?
I'm positive on that
I'm also an admin on this project and totally okay with moving it to its own org.
@tijn @auvipy , correct me if I'm wrong, but it looks like there are only two things downstream are dependent on this.
- npm
- travis
I think NPM is automatic once you do a publish (and the old repo URL will autoforward as well)
Travis is a bit trickier, I'm not sure how the relationship is set up, so you might have to update that manually.
Does that sound about right?
I'd like to get this done by end of February, so if its more involved I'd love to know.
@auvipy shall we start a new GitHub-organization and move the repo there? The devour-organization already exists. How about "devour-js"?
lets do it
@thegrandpoobah can you help us transfer the repository to https://github.com/devour-js ? GitHub forbids me to do it myself:
@tijn , to transfer this repo, I need to have repo creation rights on the devour-js org. once you give that I can transfer this over.
Thanks @thegrandpoobah !
It's pretty funny that even this issue has moved over to the new organisation 😄