[IMPORTANT] Project unmaintained. Please migrate to 'rickstaa/tmux-notify'
rickstaa opened this issue · 11 comments
oh I agree, I typically despise forks as people are too quick to fork rather than try to work with maintainers. but in the case where a maintainer has ghosted the repo and people are using it I think it's the only way. GitHub Support historically doesn't intervene when I wish they would.
Same here, de-forking is my last resort 😅. However, the last response I received from the author was more than 3 years ago (see #16 (comment)) and I tried to contact him on all channels.
The de-forking just finished, and it looks like all the history was retained 🎉. The only contributor that is not shown any more is @bruno- because I think those initial commits were cherry-picks. Anyway, we are good to continue the maintained on my new orphan repository 👍🏻. Alternatively, as stated in #16 I'm also okay with transferring the repository to the https://github.com/tmux-plugins organization and maintaining it from there if @bruno-, @ctjhoa and @jbnicolai are interested. I think there it would even reach more people.
Originally posted by @rickstaa in #28 (comment)
As explained in the post above, @ChanderG no longer seems to maintain this repository 🙁. Since I wanted more control while maintaining this project, I detached my fork and will maintain this project there. I'm happy to detach it again in the future, might @ChanderG return to help me maintain it 👍🏻.
How to migrate to the new upstream
To migrate to the new upstream (i.e. https://github.com/rickstaa/tmux-notify), change the following line:
set -g @plugin 'ChanderG/tmux-notify'to:
set -g @plugin 'rickstaa/tmux-notify'in your .tmux.conf.
@rickstaa Hi Rick. Just saw this. I am not in a position to maintain this and your move is absolutely the right one - since you have put in all the effort since the very beginning. I did see some notifications ever so often and intended to come back at some point - but that never materialized.
Is there something I can do to make your life easier? I can transfer this repo over to you or to an org like tmux-plugins - if you want the history of issues/PRs etc.
Again, my contributions were only in the initial structure and setup - it was Rick who put in the active effort to grow and maintain this, so thanks to @rickstaa for all of that.
@rickstaa Hi Rick. Just saw this. I am not in a position to maintain this and your move is absolutely the right one - since you have put in all the effort since the very beginning. I did see some notifications ever so often and intended to come back at some point - but that never materialized.
Is there something I can do to make your life easier? I can transfer this repo over to you or to an org like tmux-plugins - if you want the history of issues/PRs etc.
Again, my contributions were only in the initial structure and setup - it was Rick who put in the active effort to grow and maintain this, so thanks to @rickstaa for all of that.
@ChanderG, thanks for taking the time to answer me. No problem at all! Life can leave little time for maintaining OS projects. I also had to hand over control for other projects I could no longer maintain 😅. I chose to maintain this project because you made something very cool, and I use the tool daily.
I prefer transferring it to https://github.com/tmux-plugins because the plugin will have more reach there, and we both have control over the repository 🚀. If @bruno-, @ctjhoa and @jbnicolai don't yet want to merge this plugin into the organization because our userbase is relatively small, we can do the following:
- I will attach my detached fork to the upstream again.
- I will merge the commits of the last three weeks into the upstream.
- You transfer the repository to my account (see https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository).
This way, I will have more control over the repository (i.e. settings, applications, secrets, actions etc.), making it easier to maintain. In contrast, you still have full permission to merge any PR.
@ChanderG I just asked GitHub to attach my fork again. I think after it is attached we can transfer the repository to my account, and I can give you the most permissive collaborator permissions. If the tmux-plugins maintainers answer, we can transfer it to the organization 👍🏻. I will let you know when the re-attachment is done.
@henriqueffc, @odonckers, @cynicaljoy for your info.
@ChanderG, the GitHub team just attached the fork again. If you could transfer the repository to my account, that would be great. I will then give you all the permissions 👍🏻.
@ChanderG, you can transfer the repository to my username (see https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) 🙏🏻.
@rickstaa Just tried to transfer over the repo - but it failed since a repo with the same name exists in your account. What is the best way to proceed without breaking anything? Did you check with the tmux-plugins folks?
@rickstaa Just tried to transfer over the repo - but it failed since a repo with the same name exists in your account. What is the best way to proceed without breaking anything? Did you check with the tmux-plugins folks?
Strange, I would have thought GitHub should have handled the situation when there already is a fork since migrating to another fork is committed. I now renamed my fork to https://github.com/rickstaa/tmux-notify-fork so you can transfer the repository 👍🏻. Unfortunately, I did not hear back from the tmux-plugins maintainers.
Just tried to, but there is a new error this time:
Looks like you can't transfer a repo if the destination owner has a fork in the same network, from the prerq here: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
Not clear why this sort of rules exist... :-(
@ChanderG thank you so much for trying again. I have no idea why GitHub has those rules, as they don't make sense to me since most transfers are to other collaborators who will have a fork. Probably some safeguards to prevent server/routing problems 🤔. I removed my fork so that now it should work 👍🏻.