Re: Agenda Process Document Task Force on Webex Monday, 12 October 2015

My apologies, I will be on vacation

> On Oct 5, 2015, at 20:25 , Stephen Zilles <szilles@adobe.com> wrote:
> 
> The call is on Monday, 12 October, 2015 at  15:00-16:00 UTC
> (Note this is Columbus Day in the United States) 
> Webex Information (Note change of Telcon site)
> Dial-in: +1-617-324-0000
> Access code: 641 501 274
>  
> Meeting number: 641 501 274
> Meeting password: process
> URL to join meeting: https://mit.webex.com/mit/j.php?MTID=mbea8090287ebcf2d2cbf4b3a2b15dda9
> Host key: 628756
>  
> This meeting is now monthly, has moved to Monday and is held one hour later than before
>  
> For residents of other (typical) time zones the start times were:
> Pacific:  8:00
> Eastern US: 11:00
> Central Europe: 17:00
> Japan: 24:00 
>  
> The purpose of these meetings has been to agree on the resolution of open issues, close them where possible or assign actions to move toward closure.
>  
> Agenda:
> 1.      Review Open Action Items
> https://www.w3.org/community/w3process/track/actions/open
> 2.      Discuss Issues and Proposals for “Appeals” Issues
> Toward the end of the process of creating Process 2015, a number of issues related to "appeals" in the W3C process surfaced. At that time, there seemed to be too little time to appropriately address the issues with the care the seem to be needed. Now that Process 2015 is in Review, it is time to start on revisions for Process 2016 and the "appeals" issues seem like a good place to start. The issues:
> https://www.w3.org/community/w3process/track/issues/164
> https://www.w3.org/community/w3process/track/issues/165
> https://www.w3.org/community/w3process/track/issues/166
> https://www.w3.org/community/w3process/track/issues/167
> https://www.w3.org/community/w3process/track/issues/7
> and the proposal:
> https://lists.w3.org/Archives/Public/public-w3process/2015Jul/0030.html
> Note: there have been zero comments on the text of the proposal. Does this mean it is OK as is?

well, there are some open questions.  I also do not understand this below:  why would I appeal to *confirm* a decision that has been taken?

> 3.5 Appeal of a Chair's Decision
> 
> REPLACEMENT: "3.5 Appeal of Group Decisions"
> 
> Groups resolve issues through dialog. Individuals who disagree strongly with a decision should register with the Chair any Formal Objections<
> http://www.w3.org/2015/04/Process-20150428/#FormalObjection> (e.g., to a decision made as the result of a vote<http://www.w3.org/2015/04/Process-20150428/#Votes
> >).
> 
> When group participants believe that their concerns are not being duly considered by the group, they may ask the Director<
> http://www.w3.org/2015/04/Process-20150428/#def-Director> (for representatives of a Member organization, via their Advisory Committee representative) to confirm or deny the decision. The participants should also make their requests known to the Team Contact<http://www.w3.org/2015/04/Process-20150428/#TeamContact
> >. The Team Contact must inform the Director when a group participant has raised concerns about due process.
> 
> ADDITION: (following, "confirm or deny the decision.") This is called a Group Decision Appeal.
> [Clean-up, Issue-164<
> https://www.w3.org/community/w3process/track/issues/164
> >]
> 
> Any requests to the Director to confirm a decision must include a summary of the issue (whether technical or procedural), decision, and rationale for the objection. All counter-arguments, rationales, and decisions must be recorded.
> 
> Procedures for Advisory Committee appeals<
> http://www.w3.org/2015/04/Process-20150428/#ACAppeal
> > are described separately.
> 
> NO OTHER CHANGES ARE SUGGESTED IN THIS MESSAGE
> 
> 


David Singer
Manager, Software Standards, Apple Inc.

Received on Tuesday, 6 October 2015 21:09:56 UTC