Page MenuHomePhabricator

Move n3rsti/tools-gallery under toolforge on Github
Open, Needs TriagePublic

Description

To address the issues filed currently under https://github.com/n3rsti/tools-gallery, it might be helpful to have it under https://github.com/toolforge on Github.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 17 2020, 10:34 PM
bd808 added a comment.Apr 23 2020, 1:01 AM

@srishakatux are you a Owner of that repo on GitHub? Basically we need someone who is an Owner to follow the steps at https://help.github.com/en/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-user-account and transfer to the "toolforge" organization.

@bd808 Okay! I've requested admin access to the repository from @N3rsti

bd808 reassigned this task from bd808 to srishakatux.May 5 2020, 9:46 PM
bd808 added a subscriber: bd808.

@srishakatux ping me when you have admin access to the repo and we can do a chat or hangout to help you actually make the transfer yourself. That seems like good knowledge to share and document rather than having "ask bd808" be the way these things always get done. ;)

So, we didn't hear from @N3rsti! It looks like we may have to follow an alternative route that you proposed once @bd808 (via the Git history) if we still think that this repo should be under Toolforge.

So, we didn't hear from @N3rsti! It looks like we may have to follow an alternative route that you proposed once @bd808 (via the Git history) if we still think that this repo should be under Toolforge.

It seem like something should be done if the current owner is unresponsive. This was a tool that was worked on explicitly as a showcase and once proposed for inclusion on the Toolforge landing page to highlight community work. Does it at least have active co-maintainers who can switch out the running codebase if we create a new primary git repo?

It seem like something should be done if the current owner is unresponsive. This was a tool that was worked on explicitly as a showcase and once proposed for inclusion on the Toolforge landing page to highlight community work. Does it at least have active co-maintainers who can switch out the running codebase if we create a new primary git repo?

If you meant Toolforge, yes, I am a maintainer on the tool. So, maybe I should fork the original repo, request the forked version be added to Toolforge account on Github, and swap the tool's current code on the Toolforge server with my version? What say?

If you meant Toolforge, yes, I am a maintainer on the tool. So, maybe I should fork the original repo, request the forked version be added to Toolforge account on Github, and swap the tool's current code on the Toolforge server with my version? What say?

That sounds like a good plan. :) Find a time "soon" that fits on both of our calendars and we can pair up on the steps to actually transfer your fork of the repo.

Okay, after I am back from vacation :)