https://github.com/driusan/bug <– cool way to handle/manage project issues/bugs

@abucci@anthony.buc.ci Hmmm you raise a good point 👌 Signal/Noise is important in any design and I tend to agree here with you. Makes git-bug far more appealing in that regard because of the way it stores data…

@prologic@twtxt.net it’s possible to store any missing data using the git-bug approach to add any missing functionality to a git repo without relying on external data storage, can’t we?

@justamoment@twtxt.net I think, at least that’s the idea, and it allegedly doesn’t pollute the actual repo with unrelated files (I don’t think) – I still haven’t been able to get it to work locally though so hoping someone will answer my comment on the issue. But yeah depending on how git-bug evolves over time we could just integrate with it “somehow”

@prologic@twtxt.net I see, pretty cool.

But personally I prefer the file based approach though, you have a friendly folder that lets you open anyway you want without fiddling the repo, you can use a separate repo if you don’t like it in the source and everything is tracked in the same way without having to manual dig in them if you don’t want to use a given tool.

This is one that could be a better solution if you like that approach too: https://github.com/dspinellis/git-issue

Being file based also let you build a “protocol” on it that can be detached from the repo in itself and let you manage it in a similar fashion of twtxt.

What do you think?

@justamoment@twtxt.net Yeah that’s another pretty similar way of doing the same thing I guess? Basically a bunch of files in the same repo in even a separate repo right? 🤔

@justamoment@twtxt.net I’m still thinking about how we can make Git + Twtxt work in a way that is a sort-of “socialised” collaboration of a Git repo’s issues and reviews of patches… 😅

@prologic@twtxt.net “Git.social” then! 😎

Git “pods” with “repos”, “issue” and “review” feeds.

Every changes on a repo is notified in a repos feed.

Each issue or review is a file in a folder with an hash and people can reply on the conversation, or at least the “notification” of it in their feed.

A nice approach I saw in Trello, you can email a card ID and it get embedded in the card, it can be done here too on the file, as to not have everything spread on hundreds of feeds.

Working like this you can integrate twtxt but not rely on it entirely, letting users use it without it, I’d see this as generic integration though, so other can add more “bridges” (like in git-bug) to their liking.

How is it?

@justamoment@twtxt.net I love ti 😍

Too bad git.social is taken 😅 It would have made a great domain and project name, but you are on to something 😍

@prologic@twtxt.net Glad we’re getting there! 🥳