- From: Michael Champion <Michael.Champion@microsoft.com>
- Date: Mon, 20 May 2019 19:26:56 +0000
- To: Jeff Jaffe <jeff@w3.org>, David Singer <singer@apple.com>, W3C Process CG <public-w3process@w3.org>
- CC: Wendy Seltzer <wseltzer@w3.org>, Philippe Le Hegaret <plh@w3.org>
I did open and flag some finer-grained issues after seeing David's email. I'm wondering how best to proceed given PLH's list of use cases for various flavors of Evergreen: [[ ARIA: ARIA Mappings SVG: Beyond SVG 2 WebAppSec: CSP Web Performance: performance timeline, … Web Platform: WebIDL Dataset Exchange: Beyond DCat 1.1 Timed Text: TTML Profile registry Distributed Tracing: Trace Contact Protocol Registry WebRTC: registries WebApps: Manifest, etc. ]]\\ Several are registries. We've been treating Registries as a subtype of ER, but discussion in https://github.com/w3c/w3process/issues/79 makes me wonder if just creating a "registry" type that has more authority than a Note but not the overhead of Recommendation or even ER is good enough to solve the problem. After all, do Registries really need implementer support, patent commitments, horizontal review, etc.? If they do, I agree that making them type of ER makes sense but if not, do we really need to solve the numerous ER issues to create Registries as first-class working group products? Also, I'd be less skeptical about some of these use cases if the chairs/editors responsible for them where here discussing how to satisfy them. For example, I'm not at all sure the WebIDL community is really interested in working on an Evergreen Recommendation and hear different 3rd hand reports from different people who have talked to them. > Similarly, perhaps Wendy can give an update on PSIG discussions on Evergreen PP. Very strongly agree -----Original Message----- From: "jeff@w3.org" <jeff@w3.org> Date: Saturday, May 18, 2019 at 7:08 PM To: David Singer <singer@apple.com>, W3C Process CG <public-w3process@w3.org> Cc: Wendy Seltzer <wseltzer@w3.org>, Philippe Le Hegaret <plh@w3.org> Subject: Re: Next process call is Next Wednesday 22nd, and only one issue is Agenda+'d (and that is old) Resent-From: <public-w3process@w3.org> Resent-Date: Saturday, May 18, 2019 at 7:08 PM #271, #272, and #273 all seem ripe for discussion. Perhaps Mike added them after your email was sent. I'm trying to recall. I believe that we said we were going to create a branch of the process document with Evergreen. Has that happened yet? It would be good to get that done before the meeting on the 22nd. Last week, on issue #79, PLH posted an impressive list of specs that have some interest in Evergreen. I took that as a call to action; there is a real need that we should get addressed in Process 2020. Accordingly, I think we should have some discussion about what actions we will take to get CG consensus on these process mods. Similarly, perhaps Wendy can give an update on PSIG discussions on Evergreen PP. Jeff On 5/17/2019 5:46 PM, David Singer wrote: > Hi guys > > next call is on Wednesday 22nd. The primary focus will be on ES and Registries, I think. We have only one issue (ES) tagged Agenda+ (I’ll soon add Registries). > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fw3process%2Flabels%2FAgenda%252B&data=02%7C01%7Cmichael.champion%40microsoft.com%7C56f40c32553941ce407908d6dbfedc7f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636938285002281359&sdata=T31Rj0THSEXHSmRYfvNtmzpioFOlZKlU1lBDpSeDcUY%3D&reserved=0> > > > You might scan the issues and see whether you can move the conversations along offline, and tag Agenda+ on issues that would benefit from a declaration of consensus, or from verbal discussion. > > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fw3process%2Fissues&data=02%7C01%7Cmichael.champion%40microsoft.com%7C56f40c32553941ce407908d6dbfedc7f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636938285002281359&sdata=T8%2By2wendL71RrJjcLxWA3BSXCeJGbogmjaAtvyPLLs%3D&reserved=0> > > > I’ll do an initial agenda on Monday… > > David Singer > Manager, Software Standards, Apple Inc. > >
Received on Monday, 20 May 2019 19:27:23 UTC