Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

51–60 of 82 posts

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

#51

Post by bryanlarsen »

wankle wrote: post #46
foreigner wrote: post #28

I understand why the bug IDs are hashes, but that's going to be pretty inconvenient for practical use. Yes I know we manage it with Git commit names, but bug IDs are printed and spoken much more than commits, e.g. when communicating with a test team, management, or even in release notes. I wonder if we could use some sort of distributed naming scheme for this, similar to Blockchain DNS?

Blockchain is a terrific idea! Make it blockchain!! Not "block chain" like the git log but "blockchain" make all software use blockchain to make the world a better place for all of us!!!

The git log is a block chain.

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

#52

Post by smoyer »

michaelmure wrote: post #48
wankle wrote: post #47

Earlier quoted context omitted.

I agree, it seems self-defeating that the tool is independently distributed but offers bridges.

I disagree. Bridges are a great on-ramp, as you can individually choose to adopt the tool without having everyone on the project (let alone users) agree to switch. It breaks the network effect. It's also a much needed migration path as you don't want to lose your project history. As a bonus, it's also a way to have backups, even if you keep using your centralized forge.

You know I'm a zealot! ... Imagine the day when that network effect is flipped and new projects start with git-bug and spin up a webui to allow the decentralized stragglers to participate.

In the interim, it would be cool if projects on GitHub (e.g.) would run the bridges as an action to keep GitHub issues synced with git-bug commits right in the repository.

EDIT: Of course the above implies we all learn to use git without a central serve too ... Something I'm not ready for either.

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

#54

Post by fdye »

foreigner wrote: post #28

I understand why the bug IDs are hashes, but that's going to be pretty inconvenient for practical use. Yes I know we manage it with Git commit names, but bug IDs are printed and spoken much more than commits, e.g. when communicating with a test team, management, or even in release notes. I wonder if we could use some sort of distributed naming scheme for this, similar to Blockchain DNS?

+1 to this commenter

Really cool idea, but I would second a shorter and sequential way of ID'ing bugs. Its common in QA flows to use the JIRA-like shorthand to discuss/assign tickets. -. Proj-alias is usually like 3 letters/nums (project configurable). So like SEC-3640, QWE-123, etc. Human-readable/discussable bug ID is gonna be something desired. Hash could stay as an alternate for those with deeper GIT knowledge, but its gonna get verbose to discuss a ticket.

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

#55

Post by michaelmure »

hosh wrote: post #49
michaelmure wrote: post #37

Earlier quoted context omitted.

I haven't but I'm not sure it's really necessary. What needs to happen first is a large enough usage of git-bug, or at least a large enough use case coverage. To do so, I think it needs: - support for pull-requests - support for external auth in the webUI, to make it work as a public frontend where anyone can browse and interact with bugs like any other forge If that happens and people are convinced, I'd think that g…

I had been doodling ideas about a distributed forge. It would allow for a local-first environment. Updates can be broadcast on something lile ActivityPub, and some automatic way to pull from Githuv. Discussions can go there, though git-bug may be the better way to go. My main goal is resiliency. A typical Elixir/Phoenix project, for example, will have some dependencies on github. If github or the internet goes down,…

What you are describing is exactly within git-bug's scope, and really not that far away! I'd love to make that happen, but unfortunately I have a demanding day job and rely on contributor's help.

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

#56

Post by michaelmure »

jarbus wrote: post #53

How do I remove git-bug from a repository?

Delete .git/git-bug, .git/refs/bugs, .git/refs/identities, .git/refs/remote/*/bugs and .git/refs/remote/*/identities.

I'm considering adding a dedicated CLI command for that as it's a common concern.

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

#57

Post by michaelmure »

gregwebs wrote: post #50

Does this at all help connect a bug to the source control? For example, knowing that a bug is closed at a certain git revision?

It does not ... yet. Nothing prevent from making git-bug "branch aware", just someone writing the code for that.

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

#58

Post by anonyme-honteux »

bryanlarsen wrote: post #51
wankle wrote: post #46

Earlier quoted context omitted.

Blockchain is a terrific idea! Make it blockchain!! Not "block chain" like the git log but "blockchain" make all software use blockchain to make the world a better place for all of us!!!

The git log is a block chain.

Nope the git log is a merkle tree. The blockchain is a merkle tree plus all the layers of overengineering you need to have a consensus algorithm. And usually you "need" a consensus algorithm mostly for ideological reasons. My view is that building trust is better than assuiming it can't or shouldn't exist.

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

#59

Post by modeless »

michaelmure wrote: post #4

Hi, author here. Happy to answer questions. Version 0.8 just got out[1]. For the next one, I'll try to focus on making the codebase fully ready for multi-entities and introduce a Project Board. Later we can add support for code review! If you are looking for how it works, you can have a look at the data model introduction[2]. git-bug is only pushed forward by volunteers so it's taking its time to fully grow, so I'll…

Very cool idea, was it inspired by Fossil? I would totally use this if it had a VSCode extension.

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

#60

Post by michaelmure »

modeless wrote: post #59
michaelmure wrote: post #4

Hi, author here. Happy to answer questions. Version 0.8 just got out[1]. For the next one, I'll try to focus on making the codebase fully ready for multi-entities and introduce a Project Board. Later we can add support for code review! If you are looking for how it works, you can have a look at the data model introduction[2]. git-bug is only pushed forward by volunteers so it's taking its time to fully grow, so I'll…

Very cool idea, was it inspired by Fossil? I would totally use this if it had a VSCode extension.

I was aware of fossil but never used it. It's not a new idea, it has been attempted many time before. Hopefully that one is the one reaching large usage :-) Regarding VSCode, the CLI commands are designed to be used for such integration. Hopefully someone makes it.
Post reply on HN