#B4 is a tool created to make it easier for project developers and maintainers to use a distributed development workflow that relies on patches and distribution lists for code contributions and review.
#B4 is a tool created to make it easier for project developers and maintainers to use a distributed development workflow that relies on patches and distribution lists for code contributions and review.
Ever wanted to contribute to #guix or #emacs commons ? A bit scary about the #email based workflow ? Afraid of having to manipulate thousands of emails locally ?
No worries: https://yhetil.org, a public-inbox based service, provides a nice web front end to browse for patches, issues and bugs you may contribute to fix: thread overview, outlining, reply links, thread download in #mbox format, everything you need to start contributing is there.
Mailing lists vs Github
https://begriffs.com/posts/2018-06-05-mailing-list-vs-github.html
> Pros and Cons of Two Styles of OSS
#deltachat, #decentralized #instantmessaging done right ? π€
Fully #distributed, based on #freesofware, #email and well known internet standards.
2018 article "The advantages of an #email-driven #git workflow", by @drewdevault, remains valid even today.