Is #GitBug the only one trying to fix #Git's glaring implementation holes, or are there others to also keep an eye on?

#VCS #SCM #DVCS

@elly Unfortunately the only #DVCS that did metadata properly (#Fossil) decided it wanted to go all-in on cathedral and no one else even tried (some tried to patch it on top of #git, like #GitBug but that never got popular) so... we're stuck with that.

Everything else fails by requiring unnecessary centralization.

#VCS

@tychi hey, good to hear from you. How's it going?

Someone did build a nice web UI for the proof of concept #p2pgit but then moved on and I've not been able to take it much further. I can't commit the time it needs to move from gitbug/Golang to something without the large Go runtime. I was hoping to start with #gitbug style issues in JS and gradually shift to #Rust #WASM but it's too much for me alone.

Shame because #SafeNetwork is coming together and lots of value in a #decentralised #git

git-bug synchronization via pure git commands is reasonable. So the main requirements for git-bug adaptation are now fulfilled.

#git #gitbug

https://todo.sr.ht/~splitcells-net/net.splitcells.network/122

So, I think the decision was made: I'll first do a test run with git-bug and see if it works. If this is the case, it will be my permanent solution:

https://todo.sr.ht/~splitcells-net/net.splitcells.network/122

#gitbug #opensource

@akib @dachary @forgefriends @hostea @forgefed @gitea @codeberg Since you mention a list (assuming you mean mailing list?), how about this hybrid of all ideas: bug reports/comments go to an account that checks the sig (perhaps using a #procmail script). If the sig checks out, the msg is automatically submitted via #gitBug to the upstream git db. If the sig fails or is non-existent, the msg goes to a mailing list.

@akib @dachary @forgefriends @hostea @forgefed @gitea @codeberg It would also be useful to incorporate #gitbug (https://github.com/MichaelMure/git-bug). IIUC, someone could create a new bug report within git, and then submit it upstream. Not sure if that’s done by PR but it should be looked at because it would make repos more portable, as the bug tracker data should migrate with the code in a migration anyway.

Looks like git is slowly catching up with fossil's features.

#TIL about bug-tracking in git using git-bug
https://github.com/MichaelMure/git-bug

Already started using this with #nimcoon. I think I can drop my org-mode file with TODOs now.

#git #fossil #gitBug #bugTracking

https://github.com/MichaelMure/git-bug# #GitBug stores all your metadata in #git repo , I am wondering if data can be extracted/imported from exisiting #hosting services