- From: Michael Champion <Michael.Champion@microsoft.com>
- Date: Tue, 21 May 2019 01:36:40 +0000
- To: Jeff Jaffe <jeff@w3.org>, Florian Rivoal <florian@rivoal.net>, W3C Process CG <public-w3process@w3.org>
- CC: "www-tag@w3.org" <www-tag@w3.org>
So, the CG would work on registries and evergreen for Process 2020, and the AB would do preliminary work on the Role of the Director for some future process? That sounds reasonable. I can wait for August to discuss in the CG ... although since it's public I expect the GitHub issues to get discussion.
And yes, I means "defer" to mean we don't need to finalize until Process 2021, not that all discussion should be deferred.
-----Original Message-----
From: "jeff@w3.org" <jeff@w3.org>
Date: Monday, May 20, 2019 at 3:47 PM
To: Michael Champion <Michael.Champion@microsoft.com>, Florian Rivoal <florian@rivoal.net>, W3C Process CG <public-w3process@w3.org>
Cc: "www-tag@w3.org" <www-tag@w3.org>
Subject: Re: Director-free branch
On 5/20/2019 4:45 PM, Michael Champion wrote:
> A few thoughts:
>
> Florian, this is a great start, thanks! But what's the priority for the CG to deliberate? It might be:
> 1. Get a Repository mechanism in the Process
> 2. Get an Evergreen option of some sort in the Process
> 3. Get a Director-free model into the Process
>
> Do we try to do all this for Process 2020? Or defer 3 until Process 2021 (when presumably there is a Board of Directors to give some Director roles to).
Here is my input on this question.
At the AB F2F in April, the AB just barely started to address some of
the open questions about how this works. There are still many open
questions. As a result, the AB has set aside 7.5 hours to grind through
these issues in their F2F meeting in June.
Since the AB has already started to crunch through these issues, I think
we should allow the AB to complete their first pass before this comes to
the Process CG.
I don't believe that the level of issues that need to be addressed are
sufficiently straightforward that we can get this into Process 2020.
Remember that the target is to get Process 2020 into the hands of the AC
by August.
When Mike says "defer", I hope that he does not mean to defer the work.
I believe that can (and should) look at this in parallel with the other
work going on. I just don't think we can make it for Process 2020.
>
> That said, my personal interest is 3 > 2 > 1. I'd be OK with skipping Process 2020 and using the saved effort to ensure that Process 2021 accomplishes them all. Unless of course we could quickly agree on solutions for 1 and 2, but I'm not optimistic.
>
> -----Original Message-----
> From: Florian Rivoal <florian@rivoal.net>
> Date: Monday, May 20, 2019 at 7:23 AM
> To: W3C Process CG <public-w3process@w3.org>
> Cc: "www-tag@w3.org" <www-tag@w3.org>
> Subject: Director-free branch
> Resent-From: <public-w3process@w3.org>
> Resent-Date: Monday, May 20, 2019 at 7:22 AM
>
> Hi all,
>
> It took me longer that I thought after the last AC meeting and AB F2F, but I have now set up a branch of the process called director-free to explore what the Process would like without a director.
>
> This attempts to reflect my understanding of the consensus of the AB on areas where there was one, using my own sense of how things might work to fill in the blanks.
>
> director-free process: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fw3process%2Fdirector-free%2F&data=02%7C01%7CMichael.Champion%40microsoft.com%7Cde097161aa114e85fcab08d6dd75186b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636939892330465947&sdata=p%2F%2BYcHR4Xk9UJrBp8MLElb%2FU%2BXtMoPHLXqHhwKZLzOo%3D&reserved=0
> diff: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fservices.w3.org%2Fhtmldiff%3Fdoc1%3Dhttps%253A%252F%252Fw3c.github.io%252Fw3process%252F%26doc2%3Dhttps%253A%252F%252Fw3c.github.io%252Fw3process%252Fdirector-free%252F&data=02%7C01%7CMichael.Champion%40microsoft.com%7Cde097161aa114e85fcab08d6dd75186b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636939892330465947&sdata=WmskmHs4GW953evk9qeAf1yi%2B3DnSDbotNZyPmkZT6M%3D&reserved=0
>
> This is definitely not final, but it should be detailed enough that we can now iterate using individual issues. I've already done so for the issues noted inline in the document: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fw3process%2Flabels%2Fdirector-free&data=02%7C01%7CMichael.Champion%40microsoft.com%7Cde097161aa114e85fcab08d6dd75186b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636939892330465947&sdata=GmrT0ZEoStYoBUpbSrYwppd%2BfaW9jnlWRVmS5uVvJpw%3D&reserved=0 Please discusse there or open additional issues in https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fw3process%2Fissues%2F&data=02%7C01%7CMichael.Champion%40microsoft.com%7Cde097161aa114e85fcab08d6dd75186b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636939892330465947&sdata=XKRcyVBk7lFp4oyMn4uisZx140mkxTTzZARH6ZrPpO0%3D&reserved=0 and use "[director-free]" in the title as well as "director-free" as a label if you have the access-rights to put labels.
>
> In particular, note the straw-man proposal for a mechanism to replace the Director's appointments to the TAG, loosely based on the concept evoked during the TAG-AB joint-session in Quebec. Feedback from the TAG is very welcome on that topic. Most of it is in https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fw3process%2Fdirector-free%2F%23TAG-appointments&data=02%7C01%7CMichael.Champion%40microsoft.com%7Cde097161aa114e85fcab08d6dd75186b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636939892330465947&sdata=vlE4YXrYH2R%2FZSRE1fFOPrVDE%2FG1Ad1Zf4etBuk3%2FmA%3D&reserved=0, although there are some smaller changes to neighboring sections to integrate it.
>
> —Florian
>
>
Received on Tuesday, 21 May 2019 01:37:09 UTC