i honestly think 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 repo,

but where are Issues even hiding?

i have no idea how i'd back up my Issues

Show thread

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??

Show thread

i could just start blindly coding this exactly like i started messing with apt integration

and maybe actually succeed this time

but not today

Show thread

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"

Show thread

@Valenoern AFIAK the answer to that is "Because no one took the time to do that yet" but there are initiatives working on it out there:

@Valenoern Yes! This is an issue with every "git hosting plus" service ever. I wish at least one of them would go with shoving the issues into a repo, #distbugs style.…

Adding a gitea bridge to my current half-researched tentative favorite in the list, git-bug, would be a great start too. (it has gitlab/launchpad/github/jira bridges)…
@alcinnz Nice! @joeyh is doing it a bit like that but more formally with a user-editable wiki in the repo, using ikiwiki, e.g.
So I guess that would be one way of doing it in a portable way on gitea, just ignore the issues functionality and do it in the wiki.
Sign in to participate in the conversation

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).