Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/
#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail
The documentation of #publicinbox is really bad.
I just cloned the git public inbox, how can I now read it?
Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.
I mean, I don't care for your 5 person project, do what you want.
But for large projects, that really is the only way to develop that truly scales.
Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!
That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?
Bottle in the sea to the #fediverse, looking for author and owner of the great https://yhetil.org unofficial online service.
yhetil.org provides #publicinbox mirrors to main #emacs, #guile and #guix maillists, facilitating a practical means of browsing through history of exchanges, replying and contributing.
@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.
HTML email. Most #sourceware projects allow it, if there is at least a text/plain alternative.
But #publicinbox is not so forgiving, it only allows plain-text emails, HTML is rejected by default.
So the https://inbox.sourceware.org archive was incomplete.
We now have a filter that removes redundant HTML parts before storing in public-inbox. And we re-imported missing emails to make the archive complete.
But please don't sent HTML email. It will make DKIM verification of your email impossible.
@Hyolobrika @BrodieOnLinux In that case I would still recommend using some in-repository bug-tracking such as https://github.com/MichaelMure/git-bug, so that loss of the hosting instance for whatever reason doesn't kill the project.
The usual answer of #MailingLists https://sourcehut.org/blog/2020-10-29-how-mailing-lists-prevent-censorship/ & a #PublicInbox archive is also applicable to #AnonymousNetworks, but requires more setup. Using some of the NNTP servers on those networks for duplicating also works.
musicmatze 
Alex
Cayetano Santos
LisPi
Sourceware