-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider moving the repo to zsh-users #1284
Comments
Perhaps one way we could go about it is to rename the repo to zprezto and then move it to zsh-users? |
It'd be confusing to have multiple prezto repo's under the zsh-users repo. I know some folks want to keep the history of the fork, but assuming the fork gets mostly merged back into this one, then I'm personally in favor of deleting the fork repo. |
As far as I know, the forked repo will be removed or transferred eventually. I'm fairly certain @nicoulaj (who maintains zsh-users) doesn't want an inactive repo there. |
I am opposed. Prezto is popular. Many have Prezto as a submodule or linked in their setup scripts. Moving it breaks all links. It's bad user experience. Keep it here. |
GitHub automatically sets up a redirect when cloning and on the web interface so they would not be broken if it was moved. It's still your say though so if you don't want to move it, that's fine. |
That's nice. When did they add that? I say we should leave it here for now and start closing long-living issues. Users care more about bugs fixed. |
https://github.com/blog/1508-repository-redirects-are-here Looks like they added it some time in 2013. This isn't a high priority, but it might be nice in the future. :) |
Some thoughts and considerations:
|
A visible clarification with link to community-fork/prezto can be added in the readme. |
Personally, no problem with that. The only issue that may arise is for users that have cloned (or submoduled) the |
As the community fork is not active any more (it was shut down and the README was updated to show this) I think it would be good to move the repo there. Links will not be broken as long as Sorin doesn't create another repo named prezto (since that would override the redirect). The old community fork redirect would be lost, but I feel like that's an acceptable tradeoff. Another thing to note: I'm not 100% sure how renaming then transferring the repo would work - I assume the redirect from the original repo to the transferred, renamed repo would stay in place, but I'm not sure. We would need approval from @sorin-ionescu (and probably @nicoulaj, as he is the admin of the zsh-users org as far as I know) to do this, so it would be great to see what they think after seeing the info on repo redirects. |
There are a number of complications with this... because that fork has existed for a while, if that was removed and this repo moved over there, people who previously had their remotes pointing at the fork might have issues.
However, there is still value in moving the repo to zsh-users. Having it under an org would potentially show it has some maturity and community support.
This was recently proposed here: prezto-inactive-community-fork#63 (comment) so it seemed like a good time to start a discussion.
The text was updated successfully, but these errors were encountered: