Hacker News Reader

michaelmureon Show HN: Git-bug – Distributed bug tracker, or what to do when GitHub is down

Thank you :)

michaelmureon Show HN: Git-bug – Distributed bug tracker, or what to do when GitHub is down

Not yet but it's in the works.

michaelmureon Show HN: Git-bug – Distributed bug tracker, or what to do when GitHub is down

What sort of maturity sign would you like to see?

michaelmureon Dgit: Git with decentralized remotes

Shameless plug regarding the issues: https://github.com/MichaelMure/git-bug

michaelmureon Ask HN: BugsEverywhere was a great idea – why didn't it catch on?

Shameless plug warning. I'm the author of git-bug (https://github.com/MichaelMure/git-bug), a distributed bug tracker actively developed (even a gsoc this summer!). If you are interested by this topic I would very much like you to give it a try or even contribute.

git-bug try to improve over the previous iteration of this idea in several ways. To answer your question, those are what I think prevented them to catch on:

- it doesn't pollute your project: no files are added alongside your code, no mess during a merge, bugs are stored in your repository but decoupled from your code workflow

- it doesn't impose an interface: as you prefer, you can use the CLI tools, the interactive terminal interface or even a webUI. You could also integrate it to your editor, CI system ...

- it allows outsider of the project, client, users ... to browse and open bugs, without asking them to install anything. Admittedly, git-bug is not there yet, but the goal is to have the webUI work as a public portal that a project could host easily, accepting authentication from outside system (github OAuth ...).

michaelmureon Ask HN: BugsEverywhere was a great idea – why didn't it catch on?

Author of git-bug here, the webui is definitely just a proof of concept for now. I would definitely love to have someone help over there.

As for the alpha status, yes, the data model will likely change before becoming stable, but i suppose i have enough user to warrant a migration tool if that happen.

michaelmureon GitHub Outage Currently Ongoing – Issues, PRs, Notifications

I'm building one: https://github.com/MichaelMure/git-bug

michaelmureon Sunsetting Mercurial Support in Bitbucket

I'm working on this, have a look at https://github.com/MichaelMure/git-bug

michaelmureon Chinese developers fear the tech war will cost them access to GitHub

As another data point, I've seen more contribution and feedbacks to https://github.com/MichaelMure/git-bug (distributed bug tracker) than I expected from the chinese community.

michaelmureon Easily Review Comments in Atom – The GitHub Blog

I want to add code reviews in git-bug at some point: https://github.com/MichaelMure/git-bug

michaelmureon Ask HN: What would your ideal issue tracker look like?

Yes. `git bug webui` will start a local web server to serve a js app and a GraphQL API as a backend.

michaelmureon Ask HN: What would your ideal issue tracker look like?

It might still be a little too early, I might still make non-compatible changes in the data model. But that's not too far.

I plan to eventually have the ability to keep reading older version of the data, but it's not there yet.

michaelmureon Ask HN: What would your ideal issue tracker look like?

Shameless plug: I'm building an issue tracker integrated in your git repository, decentralized, fully working offline and from your terminal/web browser.

If you want to join the fun, feel free :-)

https://github.com/MichaelMure/git-bug

michaelmureon Ask HN: What would your ideal issue tracker look like?

https://github.com/MichaelMure/git-bug

I very much welcome any help to make that happen :-)

michaelmureon Show HN: Git-bug 0.4: performance, comment edition, GitHub importer

Hi HN !

After my first presentation of git-bug here [1], I'd like to show you the progress made.

While the original version was pretty much a prototype, the 0.3 version [2] featured a caching/indexing layer with its query language, easily handling 10k+ bugs.

This last version [3] include among others things a feature that was asked a lot, a Github incremental importer.

While this is still not 1.0, it's close. Work left before that is mainly the rework of the identity management [4] along with a Github incremental exporter [5] to make sure that the data model is done well enough and won't change much anymore in the future.

[1]: https://news.ycombinator.com/item?id=17782121 [2]: https://github.com/MichaelMure/git-bug/releases/tag/0.3.0 [3]: https://github.com/MichaelMure/git-bug/releases/tag/0.4.0 [4]: https://github.com/MichaelMure/git-bug/issues/55 [5]: https://github.com/MichaelMure/git-bug/issues/56

michaelmureon Git-bug 0.4.0: performance, comment edition, GitHub importer

Hi HN !

After my first presentation of git-bug here [1], I'd like to show you the progress made.

While the original version was pretty much a prototype, the 0.3 version [2] featured a caching/indexing layer with its query language, easily handling 10k+ bugs.

This last version [3] include among others things a feature that was long awaited, a Github incremental importer.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

Damn, your comment moved my shameless plug at the very end of the thread :(

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

Bugs Everywhere: - bug are stored as files alongside the normal code, which is different than the vast majorities of bug tracker operate, and also rely on git to merge properly the bug's files in a correct state. In git-bug, merge is simply rebasing commit, there is no conflict. - last commit was in 2013

As far as I understand, the data model of git-bug is much closer than what github does internally. If you look at githug's API, you will find the same timeline of edit operation, so it might help them to pick up the idea.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

Bugs are referenced at refs/bugs/<id> and refs/remotes/<remote>/bugs/<id> and those are not garbage collected.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

The same idea for the storage and merge can certainly be applied to other use cases. A wiki would probably be kinda tricky because you would need a an edit operation for each change in the text but that's probably doable.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

There is manual merging code in git-bug [0] only because git doesn't provide a low-level command to rebase a branch onto another without touching the index. I don't think it's an intended limitation of git but more likely no one had a use case for that so they simply used the normal index.

Apart from that, a normal git rebase would merge two versions of the same bug conflict free. Each commit is independent from the other. A merge is simply moving the new operations at the end of the chain of edit.

If for instance, that means that you closed a bug that is already closed, well the bug is still closed and your action will still be displayed in the timeline.

[0]: https://github.com/MichaelMure/git-bug/blob/c974cc022d3ecd2e...

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

If you missed it on the readme, I wrote a document that explain how it works behind the scene: https://github.com/MichaelMure/git-bug/blob/master/doc/model...

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

Bugs storage and management is entirely disconnected from the regular code and branches. That said, it probably make sense to be able to tag a bug with the branches that are affected.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

Not yet, but that might be a good feature. Also, the goal is to have an extensible data model where you can store whatever metadata you want to support arbitrary external bug tracker.

Please open an issue so we can discuss that.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

The problem with this approach is that usually your work computer is not reachable from internet, so ActivityPub won't work here. It might be used to create a federated GitHub though, but it's outside of the scope of git-bug for now. The project is just one month old ;)

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

`git gc` will garbage collect what is not referenced by a ref anymore, including arbitrary references. So it's fine !

As each bug reference the file blob needed, once your delete a bug, `git gc` will clean these blob as well.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

Shameless plug: if you like this, I'm looking for a remote job. My email is on my Github profile and my resume is here: http://pellelatarte.fr/dl/resume.pdf .

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

Each bug is stored independently and in particular independently of the source code, so older bugs could be archived or simply left on the git remote.

I don't see your point about the permission model.

You will have access permission for the code as you normally do for your git remote as well as an extra user for the web UI that will store bug edits as one of the "public" user with whatever external authentication system you want.

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

That make sense. I'm waiting to have a clear design for the CLI UX to improve that. Feel free to raise your voice: https://github.com/MichaelMure/git-bug/issues/2

michaelmureon Show HN: git-bug – Distributed bug tracker embedded in git

The web UI is designed to, in the future, be used as a public interface as well. It would need to have some kind of authentication to identify users though.