| *** gibi_pto is now known as gibi | 06:08 | |
| *** iurygregory_ is now known as iurygregory | 06:31 | |
| *** pojadhav- is now known as pojadhav | 06:38 | |
| *** diablo_rojo is now known as Guest4491 | 11:39 | |
| gmann | yoctozepto: yeah it is not yet proposed but Venus team is interested to apply for official project. as ttx mentioned, I will reply to their private email about application requirement and then start it on openstack-discuss | 14:11 |
|---|---|---|
| gmann | yoctozepto: there are lot of project with single company maintainer now a days so that should not be an issue | 14:12 |
| gmann | tc-members: Board informal brainstorming session 'Brainstorming on OIF community resource needs ' is schedule for Aug 24th, details are here http://lists.openstack.org/pipermail/foundation/2021-August/002998.html | 14:15 |
| gmann | also there will be a quick call about background of this topic on Aug 17 (tomorrow), 2021 14:00 Greenwich Mean Time. if anyone would like to join that please let me know I will forward the initiation | 14:17 |
| fungi | "greenwich mean time" is a little confusing this time of year, when the uk is still observing british summer time. for avoidance of doubt, those times are in utc | 14:19 |
| yoctozepto | fungi: UTC=GMT, no? ;p | 14:40 |
| yoctozepto | gmann: ack, agreed; might need to update the docs to be less strict | 14:41 |
| gmann | yoctozepto: yeah, we can update doc or just a note in that doc. | 14:42 |
| fungi | yoctozepto: technically not even at the times of year when gmt is observed (they handle leap seconds differently, i believe) | 15:09 |
| *** bnemec-pto is now known as bnemec | 15:12 | |
| *** diablo_rojo__ is now known as diablo_rojo | 15:43 | |
| *** timburke__ is now known as timburke | 17:16 | |
| dansmith | yeah, leap seconds are the difference | 17:58 |
| dansmith | for scheduling meetings they are equivalent, AFAIK, and the difference is that the UK doesn't stay on GMT all year | 17:58 |
| dansmith | regardless of the amount it does or does not matter, UTC is the proper thing to use, IMHO ;) | 17:59 |
| fungi | agreed. my original point was that, for people who actually live in the gmt timezone, "gmt" may be ambiguous (as it could be interpreted as "bst" half of the year). utc is unambiguous | 18:05 |
| fungi | much like how scheduling applications always want to refer to my local timezone as "est" even though roughly half the year this region switches to "edt" and the scheduling software just assumes you know that during that half the year "est" actually means "edt" instead | 18:06 |
| dansmith | I thought that people live in GMT only for part of the year, like I don't live in PST all year, even though I hadn't moved | 18:07 |
| dansmith | but yes, assuming people that live around that line will have a same time-of-day as GMT is wrong | 18:08 |
| dansmith | I can tell you one thing, I'm glad other people are as obsessive about both time and terminology as me, that's for sure :P | 18:09 |
| fungi | you don't live in pst for the entire year, but popular scheduling software would actually list 14:00 pdt as 14:00 pst and assume everyone (who may not even be in that side of the globe) just know when it means pdt and when it doesn't | 18:10 |
| dansmith | um | 18:10 |
| fungi | which is really my main peeve | 18:10 |
| dansmith | are you sure? | 18:10 |
| dansmith | if I schedule something in PST it's going to show the time for you in EST, unless I schedule it for far enough away that it's EDT for you and then it's going to show me time in EDT, no? | 18:11 |
| fungi | i often get meeting "invites" in the summer from people scheduling meetings in "cst" even though they mean "cdt" and the invites encode the meeting time as "14:00 cst" but the meeting is actually at "14:00 cdt" | 18:11 |
| dansmith | i.e. it chooses the time and zone to show based on the time of the event, not the current time | 18:11 |
| dansmith | are they really choosing cst or are they choosing/calculating a local time for you? | 18:12 |
| dansmith | can we sidestep this conversation by agreeing that DST is stupid? :) | 18:13 |
| fungi | the invites auto-sent via e-mail say thinks like "14:00 cst" regardless of what time of year it is, and expect me to know that during the warm months that's actually "14:00 cdt" | 18:13 |
| dansmith | ah, okay, they're just not rendering the correct timezone, I see | 18:14 |
| fungi | so i inevitably end up asking the meeting organizers to clarify | 18:14 |
| dansmith | well, that's (a) broken and (b) made to be too much work because DST is stupid :) | 18:14 |
| fungi | "you sent me an invite for a meeting at 14:00 cst which would be utc-0600 but i know cdt (utc-500) is currently observed..." | 18:15 |
| dansmith | by sheep that let the government shift their time twice a year! rise up! :P | 18:16 |
| fungi | maybe soon you'll be on perpetual pdt (which they should have just called mst at that point) | 18:16 |
| dansmith | no, we should call it PT | 18:17 |
| fungi | if they were pushing to make it pst year-round i would agree, but for some reason the suggestion has been to make it pdt all year | 18:17 |
| dansmith | well, because most people want the PDT hours which are fine and arbitrary | 18:18 |
| dansmith | I'm saying make it "pacific time" and not "standard" or "daylight" .. "this is the time on the pacific coast, no wishy-washy potential to reinstate a switch in the future" | 18:19 |
| fungi | (which, as i understand, is part of why they can't "just do it," it's already possible to declare you won't observe an alternative "daylight time" but congress has to get involved if you want to do something else like change your standard time) | 18:19 |
| dansmith | yeah | 18:19 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!