First of all, I’d like to express my thanks to @RasmusLindroth for writing this splendid piece of software 🌼
I see the last commit on this repo is from January 2023, which is the last commit from Rasmus Lindroth on GitHub at all. I hope he is well and just dedicating his time to other things 🙂
Maintaining software is demanding, so it is completely understandable why someone would not keep doing it as a hobby, but since I like Tut so much, I’d hate to see it decaying as issues and pull request pile up and as changes on the server side (Mastodon API?) start to break things (e.g. #278). Looking at the forks page I see no fork that is actively maintained.
I see several possible paths forwards:
-
@RasmusLindroth continuing to develop and maintain Tut 🥳
-
Passing the torch to someone else and giving them the required permissions on this repo. This involves posting a note on the README.md file and on the website, saying a new maintainer is needed. (Even though I’d love to, I cannot take this role myself).
-
Alternatively, if none of the above would take place, I hope someone will make a fork that is actively maintained. This is the situation with Orgzly, which was abandoned and then ‘revived’ as Orgzly Revived (IMHO they could’ve chosen a better name, but this is not the point 😉).
-
The worst scenario is that the current situation continues as it is.
Hoping to see a great future for Tut,
Maja
First of all, I’d like to express my thanks to @RasmusLindroth for writing this splendid piece of software 🌼
I see the last commit on this repo is from January 2023, which is the last commit from Rasmus Lindroth on GitHub at all. I hope he is well and just dedicating his time to other things 🙂
Maintaining software is demanding, so it is completely understandable why someone would not keep doing it as a hobby, but since I like Tut so much, I’d hate to see it decaying as issues and pull request pile up and as changes on the server side (Mastodon API?) start to break things (e.g. #278). Looking at the forks page I see no fork that is actively maintained.
I see several possible paths forwards:
@RasmusLindroth continuing to develop and maintain Tut 🥳
Passing the torch to someone else and giving them the required permissions on this repo. This involves posting a note on the
README.mdfile and on the website, saying a new maintainer is needed. (Even though I’d love to, I cannot take this role myself).Alternatively, if none of the above would take place, I hope someone will make a fork that is actively maintained. This is the situation with Orgzly, which was abandoned and then ‘revived’ as Orgzly Revived (IMHO they could’ve chosen a better name, but this is not the point 😉).
The worst scenario is that the current situation continues as it is.
Hoping to see a great future for Tut,
Maja