[Meta] Consider having a separate repo per explainer

[tomayac]

The current "mono repo" approach makes following explainers extremely tedious. Random email subject example from my Inbox today:

[MicrosoftEdge/MSEdgeExplainers] Is JavaScript API necessary and if so, should there be a dedicated event for it? (#380) 🤔

I know each Issue has a label, but they don't get carried over to email notifications. My flow is to mute email notification threads I am not interested in in Gmail, sometimes on GitHub. The current way MSEdgeExplainers works forces me to click through to each thread to figure out what explainer it is for, and if I want to follow it or not. I'm short before declaring email bankruptcy.

Thanks for your consideration! If it's just me, happy for others to share their (email-notification-based!) workflow. Maybe I just don't know the trick everyone else knows.

[tomayac]

Related: WebKit/explainers#49.

[travisleithead]

Thanks @tomayac. Great feedback. I guess I take it for granted that I'm in a perpetual state of "email bankruptcy" from GitHub and other standards-related notifications.

Switching to a repo-per-explainer is a relatively big change, and frankly one that I don't think is necessarily warranted for some explainers, for example those that may not be substantial enough to need an entire repo (before they progress to a full spec and beyond). It is something we will consider though.

In the short term, I think I can help address your specific email problem by adjusting our issue templates to include the name of the explainer in the title. (#383) In that way, all issues related to a particular explainer should have a consistent pre-pended "label" in your email, when sent via notifications. I hope this allows for a quick triage (without needing to read the body of the message) or email rules to be setup for the more meticulous email users among us.

[travisleithead]

(In fact, they'll end-up looking exactly like #343 which you filed.)

[tomayac]

Thanks, the short term solution works, too! Appreciated :-D Closing with actions being taken in #383.