gRFC P6: grpc-io-announce mailing list

[Jung-Yu (Gina) Yeh]

Hi,

Eric and I put together a gRFC to create an "announce" mailing list to have a high-signal method to notify users of important announcements, especially for security and reliability issues.

https://github.com/grpc/proposal/pull/458

Feedback welcome.

Best,

Gina

--

Jung-Yu (Gina) Yeh Software Engineer gin...@google.com

[Daz Wilkin]

LGTM

Since this is a new announcement list, please consider including some form of metadata at the beginning of the message content to facilitate (automated) parsing/routing.

[Eric Anderson]

On Tue, Oct 15, 2024 at 7:13 AM Daz Wilkin <daz.w...@gmail.com> wrote:

Since this is a new announcement list, please consider including some form of metadata at the beginning of the message content to facilitate (automated) parsing/routing.

The group was already configured to use [grpc-io-announce], but I just added it to the gRFC. I just adjusted the group to send emails as grpc-io-announce@ instead of the sender's address, which is probably better than a magic subject. I can update the gRFC to mention that.

Daz, does that sound good?

[Daz Wilkin]

Yes, thank you.

I was wondering whether messages could be prefixed with metadata e.g. a YAML block that could be machine read

---

priority: foo

languages: ["go","python","rust"]

...

[Eric Anderson]

 

Are there widely used systems that support that? It seems like at most one person would bolt together something to process and route those. I doubt it is worth the time to define the format, and even if we did it seems unlikely we'd consistently get the format right when sending.

I had considered using the + syntax for things, like grpc-io-announce+go@, but that doesn't work well for multiple languages. KISS. There are very few of these emails, so recipients just look at the subject line. We won't be sending enough emails to the list to get good at a complicated process.