Thread

Git-bug: Distributed, offline-first bug tracker embedded in Git

364 points · 111 comments · alentred

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. derpitron · 1790349858 · focus · HN ↗
  > - have the webui accept external auth (like github oauth) so that it can be a public portal and accept external interactions
  Have you looked into ForgeFed? It's a WIP plan for different Forgejo based forges to federate with each other. <a href="https://forgefed.org/" rel="nofollow">https://forgefed.org/
  There's also this: <a href="https://indieauth.net/" rel="nofollow">https://indieauth.net/ though I haven't looked into it. I hope you could integrate one of these into your planned OAuth/account system!

Unofficial Hacker News client; not affiliated with Y Combinator.