Re: PLEASE RESPOND Final cleanup, I need to make sure everyone is OK

I agree to all these changes.  

Léonie, you sound more comfortable with #2 after the recent GitHub discussion, correct?  I’m not sure if this needs to be in the Process, but the discussion seemed to conclude that the team procedure should be for CR announcements to include pointers to how to file issues if one believes that the transition to PR should be accelerated (e.g.,by  dropping items that don’t have consensus until the next iteration) or that the transition should be blocked until some critical issue is addressed or re-opened.  


> On Sep 27, 2017, at 9:31 AM, David Singer <singer@apple.com> wrote:
> 
> Some responses to this would be appreciated.
> 
> We intend to ‘freeze’ top-of-tree during AC review, so the document at github.io remains unchanged. Issues and pull requests that land as part of AC review will be held (or a branch will be made) so the AC has a consistent document to comment on.
> 
> 1) Leonie proposes removing the somewhat-redundant word ‘public’ before ‘working draft’ EXCEPT in the phrase First Public Working Draft, since all WDs are by definition public. See <https://github.com/w3c/w3process/pull/104>, responding to <https://github.com/w3c/w3process/issues/84>. OK?
> 
> 2) <https://github.com/w3c/w3process/pull/105> and <https://github.com/w3c/w3process/pull/106> make the change to the process to restore the formal ballot at Proposed rec instead of at CR. Implements the decision on issue #34. Do we need the process to say that nonetheless the AC will be given early comment opportunity (around CR)?
> 
> 3) There are a few other editorial issues and pull requests, see <https://github.com/w3c/w3process/labels/Editorial%20improvements>. Do you mind if we land these ASAP before AC review starts? 
> 
> 
> David Singer
> Manager, Software Standards, Apple Inc.
> 
>

Received on Wednesday, 27 September 2017 17:42:38 UTC