The Unicode consortium projects have very different processes and release schedules. - The Unicode Standard process is the heaviest; it uses larger quarterly physical meetings, plus smaller monthly one-day meetings, and has releases about 1 to 1.5 years. - Script updates use email communication only, and may be updated in weeks. - CLDR uses weekly phone meetings and email; a major release of CLDR can take 9-12 months, but a dot-dot update of CLDR only needs days. - A change in the UDHR can be done overnight. So it all depends on the process the TZ group wants to use. (BTW, in Google we are well aware of the need for speed; getting our products updated around the globe with new TZ data with notice of only a week or two is extremely painful!) Mark On Thu, Aug 27, 2009 at 11:22, Larry Gilbert <lgilbert@digium.com> wrote:
I was about to suggest this, but am concerned about whether having the TZ project under the UC umbrella would really allow it to "continue basically as it does now." Other projects under UC such as CLDR have lengthy input/review/release cycles, but the TZ data has to be able to be turned around quickly due to the unpredictability of time changes in some countries (Egypt is still fresh in my mind).
-- Larry Gilbert <lgilbert@digium.com> Digium | Switchvox
On Thu, 2009-08-27 at 10:48 -0700, Mark Davis ⌛ wrote:
The officers of the Unicode Consortium (http://unicode.org) have discussed this issue, and are interested in exploring hosting the TZ efforts. Aside from the Unicode projects, we currently also support other independent efforts (http://www.unicode.org/iso15924/, http://www.unicode.org/udhr/). Hosting the TZ project would provide for mailing list hosting, code distribution, source code repository (SVN) if desired, etc., web pages, etc. -- presuming that the functioning of the TZ group would continue basically as it does now.