🥳🎉 "Git Bug" is here, folks! Because who doesn't dream of embedding a bug tracker right into their version control system? 🙃 Welcome to the future, where every bug is a feature, and every feature is... just another bug. 🚀🔧
https://github.com/git-bug/git-bug #GitBug #versioncontrol #bugtracker #techinnovation #softwaredevelopment #HackerNews #ngated

Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges

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

#HackerNews #GitBug #Distributed #OfflineFirst #BugTracker #Git #Bridges

@technomancy it's nice to learn about these alternatives but I don't think I've seen any that address the big draws of github, one of which is issues.

I few years ago I looked for decentralised alternatives to GitHub issues. I found gitbug which is very nice and was working quite well back then & able to import/export.

The was nothing else usable so I made a proof of concept for a web ui on top of #gitbug to show a #github like system working with decentralised #p2p storage. See #p2pgit
#git

@whynothugo Here's a more hands-on one from the #sourcehut folks: https://git-send-email.io/

After hosting my own #GitHub-style forge for many years (used #forgejo last), most of my private projects are now just plain ssh-hosted repos. Managing the ever growing complexity just stopped being worth it for me. #GitBug and #cgit (simple read-only web frontend) is all I need. Accepting patches/issues via mail only is not ideal, but not dealing with low-effort PRs and lazily filed issues is nice too.

@cas @pojntfx For what it's worth, I do agree we need something else.

Email is only slightly more resilient to censorship than full centralization.

I think accepting more centralization is a move in the wrong direction.

Is #GitBug the ultimate solution? I don't think so. It's the main one in development and usable right now though.

The corposcum PR apparatus pushing their centralized #SaaSS so hard hasn't helped, distracting many capable of coming up with decent alternatives from doing so.

@pojntfx @cas I have not found any fully distributed issue/patch management system compatible with #Git that has had any adoption, the next closest is #decentralized #email which, if mirrored onto users' machines (as they should be) can also count as #distributed.

#GitBug is such a system but since it has barely any adoption…

#Fossil meanwhile includes all the necessary tooling, but has this annoying and misguided focus on cathedral development style that greatly limits its applicability.

@nicolas17 @marcan @lschuermann #GitBug handles the issues part, if you use it.

The pull requests though? Sort of, if you decide to use the issue tracker to deal with them.

@jfrench @donkeyblam @baldur #Git has some glaring omissions in that design that #Fossil doesn't have (all the bug-tracking and wiki features).

#GitBug (https://github.com/MichaelMure/git-bug) attempts to fix that, but it hasn't been widely adopted.

(Yes, ironic choice of hosting, I know. Incidentally Gitlab is also enshittifying.)

Working over #email also works better if you also use #PublicInbox (https://public-inbox.org/README.html), as synchronization of an archive is non-trivial if you just use mailman's builtins.

@knu @fasterthanlime Yeah, if #fossil wasn't quite so insistent on the Cathedral model in its handling of various things, I'd use it immediately.

Its incorporation of all the necessary project management features is also great. #Git has no standard way to handle that and #GitBug (https://github.com/MichaelMure/git-bug) is not used by most (instead using external services and inducing unnecessary centralization).

I just migrated the 50 odd repos from my #selfhosted #Forgejo instance used for small and personal projects and deleted it (which ran #Gitea and even #Gogs before).

The dev-ops push has made it too big, slow and difficult to maintain for me (new versions frequently breaking things). 90% of the projects only need issue tracking, pull requests and a wiki anyway.

I'll now try a barebones ssh-hosted setup with git hooks, #GitBug and #markdown files instead. #minimalism

@happyborg

Do you have a link to what you've done so far? Any design documents?

#github #enshitification #p2pgit #git #p2p #gitbug #git

Jeeze is the new #github home feed bad. 🤦‍♂️

The #enshitification of Github by Microsoft is accelerating.

Wish I had time to work on #p2pgit. That aimed to move the social and #git features into the browser using Svelte/Rust/WASI and share repos on p2p storage. So nothing to self host, no third party service etc. True #p2p.

I got the proof of concept working, including support for issues based on #gitbug, but it's too much work for me to get full #git support in the browser.

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

@toxi How’s #Codeberg handling issues, PR:s and such?

Ideally any post- #GitHub host would make use of something like #GitBug (https://github.com/MichaelMure/git-bug) or similar to have the issue data live with the code repositories

That and/or do a #Fediverse / #IndieWeb approach and have people publish their issues and pull requests on their own sites / instances and then notify the upstream repository about that. See eg: https://indieweb.org/issue

Is #Codeberg doing any of that?

@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

@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.

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

#gitbug is a #Git-based #decentralized bug tracker.

git-bug is a Git extension that allows for a Git repository to have integrated, distributed bug tracking compatible with any Git host. Once a repository is initialized issues can be created through a command line, terminal, or local web interface. git-bug features bridges which can sync from and/or to various bug trackers including #GitHub and #GitLab.

Website 🔗️: https://github.com/MichaelMure/git-bug

#free #opensource #foss #fossmendations #programming