Add a prominent deprecation notice

[paulmelnikow]

@belak has started merging contributions at the original repo! 🚀

So, it's time to deprecate this fork. Here's a prominent notice sending people back to the original.

[belak]

Perhaps the "Upgrading from sorin-ionescu/prezto" section should be removed as well?

[paulmelnikow]

The notice is pretty hard to miss.

I think those upgrade instructions are useful as historical reference. People who followed them before may come to look for them, wondering, what commands did I run again??

I could add a second clarifying note, if you think folks legitimately will be confused.

[belak]

No I suppose that makes sense. :)

[plessbd]

Maybe we should put how to reset back to sorin-ionescu/prezto in the deprecation notice?

cd "${ZDOTDIR:-$HOME}/.zprezto"
git remote set-url origin https://github.com/sorin-ionescu/prezto.git
git pull
git submodule update --init --recursive

Though that might cause conflicts, so we might want to fix that before doing it...

[paulmelnikow]

Hmmm. I wouldn't expect those instructions to work. They'd preserve the commits from the fork, not to mention cause a million merge conflicts. Have you tested them?

If we can develop some instructions that are tested and safe, I'd love to include them. They could also be added at a later time.

[paulmelnikow]

Perhaps moving .zprezto to bkp.zprezto and re-cloning would be simplest.

[johnpneumann]

+1

I agree that we should give some type of indication on how to reset back. Has anyone tried to change the remote repo and just do a git fetch and git reset --hard origin/master

[plessbd]

so far i had to move and redo the install myself.

[paulmelnikow]

A hard reset would risk losing local commits into the ether of the git reflog, as well as losing uncommitted changes. I'd be more comfortable with a backup and reinstall.

[star-szr]

Not sure if it's been discussed already, and it would probably break things even more than what's being discussed here for people that have switched to this fork, but…

I think @sorin-ionescu expressed some interest in sorin-ionescu#1239 (comment) toward moving the prezto project to the zsh-users organization.

I like seeing projects that start as a personal repo on GH move to an organization. To me, it's often a sign that the project has some maturity and a community of some kind behind it.

[belak]

I'd like to get this notice in sooner rather than later... once it goes in, someone can open a new PR and debate about the best way for people to migrate back.

[paulmelnikow]

Agreed. @johnpneumann could you mark it approved? I can't merge it until you do.

[johnpneumann]

Approved

[sorin-ionescu]

@cottser I spoke of my past misdeeds. I don't want to move it at the moment but get long-living issues fixed. I have added contributors.