Re: DRAFT-R1 Agenda Process Call Wednesday November 1st, 9am Pacific

Would someone please send me the call coord8nates?  I can’t get to the web page.  Thanks.

Best regards,

Virginia Fournier
Senior Standards Counsel
 Apple Inc.
☏ 669-227-9595
✉︎ vmf@apple.com






On Oct 30, 2017, at 4:15 PM, David Singer <singer@apple.com> wrote:

Please comment on the issues, as needed, and on this agenda, BEFORE the call, so we can complete the agenda in time. We have a HUGE agenda. Please come prepared to be efficient!

Thanks




Full Webex Information is on our Mail Archives <https://lists.w3.org/Archives/Member/internal-w3process/2017Oct/0000.html>  (member only accessible, email me if this is a problem)

IRC is #w3process


1) Assign scribe, etc.

2) Issues raised since we sent the document out for review.

 2.1) Issues that seem to be needing addressing, or can be addressed, in 2017, and are not editorial.

 <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue%20is%3Aopen%20label%3AAC-review%20-label%3A%22Editorial%20Improvements%22%20>

The first substantive issue here is WG voting. I think we should REVERT the PR #81 <https://github.com/w3c/w3process/pull/81> and simply add what we intended to 3.4, the defaults so that charters don’t need voting rules at all:
 #109 Voting notice before it starts or before it ends? <https://github.com/w3c/w3process/issues/109>
    — see #24 <https://github.com/w3c/w3process/issues/24>, which I re-opened as we are getting pushback. 
        We simply need defaults for things that the charter might override (but need not).
 #121 Revert section 3.4 default in WG voting rules to Process 2017 <https://github.com/w3c/w3process/issues/121>
    — see #24 for the original issue <https://github.com/w3c/w3process/issues/24>. We were merely seeking to (a) make sure that the charter requirements and the voting rules were in accord and (b) try to make it possible to write a charter without talking about voting, because there were sensible defaults in the process.  Our edit went beyond that. We should revert and simply add these defaults.

The second is on whether we need to codify Contribution IPR grants coming from anyone not under an obligation as a result of WG membership:
#67 Clarify the handling contributions from guests, non-w3c members, and non-WG members <https://github.com/w3c/w3process/issues/67>

 I think we should DEFER these:

#83 Written notification <https://github.com/w3c/w3process/issues/83> 
    — minor, and no suggested fix, and not related to new text in 2017. Defer?
#103 Should the process allow REC->WD transition directly? <https://github.com/w3c/w3process/issues/103> 
    — minor, no suggested text, defer?
#107 Audit of Members / Quorum? <https://github.com/w3c/w3process/issues/107>
    — major (‘zombie ac reps’)  but not related to the 2017 changes; defer?

DB thinks we should REVERT this:

#97 consider keeping 'other than to remove features explicitly identified as "at risk”’? <https://github.com/w3c/w3process/issues/97>
    — revert?

This one is trivial; some like completeness:
 #112 appeals outcome that sustains the decision
    — trivial; we need to say (for some people) what happens when an appeal is not successful

 Possibly No Change:
 #123 Who at W3C can request publication of an Amended Recommendation? <https://github.com/w3c/w3process/issues/123>
    — some misunderstanding here; we might need clarification, but this might be a ‘no change'


 2.2) Editorial Issues that seem to be needing addressing, or can be addressed, in 2017
    <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue%20is%3Aopen%20label%3AAC-review%20label%3A%22Editorial%20Improvements%22>

 #82 Duplicated links
 #108 Team Contact or Staff Contact?
    — new text introduced “Staff Contact” for the AB and TAG, should be “Team Contact"
 #110 Amended Recs currently appear to BE Candidate Recs <https://github.com/w3c/w3process/issues/110>
 #111 6.1.2 "editorial or other minor corrections"
 #113 Capitalization of 'Host' in section 9
 #114 "Reference Draft" and "Other Charter”
    — this is related to the text introduced last year

3) Other open issues: <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue%20is%3Aopen%20-label%3AAC-review>
 There are 25 of these. Should any be addressed as part of Process2018?

4) Slides for the AC meeting (as time permits).

5) Next meeting. December 13th, review after the AC meeting, and get started on the Process2019?

6) Any other business.



Thanks

David Singer
Manager, Software Standards, Apple Inc.

Received on Wednesday, 1 November 2017 16:05:03 UTC