i honestly think #gitea is pretty great and that once it had that "modules" thing worked out it could be The entry level code forge software suitable for almost anyone
(big claim i know, but i personally think it's one of the few For-Programmers tools i've ever used that feels not bewildering toward Windows users who barely know what a package manager is.)
but its issue tracking leaves me in this weird place between 'my favourite one i've used' and 'not satisfied'
gitea Wikis are intuitively stored in their own reponame.wiki repo,
but where are Issues even hiding?
i have no idea how i'd back up my Issues
you'd also think it's very important for an issue tracker to be available offline next to the code for reference,
at least the top posts of each of its issues and whether they're open or closed / what labels
the comments below might not be extremely important to archive,
particularly if you establish a norm of editing the OP with a brief summary of workarounds/fixes
but wouldn't it be convenient to just git push on a reponame.issues repo in order to close/reopen an issue??
i could just start blindly coding this exactly like i started messing with apt integration
and maybe actually succeed this time
but not today
i think a lot about how sometimes my threads demonstrate how little difference there is between a mastodon thread and a "good" issue tracker thread
which is what leads me to think of weird things like "why aren't issue comments in activitypub"
@clacke I'm doing this quite informally!
For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).