It's really hard (impossible?) to define a feature set that work for everyone. Every bug tracker is a bit different, and if you want to have everything you end with Jira, which I'm not sure is actually solving a problem.
However, git-bug's data model is designed in a way that you can add more "operations" on an entity (say: assign a bug) without every client having to implement it. You can also add your own entity type (pr, kanban, ...) the same way. Clients will just ignore that extra data and support what they want. This open the possibility for addons and so on.
For this specific case of the bug states, I want to add a config entity to configure that. You'd start with a reasonable default (open/close) but you could tune it for the needs of your project.
created something similar but specific to llama-server. it takes advantage of logprob output and completes decisions in a single forward pass https://github.com/khimaros/verdict
Fairphone with its 8-year updates, swappable battery, and decent repairability is great for those of us who doesn't like to be forced to change phones often. I'm not sure, however, what variety of distributions you mean. It supports 1 Android, and 1 de-googled Android. Which isn't bad at all, but still doesn't sound like "variety".
Wikipedia (https://en.wikipedia.org/wiki/List_of_open-source_mobile_pho...) lists /e/OS, CalyxOS, IodéOS, LineageOS, postmarketOS, Ubuntu Touch, the latter two being non-Android, the rest Android derivatives on Fairphone 5. Fairphone 6 has only /e/OS and IodéOS listed at the moment, but that will probably change after some time on the market.
There are also various reports of things like running e.g. Fedora on an FP6, https://www.notebookcheck.net/Fairphone-6-turns-into-a-Linux... or Debian on FP4/5, but those generally aren't something that is usable due to lacking support for basic things like calls.
reply