Move to fork?
-
The project does not seem to be maintained anymore. Should we move to this fork? https://github.com/sharevb/it-tools
-
It is not clear if the fork is something "official" or just one active person adding features. Looks like the main project does mostly update the sponsor banner since quite a long time https://github.com/CorentinTh/it-tools/commits . Though unless there are some official statements, I don't think we should hastily move to a fork by one person.
Sadly no reaction on https://github.com/CorentinTh/it-tools/issues/1635
-
Hello @it-tools users
We reached out to Corentin Thomasset the maintainer of @it-tools for a statement.
From Corentin Thomasset:
To be totally transparent with you about the current state of the project. It-tools is currently on pause as I haven't had the time to maintain it properly over the past months. The project grew much faster than I anticipated, and between the volume of issues, PRs, and the technical debt that accumulated, I found myself a bit overwhelmed. I didn't want to disappoint people, so I went a bit into ostrich mode with the project.
That said, I haven't abandoned it. I've actually been thinking about a complete rewrite with a modern stack and fresh approach, and have slightly started exploring new architecture/stack in some other branches some time ago. But I don't have a concrete timeline for this yet, so it won't be for soon. I'm currently focused on other projects, particularly Papra.
I'm aware that sharevb has created an actively maintained fork with additional tools. For your immediate needs at Cloudron, it might make sense to align with that fork for now, as it's actively developed and has a growing community around it, though it has taken a slightly different direction than my original vision.
So we might switch to the fork.
-
Hello @teiluj
Would you expect this to be a new app or would be enough to simply switch over to the fork with the existing app?
Trying to gauge the expectation in this scenario.Hi @james - Many thanks for asking.
Based on the current state of the app, the stat of the fork and the message of the dev, I would suggest to move to the fork but, since the app is also not the most business critical app for us:
- This mostly a @cloudron question. What practices you follow in such case, what makes more sense technically for you etc...We could easily live with both the options you presented
- We are possibly not the only one in this situation and others might have alternative preferences
Hope that this makes sense. Thanks again for checking.
