michaelmure

10 ms·

61.
by michaelmure 5y ago
Just a note though, you could centralize git-bug. Standardize/build on what git-bug is doing, and just don't expose the bug data in the same repo as the code. You then just need the extra bits of centralized administration.
62.
by michaelmure 5y ago
That's fair, those are indeed hard to do right or impossible (although I hope we can collectively solve the "people use crypto keys properly" problem at some point).
63.
by michaelmure 5y ago
Let see: -- per-issue/component authorization (secrecy!): git-bug already support internally to attach crypto keypair to an identity and sign/verify the created commits. What's missing is proper tooling around that, ACLs and
64.
by michaelmure 5y ago
I feel like those goals align pretty well with https://github.com/MichaelMure/git-bug , and many are already there. If you feel like pushing your own project is too much to bear, maybe consider contributing to git-bug t
65.
by michaelmure 5y ago
Yes please :) Edit: consider having a look at the development version. While the core feature hasn't changed much, the webUI definitely improved. Also, the core became more robust and ready to accept more features easily.
66.
by michaelmure 6y ago
It might not be exactly what you are looking for, but git-bug[1] is encoding data into regular git objects, with merges and conflict resolution. I'm mentioning this because the hard part is providing an ordering of events. Once you hav
67.
by michaelmure 6y ago
See https://github.com/MichaelMure/git-bug
68.
by michaelmure 6y ago
This could be great to integrate in git-bug[1] if/when kanban get supported. This would be the fronted and git-bug would be the storage/collaboration layer. [1] https://github.com/MichaelMure/git-bug/
69.
by michaelmure 6y ago
It's the whole point of git-bug: breaking the vendor locking. There is a Github bridge that will import the issues (including the complete history). PRs are not supported yet though.
70.
by michaelmure 6y ago
Shameless plug, but that's exactly the aim of https://github.com/MichaelMure/git-bug . It's a distributed bug-tracker: it stores issues (and one day, PRs) within git. You can work offline and you always have a
71.
by michaelmure 6y ago
Haha, that's awesome. It's interaction like these (and pretty much this whole thread) that make me think that there is value in this idea. It just has to reach some completion with a good UX ... I have a bunch of git-bug.tld dom
72.
by michaelmure 6y ago
If you like this idea of embedding a bug-tracker (and eventually the code review) within a DVCS, I'm working on a project[1] that does that for git. [1]: https://github.com/MichaelMure/git-bug
73.
by michaelmure 6y ago
From what I've seen it's quite common to use a library to output those escape code. Given that, there is often a flag to disable all those colors/decoration at once without implementing a fallback specifically. > Support f
74.
by michaelmure 6y ago
My point exactly. Some terminals do the expected thing of doing "bold off" because that make the mapping of codes regular, some follow ECMA-48 and do "double underline" even if that means that "bold off" is not
75.
by michaelmure 6y ago
A new standard would also make it easier to fallback to no colors/decoration if the user wish so. At the moment, there is no way to do that without a flags or similar for each app. Even detecting if the terminal support colors is a pai
76.
by michaelmure 6y ago
It looks to me that the reality is closer to "40 years of hack over something that was not meant to be a standard (a popular hardware terminal from the 80s)". I'll give you just one example of the madness that is sometimes re
77.
by michaelmure 6y ago
Shameless plug: https://github.com/MichaelMure/git-bug Yes I realize the irony of pushing a project hosted on github when it's down.
78.
by michaelmure 6y ago
"git" is in the name but it's actually not tied to it so much. If you can implement those interfaces [1], you can port it to another VCS and everything else will work. It's not trivial but entirely possible. [1]: https:
79.
by michaelmure 6y ago
I won't comment on BE because I simply don't know enough about it but I'll try to clarify some things. Instead of storing bug state, git-bug store intent of the users in a chain of commit. When read, those intents are inte
80.
by michaelmure 6y ago
Thank you :)
81.
by michaelmure 6y ago
Not yet but it's in the works.
82.
by michaelmure 6y ago
What sort of maturity sign would you like to see?
83.
Show HN: Git-bug – Distributed bug tracker, or what to do when GitHub is down(github.com)
153 points by michaelmure 6y ago|55 comments
84.
by michaelmure 7y ago
Shameless plug regarding the issues: https://github.com/MichaelMure/git-bug
85.
Show HN: Read and edit offline your GitHub/Gitlab/Jira issues with Git-bug(github.com)
4 points by michaelmure 7y ago|0 comments
86.
Show HN: Mdr, a Markdown Renderer for the Terminal(github.com)
3 points by michaelmure 7y ago|0 comments
87.
by michaelmure 7y ago
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
88.
by michaelmure 7y ago
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
89.
by michaelmure 7y ago
I'm building one: https://github.com/MichaelMure/git-bug
90.
by michaelmure 7y ago
I'm working on this, have a look at https://github.com/MichaelMure/git-bug

More ›