[tz] Replacing the TZ Coordinator

[Robert Masters]

I do not believe we have got to that stage. That said, I also believe we should hold off on any major changes until we have a clear consensus. 

I think an appropriate course of action would be to revert to 2021a, apply the changes just announced, and then everyone take a week off to think about things and to calm down.

After we've all taken a week's break let's all put together the various proposals in a single list, and work out which is the right one (if any) to go forward with.

-Rob


Robert Masters


On 9/21/21 17:42, Stephen Colebourne via tz wrote:
> The TZDB project is guided by RFC 6557. Section 4 allows the list to 
> seek an alternate TZ coordinator where "The TZ Coordinator is not 
> performing the function in accordance with community wishes".
> https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc6557.htm
> l*section-4__;Iw!!O7oHvdjpjIQ!kM6ZNHhCWnmLkZH2xxPctTn67pvsqSctoUcYUKVD
> kNkF_p6RkOKH45-3G2URdtxH-A$
>
> The RFC instructs as follows:
>
>     Members of the community should raise the
>     issue on the TZ mailing list and attempt to reach consensus on a new
>     candidate to fulfill the role of TZ Coordinator.  If rough consensus
>     cannot be reached easily, the Area Directors of the IETF Applications
>     Area should attempt to guide the members of the community to rough
>     consensus.  The candidate that is agreed upon by the community
>     through rough consensus shall be presented to the IESG for
>     confirmation.  If rough consensus cannot be reached, even with
>     guidance from the Applications Area Directors, the IESG shall use
>     whatever means it has at its disposal to choose a candidate who in
>     its best judgment will be able to fulfill the role of TZ Coordinator.
>
> Is there consensus on the list that a change is required?
> Is there a candidate willing to take on the role of TZ Coordinator?
>
> Stephen

**********************************************************************
This email is confidential and may contain legally privileged information. 
If you are not the intended recipient, you must not disclose or use the information contained in it. 
If you have received this email in error, please notify us immediately by return email and delete the document