3 ms·
> 1980s protocol TCP is even older; so what? It works, as does email. It's merely a transport layer. What is required is a well-defined standard to encapsulat
by nine_k 1y ago
> 1980s protocol
TCP is even older; so what? It works, as does email. It's merely a transport layer.
What is required is a well-defined standard to encapsulate relevant data into it: PR definitions, code review comments, approval / rejection votes. This all could be a zipped JSON attachment, for instance.
The code change proper can continue be passed in the patch format. Or the whole thing could arrive via an exposed API endpoint, or even be pushed by git protocol.
A tool could interpret the extracted data and update a database that powers a nice GUI / TUI, and controls a CI/CD interface.
(Now if I only had time to properly design and implement that.)
- skydhash 1y agoWhy all of this? You can just enforce some formatting rules and add a few script to the system mailbox to alter the message (add an issue number, send a notification when a change is accepted and merged, etc,...). No need to complicate stuff. Just send a standard plain text email that follows the rules.