Multiple forks?

[smiller171]

Looks like @maykar is endorsing @zanna-37's fork. Might it make sense for the two of you to join forces rather than maintaining two separate forks?

[jsnfwlr]

The bigger problem is that @zanna-37 didn't fork via github, so we can't compare the two branches, or see what has changed since the fork.

[zanna-37]

Hi @smiller171, it seems to me that NemesisRE just changed few links and replace maykar name and nothing more (please, correct me if I'm wrong).
In my repo I'm committed to continue the development. I already solved all the issues that were present in the original repo and also addressed the pull requests. I also rewrote the exception logic and I'm willing to continue.

NemesisRE, and anyone else, is more that welcome to contribute by creating issues, discussion, or proposing pull requests. =)

[zanna-37]

Hi @jsnfwlr, actually you can compare the two repositories. You just need to compare the main branch against maykar's last commit. You can see all the changes by clicking in the following link zanna-37/hass-swipe-navigation@168e0e3...main.

Moreover, I did fork via GitHub, but I choose to deattach from the original repository on purpose. Since maykar was clear about its intentions to not continuing the development in the next future, I don't think my repo will ever be merged back with maykar's one. Since the development will continue in my repo there is no need to have the back pointer to the original.
This is common when doing hard-forks, for example BorgBackup did something similar when hard-forking from attic-backup.

If maykar decides to come back we'll think about merging the commits manually, but it isn't a concern now.

[NemesisRE]

@smiller171 My forks were meant to keep it in HACS mainly for me but when I do something like that for me I can do it for everyone. I am not a developer I'm a sysadmin so I happily archive my fork in favor of the active developed fork from @zanna-37.

[jscmidt]

@NemesisRE please archive your repository. It’s really confusing when installing this via HACS, since it isn’t clear which repository is under active development.