Figure out what to do with repositories on this organization

[technicalpickles]

Now that this is deprecated, we'll need to figure out what to do with this organization. There are 3 groups of repositories remaining:

• forks that were requested to be added through these issues
• those added by @technicalpickles and others on the @hubot-scripts/owners
• as the above, but which are included in the new hubot instances through generator-hubot

I have some ideas, but I figured I'd through this out there first.

cc @bhuga @michaelansel @bkeepers

[therealklanni]

Well, we could have the original authors fork it back to their own account and maintain it there once again, but that seems like it would be pretty messy.

What were your thoughts?

[technicalpickles]

fork it back to their own account and maintain it there once again

They can't fork it to their own accounts, since that is where the origin is 😓

[technicalpickles]

I know if you transfer repositories, there is a redirect setup from the old location to the new one. Feasibly if the repository is transferred to hubot-scripts and back to the user, that might setup the right redirects. But that is tedious, and it's unclear what would happen to PRs and issues that are on the hubot-scripts fork.

I am asking around if we can get a redirect setup and transfer issues over to the parent repo, without having to go through that process.

[bkeepers]

Another (not great) option for forks:

• Replace the contents of the repos with a README that points people to the parent

[technicalpickles]

Replace the contents of the repos with a README that points people to the parent

Building on that, we could do that on a non-master branch, and make that the new default branch.

[technicalpickles]

I asked around and found out how to setup repository redirects, so that should be feasible. I think we can start with forked repositories that don't have any issues or PRs, as there's not an easy way to copy those over yet.

[cycomachead]

Is there any updates on this? I'm thinking of trying something myself

I have cycomachead/hubot-group-alias and hubot-scripts

I'm thinking of:

• renaming my main repo "-temp"
• transfer ownership of the fork back to me (Can I actually do that?)
• Rename the forked repo to "-deprecated"
• rename the original repo to remove the "-temp"
• re-publish to NPM with the new URL (personal repo)
• Transfer issues w/ https://github-issue-mover.appspot.com
• Change the default branch on the "-deprecated" repo.

I don't have any outstanding PR's, but I don't want to just delete the "main" repo incase links point directly to it, and there's still some stars associated with it.

Ok, so that process seems a bit complex so I could be totally overthinking it, but this is my plan to do in the next day.

[stephenyeargin]

In my case, it was as simple as going under the Settings panel for the repository under this Organization and moving it back to my account (I'd deleted the original repository a while ago). That allowed me to keep the issues, stars, etc. The next steps would be to delete my per-package team, though I'm a bit bummed it didn't transfer the collaborators to the transferred repository.

EDIT to add: It also broke my Pages for the repository (which wasn't anything more than a web view of the README.md, but still)