Hotfixes: serious suggestion
Hi all, I already wrote it to DC but got no response, so I will try to get some feedback here. At the moment DC uses the north american way of expressing dates and assigns them in this form to the names of the Hotfixes. I propose another naming scheme and will explain the reasons below. The current format is Hotfix_08_09_2000, my proposed format is Hotfix_2000-08-09. This is the ISO 8601 format (abbreviated form). Reasoning: First of all Zope is a product of a north american company but is used worldwide. Not all countries use the american form of dates, so it would be nice to have a standardized one (in my opinion this applies also to the standard date functions in Zope). The reasons for establishing ISO 8601 apply here as well: - ordering of month and day are different in Europe and America, this leads to difficulties interpreting date values - ISO dates are sortable by string functions - ISO dates are easy to parse by humans AND programs Opinions? Regards, Frank
On Tue, Aug 15, 2000 at 10:18:24AM +0200, Frank Tegtmeyer wrote:
Hi all,
The current format is Hotfix_08_09_2000, my proposed format is Hotfix_2000-08-09. This is the ISO 8601 format (abbreviated form).
totally agree. american style dates are frustrating in many ways. whereever it can be done, i believe the ISO format should be used. -d -- | Dyon Balding dyon@adroit.net |
Totally agree. In fact I think it is so logically that the question should be: Can anyone think of an argument against it ? (Else then: I am an arrogant American, I like it and f**k the rest of the world). Gijs Reulen
-----Oorspronkelijk bericht----- Van: zope-admin@zope.org [mailto:zope-admin@zope.org]Namens Dyon Balding Verzonden: dinsdag 15 augustus 2000 10:26 Aan: Frank Tegtmeyer CC: zope@zope.org Onderwerp: Re: [Zope] Hotfixes: serious suggestion
On Tue, Aug 15, 2000 at 10:18:24AM +0200, Frank Tegtmeyer wrote:
Hi all,
The current format is Hotfix_08_09_2000, my proposed format is Hotfix_2000-08-09. This is the ISO 8601 format (abbreviated form).
totally agree.
american style dates are frustrating in many ways.
whereever it can be done, i believe the ISO format should be used.
-d
-- | Dyon Balding dyon@adroit.net |
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
At 2000-08-15 10:18 +0200, "Frank Tegtmeyer" <fte@d.de.mqi.net> wrote:
The current format is Hotfix_08_09_2000, my proposed format is Hotfix_2000-08-09. This is the ISO 8601 format (abbreviated form).
Reasoning:
First of all Zope is a product of a north american company but is used worldwide. Not all countries use the american form of dates, so it would be nice to have a standardized one (in my opinion this applies also to the standard date functions in Zope).
The reasons for establishing ISO 8601 apply here as well: - ordering of month and day are different in Europe and America, this leads to difficulties interpreting date values - ISO dates are sortable by string functions - ISO dates are easy to parse by humans AND programs
Opinions?
I agree. If everyone standardised on ISO 8601 in written date and time formats, the world would be a saner place. Writing MM-DD-YY(YY) is just silly in my opinion, no matter how you like to say it out loud. It may have been acceptable in times past (like when the Internet was not nearly globally ubiquitous), but these days it's just an anachronism (as is DD-MM-YY, because it is easily mistaken for MM-DD-YY). Likewise for 12 hour time. There's only one 14:00 in the day, and that's the way I like it! ;-) David Trudgett
On Wed, 16 Aug 2000, David Trudgett wrote:
At 2000-08-15 10:18 +0200, "Frank Tegtmeyer" <fte@d.de.mqi.net> wrote:
The current format is Hotfix_08_09_2000, my proposed format is Hotfix_2000-08-09. This is the ISO 8601 format (abbreviated form).
Reasoning:
First of all Zope is a product of a north american company but is used worldwide. Not all countries use the american form of dates, so it would be nice to have a standardized one (in my opinion this applies also to the standard date functions in Zope).
The reasons for establishing ISO 8601 apply here as well: - ordering of month and day are different in Europe and America, this leads to difficulties interpreting date values - ISO dates are sortable by string functions - ISO dates are easy to parse by humans AND programs
Opinions?
I agree. If everyone standardised on ISO 8601 in written date and time formats, the world would be a saner place. Writing MM-DD-YY(YY) is just silly in my opinion, no matter how you like to say it out loud. It may have been acceptable in times past (like when the Internet was not nearly globally ubiquitous), but these days it's just an anachronism (as is DD-MM-YY, because it is easily mistaken for MM-DD-YY). Likewise for 12 hour
We had a similar discussion here at work, and simply put "Largest to smallest" makes the most sense. YYYY / MM / DD / HH : MM : SS
time. There's only one 14:00 in the day, and that's the way I like it! ;-)
So, when are you joining me in working in UTC? I mean, really. We deal with people globally on a daily basis. Why bother with all this timezone nonsens? So I get up and out of bed at 2100, get to work at a fresh and early 2300, have lunch when the sun is high at 0200, and finally make it home, on an early day, for dinner at 0900. (o8
David Trudgett
Confuses people when they ask you for the time, tho. (o8 Have a better one, Curtis Maloney
At 2000-08-16 01:54 +0000, Curtis Maloney <curtis@umd.com.au> wrote:
So, when are you joining me in working in UTC? I mean, really. We deal with people globally on a daily basis. Why bother with all this timezone nonsens? So I get up and out of bed at 2100, get to work at a fresh and early 2300,
You get up late! Myself, I'm up and at 'em at a brisk 2000 (in theory). :-) Cheers. David Trudgett
participants (5)
-
Curtis Maloney -
David Trudgett -
Dyon Balding -
Frank Tegtmeyer -
Gijs Reulen