[tz] Preparing to fork tzdb
Shawn.Steele at microsoft.com
Fri Sep 24 20:28:15 UTC 2021
(I subscribe to digests - though as many of those have been sent recently, it doesn't feel like a digest 😁)
It's one thing to have a zone that has "always" behaved this way, and another to have folks feel like it was "taken away" from them. The first may have begrudging acceptance, but the second is harder to come to terms with.
I confess the identifiers always bug me a bit when I don't actually live in the place being identified, but that's closest to my time zone.
Date: Fri, 24 Sep 2021 00:43:26 -0700
From: Paul Eggert <eggert at cs.ucla.edu>
To: Stephen Colebourne <scolebourne at joda.org>, Time Zone Mailing List
<tz at iana.org>
Subject: Re: [tz] Preparing to fork tzdb
Message-ID: <3c8e2714-752c-83f3-fafd-61fd796c7353 at cs.ucla.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
On 9/23/21 6:07 AM, Stephen Colebourne via tz wrote:
> the solution adopted (creating Links
> where previously there were Zones) has created a *different* equity,
> diversity or inclusion issue.
That's not a new issue. We've dealt with it many times, by dealing with questions like "How come there's no Asia/Beijing Zone?" When the issue comes up we point to the guidelines, which are based on timekeeping rather than traditional political issues.
Although we can't expect the guidelines to be familiar in advance to everyone who asks such questions, explaining the guidelines hasn't been much of a problem in practice.
More information about the tz