W3C home > Mailing lists > Public > public-w3process@w3.org > September 2016

Re: Agenda: Process Document TF Telcon on Monday, 12 September, 2016

From: <chaals@yandex-team.ru>
Date: Sat, 10 Sep 2016 12:17:09 +0200
To: David Singer <singer@mac.com>, Jeff Jaffe <jeff@w3.org>
Cc: Stephen Zilles <szilles@adobe.com>, "public-w3process@w3.org" <public-w3process@w3.org>
Message-Id: <15601473502629@webcorp01g.yandex-team.ru>

10.09.2016, 05:43, "David Singer" <singer@mac.com>:
>>  On Sep 9, 2016, at 13:19 , Jeff Jaffe <jeff@w3.org> wrote:
>>  On 9/9/2016 3:04 AM, David Singer wrote:
>>>  Hi Steve, friends
>>>  I sent in some comments just before the deadline, can they be on the list of edits, please?
>>>  On TAG/AB vacated seats <https://www.w3.org/community/w3process/wiki/Advisory_Board_and_Technical_Architecture_Group_Vacated_Seats_Comment>:
>>>  Current text:
>>>  An Advisory Board or TAG participant's seat is vacated when either of the following occurs:
>>>          • the participant resigns, or
>>>          • the Chair asks the participant to resign.
>>>  I think this is not right; the chair does not have the authority to remove someone at whim, do they?
>>  Apparently, at the moment the chair does have that authority.
> All they can do is ask; apparently it’s a request.

The seat is vacated when the chair asks. So the chair *does* have authority to remove people at whim.


>>  We may want to change this in Process 2017, but I would be reluctant to make such a change so late in the game with little review. I can certainly imagine a case where Tim might want to remove someone unhelpful from the TAG.
> Yes. or indeed the AB (like, non-attendance…?)
> But then we should be clear and say who has authority to *remove*….
>>>   And even for the cases where resignation is forced because of the rules, the choice of who resigns is not made by the Chair. So, actually, I think it’s more like:
>>>  An Advisory Board or TAG participant's seat is vacated when the participant resigns, either voluntarily or in order to satisfy the _participation requirements_.
>>>  Also, this is very confused:
>>>  "When an Advisory Board or TAG participant changes affiliations, as long as Advisory Board and TAG participation constraints are respected, the individual may continue to participate until the next regularly scheduled election for that group. Otherwise, the seat is vacated."
>>>  a) AB has a hard ‘no two reps from the same member’, so it’s misleading for the AB (there is no way to respect the rule and continue to serve)
>>  The way to respect the rule is if someone changes affiliations to a new organization not currently represented on the AB.
> oh right, sorry.
>>>  b) for the TAG, they don’t have to *resign* immediately, but the seat *is* vacated immediately when they do, in fact, resign.
>>>  So, I think that this needs to be at most a note, and perhaps it should be deleted.
>>>>  On Sep 9, 2016, at 8:09 , Stephen Zilles <szilles@adobe.com> wrote:
>>>>  The call is on Monday, 12 September, 2016 at 15:00-16:00 UTC
>>>>   Webex Information is on our Mail Archives internal-w3process@w3.org (see separate e-mail to this list)
>>>>  https://lists.w3.org/Archives/Member/internal-w3process/2016Jun/0000.html (member only accessible)
>>>>   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 the draft Disposition of Comments on the August 3 Process Document.
>>>>  https://www.w3.org/community/w3process/wiki/Draft_Process_2016_Comments
>>>>  (in progress)
>>>>  2. Any other topics
>>>>       Steve Zilles
>>>>  Chair, W3C Process Document Task Force
>>>  Dave Singer
>>>  singer@mac.com
> Dave Singer
> singer@mac.com

Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Saturday, 10 September 2016 10:17:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:51:40 UTC