There may be some misunderstanding here. While there are some standardization efforts that are perscriptive, many standardization efforts are targeted at "reflecting reality as closely as possible". The Unicode Locales project, for example, aims at getting translations, date formats, time formats, etc. on the basis of customary usage.<br>
<br clear="all">Mark<br>
<br><br><div class="gmail_quote">On Thu, Aug 27, 2009 at 16:48, Robert Masters <span dir="ltr"><<a href="mailto:RMasters@bunnings.com.au">RMasters@bunnings.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Thank-you Russ!<br>
<br>
That is exactly the sort of response I was hoping for - why NOT to use<br>
my suggestion.<br>
<br>
Further, your suggestion has a number of very good points to support it.<br>
<br>
Eyrie.org has been around for a long time by net standards (over 10<br>
years now), and has always been well maintained and resourced. They<br>
provide the same benefits that Sourceforge offer, with none of the<br>
problems that the site currently suffers from. It is independent of a<br>
formal body, providing a separation from bureaucratic controls, and is<br>
likewise separated from an individual's place of employment.<br>
<br>
I do not think that moving the project under the umbrella of a standards<br>
or similar organistation will be of particular benefit, as the point of<br>
the project is to reflect reality as closely as possible, not to try to<br>
enforce a standard on reality. In many ways it requires the exact<br>
opposite of a standards body.<br>
<div class="im"><br>
Regards<br>
<br>
Rob Masters<br>
Unix Systems Administrator<br>
<br>
Bunnings Group Limited<br>
126 Pilbara Street, Welshpool WA 6106<br>
Locked Bag 20, Welshpool WA 6986<br>
Phone: (08) 9365-1507<br>
E-mail : <a href="mailto:rmasters@bunnings.com.au">rmasters@bunnings.com.au</a><br>
Website: <a href="http://www.bunnings.com.au" target="_blank">www.bunnings.com.au</a><br>
<br>
<br>
</div><div class="im">-----Original Message-----<br>
From: Russ Allbery [mailto:<a href="mailto:rra@stanford.edu">rra@stanford.edu</a>]<br>
Sent: Friday, 28 August 2009 2:55 AM<br>
To: <a href="mailto:tz@lecserver.nci.nih.gov">tz@lecserver.nci.nih.gov</a><br>
</div><div><div></div><div class="h5">Subject: Re: New home for time zone stuff by 2012?<br>
<br>
"Olson, Arthur David (NIH/NCI) [E]" <<a href="mailto:olsona@dc37a.nci.nih.gov">olsona@dc37a.nci.nih.gov</a>> writes:<br>
<br>
> I'll be eligible to start drawing a pension in mid-2012. Since I'm<br>
> accustomed to slow-moving Quaker process, that makes it time to get<br>
> serious about finding a new home for time zone stuff.<br>
<br>
> There are several pieces of the puzzle (some of which haven't seen<br>
> much work of late):<br>
<br>
> Data maintenance<br>
> Data distribution<br>
> Code maintenance<br>
> Code distribution<br>
> Mailing list maintenance<br>
> Mailing list hosting<br>
> Standards work (for example, tweaking POSIX TZ environment<br>
variables so Godthab can be represented)<br>
> Code enhancement (for example, year zero work and Julian<br>
calendar<br>
> work)<br>
<br>
Since it's been explicitly mentioned as a suggestion, I guess I'll be<br>
one to stand up and say that I'd really hate to see this work move to<br>
Sourceforge. The Sourceforge site is riddled with advertising in ways<br>
that have gotten increasingly obnoxious over the years, it's slow, it's<br>
often buggy, and the mailing lists that it hosts have historically also<br>
mangled outgoing messages with even more advertising.<br>
<br>
In the name of not complaining about something without offering an<br>
alternative:<br>
<br>
Moving from hosting based on the current maintainer to hosting based on<br>
another individual may not be the best approach, and I certainly<br>
understand if people would prefer something more distributed that makes<br>
it easier to have continuity of access. However, I'm willing to host<br>
the infrastructure for continuing to distribute and discuss the timezone<br>
database personally, particularly as an alternative to seeing it move to<br>
Sourceforge.<br>
<br>
<a href="http://eyrie.org" target="_blank">eyrie.org</a> is my personal domain, independent of any employment of mine,<br>
and can offer:<br>
<br>
* Mailing list hosting (via Mailman)<br>
* Mailing list maintenance (I'm willing to review the moderation queue)<br>
* Data distribution via <a href="http://archives.eyrie.org" target="_blank">archives.eyrie.org</a> / <a href="http://ftp.eyrie.org" target="_blank">ftp.eyrie.org</a><br>
* Code distribution via <a href="http://archives.eyrie.org" target="_blank">archives.eyrie.org</a> / <a href="http://ftp.eyrie.org" target="_blank">ftp.eyrie.org</a><br>
<br>
If the number of downloads of the source and data is in excess of a few<br>
GiB a day of network traffic averaged over a month, hosting the<br>
distribution is a bit trickier, but I think it's unlikely that would be<br>
the case. That's over 10,000 downloads of the tarball a day, and I<br>
suspect nearly all users get it via distributions or other sources.<br>
<br>
If whoever is doing the maintenance would like to use a revision control<br>
system, I'm happy to host the repository with the caveat that I would<br>
like to keep the number of people with access small and restricted to<br>
people whose identities I can be reasonably assured about, since I don't<br>
have the distributed hosting facilities of a Sourceforge or the like.<br>
If the intention is to move to a more open commit model, it would<br>
probably be better to explore an option like GitHub, Savannah, or a<br>
similar project hosting provider. If the project would stay with a<br>
single committer who just needs a place to upload things, I can<br>
certainly provide that.<br>
<br>
--<br>
Russ Allbery (<a href="mailto:rra@stanford.edu">rra@stanford.edu</a>)<br>
<<a href="http://www.eyrie.org/%7Eeagle/" target="_blank">http://www.eyrie.org/~eagle/</a>><br>
<br>
<br>
</div></div><div><div></div><div class="h5">************************************************************************<br>
Bunnings Legal Disclaimer:<br>
<br>
1) This email is confidential and may contain legally privileged<br>
information. If you are not the intended recipient, you must not<br>
disclose or use the information contained in it. If you have received<br>
this email in error, please notify us immediately by return email and<br>
delete the document.<br>
<br>
2) All emails sent to and sent from Bunnings Group Limited.<br>
are scanned for content. Any material deemed to contain inappropriate<br>
subject matter will be reported to the email administrator of all<br>
parties concerned.<br>
************************************************************************<br>
<br>
</div></div></blockquote></div><br>