Fixed
Status Update
Comments
mi...@google.com <mi...@google.com> #2
[Empty comment from Monorail migration]
os...@gmx.de <os...@gmx.de> #3
today i was pondering bothering the ESC with an issue, and came to a halt:
- it's entirely unclear how to contact the ESC. the members are named, but no contact info is provided. i'd have expected a dedicated mailing list, but using the issue tracker also for initial contact would presumably work as well.
- it's not even clear under which circumstances (not) to contact. the fundamental scope of the ESC is clear, but the "escalation process" is undefined.
- it's entirely unclear how to contact the ESC. the members are named, but no contact info is provided. i'd have expected a dedicated mailing list, but using the issue tracker also for initial contact would presumably work as well.
- it's not even clear under which circumstances (not) to contact. the fundamental scope of the ESC is clear, but the "escalation process" is undefined.
da...@gmail.com <da...@gmail.com> #4
We discussed this in yesterday's ESC meeting. In short, we've agreed to follow what the Community Managers are doing. We will create an ESC component in the issue tracker, create a mailing list, and update the documentation to clarify.
da...@gmail.com <da...@gmail.com> #5
[Empty comment from Monorail migration]
da...@gmail.com <da...@gmail.com> #6
Created the ESC component.
[Monorail components: ESC]
[Monorail components: ESC]
ma...@gmail.com <ma...@gmail.com> #7
[Empty comment from Monorail migration]
da...@gmail.com <da...@gmail.com> #8
da...@gmail.com <da...@gmail.com> #9
Tracking creation of a mailing list for ESC in https://crbug.com/gerrit/11548 .
da...@gmail.com <da...@gmail.com> #10
[Empty comment from Monorail migration]
ek...@google.com <ek...@google.com> #11
[Monorail components: SteeringCommittee]
ek...@google.com <ek...@google.com> #12
[Monorail components: -ESC]
ek...@google.com <ek...@google.com> #13
[Empty comment from Monorail migration]
is...@google.com <is...@google.com> #14
Edits were made to reflect the following in Monorail: auto-CCs.
Description
However it's difficult to know what the ESC is working on, or what they plan to work on. E.g. the ESC is expected to make a roadmap [2] but for non-ESC members it's unknown if work on this has started, or is planned anytime soon (see
To address these issues I suggest to add an 'ESC' component to the issue tracker that
* is used to track work that is being done by the ESC
* monitored by the ESC in case someone wants to bring an issue to the attention of the ESC
[1]
[2]