[HN Gopher] I'm running for the OSI board maybe
___________________________________________________________________
I'm running for the OSI board maybe
Author : elboulangero
Score : 35 points
Date : 2025-02-20 23:31 UTC (1 days ago)
(HTM) web link (blog.luke.wf)
(TXT) w3m dump (blog.luke.wf)
| rafram wrote:
| This sucks, but they do list other times in UTC (well, GMT,
| actually), so it's not unexpected IMO.
| seabass-labrax wrote:
| GMT is a bizarre choice for an international organization based
| in California, too. GMT isn't used in the summer, and the dates
| when the time switches from GMT to BST and from PST to PDT
| aren't the same! That alone has caused confusion in every
| international organization I've been involved with. At least
| with UTC one can reasonably expect to use it throughout the
| entire year.
| sevg wrote:
| It's an awkward situation for sure and the timezone could have
| been clearer.
|
| But I also feel like if there's no timezone for a deadline then
| you should assume the worst case (which here would be UTC) and
| make sure you submit before?
|
| The author left it so late that in 95% of the world it was no
| longer the 17th Feb.
| orra wrote:
| Ah but UTC isn't the worst case: it's UTC+14.
|
| I agree with the author: the timezone of the organisation is
| what I'd expect.
| sevg wrote:
| > Ah but UTC isn't the worst case: it's UTC+14.
|
| The worst _reasonable_ case is UTC. Nobody is thinking
| UTC+14.
|
| > I agree with the author: the timezone of the organisation
| is what I'd expect.
|
| If the job was a local office job, I'd expect a local time
| zone. But the board of directors isn't restricted to
| California or even the USA.
| maxboone wrote:
| AOE times are pretty common in academic and CS circles, it
| is the standard for IEEE 802:
| https://www.ieee802.org/16/aoe.html
| sevg wrote:
| The OSI post that the author links to specifies the
| voting deadline in GMT (effectively UTC) in the sentence
| immediately preceding the timeline diagram.
|
| So it can be reasonably inferred that they're generally
| using GMT/UTC in the rest of their timeline, rather than
| AOE, UTC+14 or anything else out of the ordinary.
| worik wrote:
| No excuses for this.
|
| They should accept they made a mistake and accept the nomination.
|
| You cannot assume a timezone. Especially as a computer
| programmer, we should know that. It was Feb 17 somewhere in the
| world until 12:00 Feb 18 UTC
| seabass-labrax wrote:
| In the quoted email, it is stated that to "ensure a fair process,
| [the OSI] must adhere to the deadline for all candidates". I'm
| not sure what the OSI or their stakeholders have to gain by
| rejecting nominations for the sake of the few hours that result
| from timezone differences. The purpose of a deadline is to
| provide enough time to vet submissions to remove candidates who
| are ineligible or insincere, clear up any confusion stemming from
| mistakes in the submission and so on. It's not a race!
| EarlKing wrote:
| Even if this is entirely innocent and the result of someone
| trying to do the right thing... not a good look. They should
| honestly accept his candidacy and then revise the submission
| guidelines to be more specific in the future. To do otherwise
| makes it look like they're trying to exclude candidates to ensure
| a pre-selected candidate runs unopposed.
___________________________________________________________________
(page generated 2025-02-22 23:02 UTC)