• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • But the nice thing about email is it’s decentralized, and everyone already has it.

    That is true, but in the case of email as an issue tracker: only the people who have received it will know of its existence (unless it’s mirrored on public facing websites - like Debian does with their issue tracking).

    The thing we’d lose is the “ease of access”. Tbh, I’d see Usenet being a better distribution medium than email for OSS apps… but I really appreciate the intention behind solutions like git-issues: move the issue tracking into the same tools used to track code changes. It, in my opinion, is more in line with K. I. S. S.


  • You make a valid point regarding losing important contextual information like PR and open bugs.

    However, I don’t think email offers the same level of visibility as we currently have with github workflows.

    There is an creative Git based issue tracker, I used called git-issue. Basically, the entire bug/issue/pr process is captured as yaml (I think) files, which are kept in a dedicated branch.

    When I used it (as I wanted a self-hosted bug tracker), I found it functional but a bit cumbersome. However, I could see someone creating a very nice github like web interface for it.