michaelmure

8 ms·

31.
by michaelmure 4y ago
You might be interested by git-bug and https://github.com/MichaelMure/git-bug/blob/master/doc/model... , which seems to be exactly what you describe. (Disclaimer: author).
32.
by michaelmure 4y ago
https://github.com/MichaelMure/git-bug Offline-first bug tracker (and soon-ish forge) embedded in git. I keep working on this because the idea makes a lot of sense to me, because I learn a lot from it and it benefits m
33.
by michaelmure 4y ago
Really cool. I have with git-bug[0] similar properties (offline first, identities, generic "crdt like" base data structure... ). Maybe you'd like to have a look and improve each other's design. [0]: https://gi
34.
by michaelmure 4y ago
A bugtracker being "branch aware" and able to say where an issue started, where it was fixed ... can (and should IMHO) be a different concern than how the data is stored and how conflict resolution happen. By conflict resolution h
35.
by michaelmure 4y ago
It's significantly more friction for little benefit compared to git-bug's solution. First, storing this data alongside the code means requiring everyone agreeing to use that tool (quite high ask). Then, that means that you let git
36.
by michaelmure 4y ago
git-bug's author here with my 2cts. For what it's worth, I was aware of git notes during my original design process, but I found them clunky. I realized they would not be enough on their own to do conflict resolution and I'd
37.
by michaelmure 4y ago
Thank you for that idea, I haven't considered that. I'm not too sure about how feasible that is as right now bridges sit on a sort of framework for configurations, credentials, events ... that seems uneasy to break into a plugin p
38.
by michaelmure 4y ago
I haven't considered myself or git-bug worthy enough to bother him :-|
39.
by michaelmure 4y ago
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 integratio
40.
by michaelmure 4y ago
It does not ... yet. Nothing prevent from making git-bug "branch aware", just someone writing the code for that.
41.
by michaelmure 4y ago
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 t
42.
by michaelmure 4y ago
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.
43.
by michaelmure 4y ago
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
44.
by michaelmure 4y ago
No plan but it's typically something that is brought by an eternal contributor as I need to focus on the core and I don't use those other tools. If you are up for the task, please do! A "good enough" bridge (config+impor
45.
by michaelmure 4y ago
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
46.
by michaelmure 4y ago
As mentioned in the release notes, the intent is really to have a reusable data structure in git capable of conflict resolution, plus all the tooling around that. So if you want to build a tool using the same techniques but outside of git-b
47.
by michaelmure 4y ago
No, it's completely separated from your normal code and branches and doesn't pollute your development workflow. git-bug's data is stored in hidden branches (not in the way you think about branches though).
48.
by michaelmure 4y ago
They have been quite ok[1] about the trademark aspect, but they do have a point about the namespace grab. I'm actually at a point where I do consider opting out of the git integration[2], as the introduction of new entities (project bo
49.
by michaelmure 4y ago
... which are bidirectional and incremental, meaning that you can use git-bug as an offline and local copy for github[1], without having to convert everyone on the project to that tool. [1] https://github.com/MichaelMure&#x2
50.
by michaelmure 4y ago
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!
51.
by michaelmure 4y ago
https://github.com/MichaelMure/git-bug/blob/v0.8.0/doc/model... should answers all those question. In short: merge conflict are handled.
52.
by michaelmure 4y ago
Author here, happy to answer questions.
53.
by michaelmure 4y ago
Hi, git-bug's author here. That's pretty interesting way to have a text interface for PRs. I'd like to have something like that in git-bug.
54.
by michaelmure 4y ago
Hi everyone. I'd like to show you the result of a long maturation process, the reusable distributed data structure of git-bug, that you can use in your own project to store your entities in git and collaborate through git remotes. I&#x
55.
Show HN: Git-bug's reusable data model(github.com)
2 points by michaelmure 4y ago|1 comments
56.
by michaelmure 4y ago
One thing I've always wanted to see visualized if how the distribution of authorship of code evolve over time. Who wrote most of the code? Does that code remains or does it get rewritten? Who wrote the most foundational and time resist
57.
by michaelmure 4y ago
Do you fancy re-thinking buf trackers? I'm looking for help over at https://github.com/MichaelMure/git-bug to create a distributed bug tracker embeded in git, with bridges. It's close to be ready for prime ti
58.
by michaelmure 5y ago
I've been doing something a bit similar with https://github.com/MichaelMure/git-bug/tree/master/entity/da... if you care about digging. It's a generic distrubuted data structure in git, wi
59.
by michaelmure 5y ago
git-bug author here. It's still not v1 where there would be some sort of backward compatibility guarantee, but it's close if you are using master. Note though that even without that guarantee, there is git-bug-migration to provide
60.
by michaelmure 5y ago
It seems to be a polarizing idea. Many people can't stand it, but also I suspect that very few actually worked with something like that. In any case, I believe that it's better to build a data model/storage without that conce

More ›