W3C home > Mailing lists > Public > public-w3process@w3.org > May 2019

Re: Increasing the number of TAG

From: Chris Wilson <cwilso@google.com>
Date: Mon, 13 May 2019 09:25:20 -0700
Message-ID: <CAJK2wqX44DitYuMPF=NbxaWThe60uXQe_5_w9f9wdrC2ZjC2OA@mail.gmail.com>
To: Naomi Yoshizawa <naomi@w3.org>
Cc: Daniel Appelquist <appelquist@gmail.com>, "lw@tetralogical.com" <lw@tetralogical.com>, Michael Champion <Michael.Champion@microsoft.com>, David Singer <singer@mac.com>, "public-w3process@w3.org" <public-w3process@w3.org>
Incidentally, when we increased the membership of the AB last year (
https://github.com/w3c/w3process/issues/190), we discussed increasing the
TAG as well.  I followed up with several TAG members and got the same
response - they were not convinced that the TAG would be able to increase
its workload by adding members, and it would complexify logistics.  I will
continue to support their take on that, whatever it is.  :)

*From: *Naomi Yoshizawa <naomi@w3.org>
*Date: *Mon, May 13, 2019 at 1:42 AM
*To: *Daniel Appelquist
*Cc: *lw@tetralogical.com, Michael Champion, David Singer,
public-w3process@w3.org

Hello Dan,
>
> Thanks so much for taking it as homework at TAG. Yes, TAG knows the best.
> I'd appreciate being shared with any proposals.
>
>
> On Sun, May 12, 2019 at 2:03 AM Daniel Appelquist <appelquist@gmail.com>
> wrote:
>
>> Hi - happy to provide some more detail. It is true that we are currently
>> not moving quickly enough and therefore we are falling behind in meeting
>> the needs of our stakeholders.  I might support adding an additional member
>> to the TAG but I wouldn't go beyond that. I also think it's a fallacy to
>> think that adding another person necessarily makes the TAG operate faster.
>
>
> +1
> That happens everywhere, not only at the TAG.
>
> Thanks to David, Michael and Leonie for caring on this as well.
>
> Best,
> Naomi
>
>
>> I think there was a book written about this? We are about to have our f2f
>> in a week's time and we are going to dedicate some time there to having a
>> retrospective of how the TAG currently works and how we can operate faster
>> and more efficiently. Can we take it as homework to come back to you with
>> any proposals about the makeup of the TAG that might come out of this
>> session?
>>
>> Dan
>>
>> On Saturday, May 11, 2019, Léonie Watson <lw@tetralogical.com> wrote:
>>
>>>
>>> On 10/05/2019 19:35, Michael Champion wrote:
>>>
>>>> I'd be happy to raise the issue in GitHub, but I'd be interested in
>>>> learning more from Naomi about the information she has that the TAG is
>>>> overloaded and whether the TAG members / chairs support the idea of getting
>>>> more people to help.  We did increase the size of the TAG by one person
>>>> recently, and it would be good to know if that helped somewhat, and how
>>>> many more people it would take to really handle the workload.
>>>>
>>>
>>> It would also help to understand more about what the workload is.
>>>
>>> Léonie.
>>>
>>>
>>>> -----Original Message-----
>>>> From: David Singer <singer@mac.com>
>>>> Date: Friday, May 10, 2019 at 8:52 AM
>>>> To: Naomi Yoshizawa <naomi@w3.org>
>>>> Cc: "public-w3process@w3.org" <public-w3process@w3.org>
>>>> Subject: Re: Increasing the number of TAG
>>>> Resent-From: <public-w3process@w3.org>
>>>> Resent-Date: Friday, May 10, 2019 at 8:52 AM
>>>>
>>>>      Sure
>>>>           can you raise an issue in the Process CG repo, and probably
>>>> then one of us should alert the AB?
>>>>           > On May 10, 2019, at 6:47 , Naomi Yoshizawa <naomi@w3.org>
>>>> wrote:
>>>>      >
>>>>      > Hello David and Revising W3C Process Community Group,
>>>>      >
>>>>      > Could the group discuss to boost the number of TAG, please?
>>>> There is a voice to increase the headcount of TAG since every TAG member
>>>> barely has enough time to review everything that comes in.
>>>>      >
>>>>      > Thanks,
>>>>      > Naomi
>>>>           David Singer
>>>>           singer@mac.com
>>>>
>>>>
>>>
>>> --
>>> @TetraLogical TetraLogical.com
>>>
>>>
Received on Monday, 13 May 2019 16:25:58 UTC

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