Thread

1. michaelmure · 1790343402 · focus · HN ↗

   Hi, author here, nice to see some interest :-)

   FYI, this is my near-term roadmap:

     - have the webui accept external auth (like github oauth) so that it can be a public portal and accept external interactions
     - have the webui expose a git remote endpoint
     - slightly rework identities (and likely root them in did:plc for pubkey distribution, the identity system from bluesky, without being an ATProto thing), which would allow to share identities between repos way more naturally
     - extend to support pull-requests, possibly CI. That would make it a somewhat complete local-first forge that you can also self-host trivially
   

   Also, while there is some attention ... I'm considering working on this full time. If you have some advice or opportunities on how I can support myself doing this, let me know!

   1. deprave · 1790358607 · focus · HN ↗

      Thank you for working on this, I love the idea. What surprised me was the way user identities is managed, I assumed you’d use whatever git uses. Would you mind elaborating on that?

      1. khimaros · 1790358939 · focus · HN ↗

         same question here. the other limitation i ran into immediately was only having two status types: open and closed

         1. michaelmure · 1790360208 · focus · HN ↗

            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.

            1. khimaros · 1790361758 · focus · HN ↗

               that sounds great and looking toward to it. is there an issue i can subscribe to?

               1. michaelmure · 1790362306 · focus · HN ↗

                  There is <a href="https:&#x2F;&#x2F;github.com&#x2F;git-bug&#x2F;git-bug&#x2F;issues&#x2F;63" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;git-bug&#x2F;git-bug&#x2F;issues&#x2F;63, but I have plenty to do before that.

Unofficial Hacker News client; not affiliated with Y Combinator.