Rename project to "terminus"

[ari-gold]

Problem:

Google for "pantheon terminus" and top result is the deprecated project. Reported by Marketing

Proposed solution:

According to https://github.com/blog/1508-repository-redirects-are-here renaming a repo adds a redirect so:

1. Renaming https://github.com/pantheon-systems/terminus/ to https://github.com/pantheon-systems/terminus-deprecated
   and
2. Renaming https://github.com/pantheon-systems/cli to https://github.com/pantheon-systems/terminus

will have the desired effect that:

• Someone visits cli or terminus they'll end up on terminus project page
• People will need to go directly to terminus-deprecated to reach that deprecated project

I tested this with my forks and it seemed to work fine. Does this sound like a reasonable solution?

[bmackinney]

+1. Does composer respect the redirects? I imagine it would.

[bmackinney]

It seems not: composer/packagist#496

[ari-gold]

@bensheldon @TeslaDethray Can we do this today or tomorrow?

[bensheldon]

@ari-gold can you put together a rollout plan that includes a customer notification and any updates to docs or links? That composer link above seems to imply composer won't automatically redirect and folks will probably need to update their scripts if they're manually fetching packages from github.

[ari-gold]

@bensheldon I've referenced PRs to update relevant docs on pantheon.io/docs as well as this README and CHANGELOG. Do you think that covers everything? /cc @bmackinney @TeslaDethray

[bmackinney]

https://packagist.org/packages/pantheon-systems/terminus is marked abandoned already. We should investigate whether that can be reversed. @greg-1-anderson owns that project on packagist.

@bensheldon I think if scripts download /cli directly from github, it should respect the redirect to the new/old url, but yes they'll generally want to update scripts. We should also email the power-users list.

On Packagist:

• Add a new package
• Abandon pantheon-systems/cli ad point to pantheon-systems/terminus
• un-abandon pantheon-systems/terminus? @greg-1-anderson

[bensheldon]

@bmackinney I can un-abandon the project... oops, I guess I just did.

[bensheldon]

I've renamed the repos:

• pantheon-systems/terminus -> pantheon-systems/terminus-deprecated
• pantheon-systems/cli -> pantheon-systems/terminus

And I've updated the Packagist projects to be either abandoned/redirected, with the proper source being pantheon-systems/terminus

[greg-1-anderson]

+1 looks like that will work. Screen shot is out-of-date, though; are the projects set to auto-update in Packagist? Can github auto-update more than one Packagist package per repository?

[bensheldon]

@greg-1-anderson it seems like the auto-update logic lives in Github, rather than Packagist. We're firing off the github webhook at Packagist, and Packagist must auto-update (one/any?) project that matches the git repo for the webhook. So it's wired up right, we'll just have to see if Packagist will update them appropriately.

[greg-1-anderson]

Yep, both pantheon-systems/terminus and pantheon-systems/cli are showing the right info, and the "(Not Auto-Updated)" tag shown in the screenshot above has been removed on Packagist, so it seems that all should be fine now. Folks will get the right thing from Composer if they require pantheon-systems/terminus or pantheon-systems/cli.