‹ BackHN Continuity

Thread

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

364 points · 111 comments · alentred

  1. teddyh · · focus · HN ↗
    Just for those people for whom this might be a new concept: There is actually a fair number of these distributed bug trackers: &lt;<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22833037">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22833037&gt;
    1. mcepl · · focus · HN ↗
      And none of them actually work really well. This blog post is over ten years old, but the situation didn’t improve much <a href="https:&#x2F;&#x2F;matej.ceplovi.cz&#x2F;blog&#x2F;current-state-of-the-distributed-issue-tracking.html" rel="nofollow">https:&#x2F;&#x2F;matej.ceplovi.cz&#x2F;blog&#x2F;current-state-of-the-distribut...
      1. gritzko · · focus · HN ↗
        Hits hard.

        I looked into them. Most of them use some CRDT-ish machinery to merge concurrent ticket changes. (Fixing merge conflicts in tickets would be too disappointing.) As a CRDT person, I noticed that implementing CRDT merges in git itself mostly makes that machinery unnecessary. Then you can keep your tickets in plain Markdown, having CRDT merges for both code and metadata. I have it working here btw

        <a href="https:&#x2F;&#x2F;replicated.live&#x2F;blog&#x2F;meta" rel="nofollow">https:&#x2F;&#x2F;replicated.live&#x2F;blog&#x2F;meta

        1. mdrcode · · focus · HN ↗
          Well written blog post! I enjoyed reading it.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.