| Summary: | Creation of a jakartaee-spec-leads@eclipse.org list | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Blevins <david.blevins> |
| Component: | MailingLists | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
David Blevins
It's queued for creation, which happens in about 12h. At that point it will appear on https://www.eclipse.org/mail/ Please reopen if that doesn't occur. Let's change the name of the list to this: jakartaee-project-leadership@eclipse.org We'll populate the list with the Jakarta EE project leadership, which includes the Project Leads for each specification project and the PMC Leads and Members. I'll send you a list of names. I've set the list to be created as jakartaee-project-leadership@eclipse.org Just going to call out the opportunity for ambiguity again. We have other "leadership" lists: Steering Committee, Specification Committee, PMC. What we're lacking is a way to pin tasks on spec leads. If the list doesn't target them specifically and starts getting general "leadership" messages, we're likely back to square one. We need something that says "If you're a spec lead and do not read and answer emails on this list, you're not doing your job and therefore can be removed as a spec lead." We need to at least put the word "spec" back in somewhere. There is no notion of "spec lead" in the Eclipse Foundation Specification Process. We do have a well defined notion of a leadership chain which includes the Project Leads, PMC, and EMO. How about jakartaee-spec-project-leads@eclipse.org? jakartaee-spec-project-leads@eclipse.org is specific and targeted. +1 The list is set up, and pre-populated according to a list supplied by Wayne. |