Wow, wasn’t expecting Tenzu to get mentioned here ^^
I’m one of the developer behind Tenzu, I think @StephanieAG summarised it pretty well (and I answered her question about our financial state) but feel free to ask me any additional questions.
I can provide some more details about our roadmap which might be relevant here:
- We are currently working on adding tags and and custom fields to enrich the tickets, as well as a search and filters system
- As Stephanie said, we are very much committed on accessibility, we have work planned on this before the end of the year in order to make Tenzu much better and we will follow this with an accessibility audit, thanks to the grant we received from NlNet
- We are planning to work on integrating with forges (gitlab, github, forgejo) but I can’t give any date
- We are planning to engineer a plugin system in order to enable anybody to develop something for their specific use case (like, an auto triage banner display for example
, completely random example of course ). But once again, no date given - Today, we don’t have any way to make a project “public”, either in read-only or otherwise. You need an account and to have been invited to collaborate on the project. That doesn’t mean it won’t come one day (and it was planned in Taiga Next initially), but this is not part of our current roadmap
Not sure if Tenzu could be a good fit for Django trac replacement, it definitely look like it would need a fair bit a tweaking to support the django workflow and the current version is certainly not sufficient for it.
It is a huge endeavour and it’s good this is considered in advance, before the issue become any more pressing if trac goes completely unmaintained. As a django community member, I’m also not a fan of the github solution, because of what stand behind github. I would love for the issue tracker to keep being an opensource tool, no matter which one is chosen.