Cayetano Santos#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.
Stéphane Bortzmeyer@xalofar J'imprime la dernière mise à jour du protocole SMTP https://datatracker.ietf.org/doc/draft-ietf-emailcore-rfc5321bis/
Simple Mail Transfer Protocol
This document is a specification of the basic protocol for Internet electronic mail transport. It (including text carried forward from RFC 5321) consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. The document also provides information about use of SMTP for other than strict mail transport and delivery. This document replaces RFC 5321, the earlier version with the same title, and supersedes RFCs 1846, 7504, and 7505, incorporating all the relevant information in them.