| *** pojadhav is now known as pojadhav|ruck | 02:36 | |
| *** lbragstad8 is now known as lbragstad | 04:48 | |
| *** pojadhav|ruck is now known as pojadhav|rover | 05:26 | |
| *** tobias-urdin5 is now known as tobias-urdin | 06:03 | |
| *** gibi_pto is now known as gibi | 07:27 | |
| *** pojadhav is now known as pojadhav|rover | 13:30 | |
| *** dasm|off is now known as dasm | 13:31 | |
| dansmith | it's interesting that there have been no replies to the announcement | 13:38 |
|---|---|---|
| fungi | to the ptg announcement? | 14:09 |
| gmann | yeah | 14:10 |
| dansmith | yeah | 14:15 |
| dansmith | I expected a lot of angry villagers with pitchforks | 14:15 |
| fungi | well, it was announced to lots of different places, but yeah it seems like the event coordinators so far haven't gotten much negative feedback on the sudden change in direction | 14:16 |
| dansmith | I've heard plenty of non-public grumbling about the "sudden" part, but less so about the "change" part | 14:19 |
| gmann | may be discussion happening on individual emails foundation sent to registered members? | 14:55 |
| gmann | hopefully, those emails or announcement are read/noticed. | 14:55 |
| dansmith | is there an agenda for this TC/board meeting on Weds? | 15:45 |
| dansmith | it's a bit short notice, so I assume it's something important enough to justify the sudden-ness | 15:46 |
| clarkb | dansmith: it is this meeting aiui https://lists.openstack.org/pipermail/openstack-discuss/2022-June/029352.html been in planning for about a month and a half | 15:51 |
| dansmith | clarkb: okay, it's the first I'm hearing of it and given the audience, I would have expected a doodle | 15:52 |
| gmann | dansmith: in this call we will continue the discussion on keys points we presented in board meeting in berlin. but we can add more topics in the etherpad https://etherpad.opendev.org/p/2022-08-board-openstack-sync | 15:54 |
| dansmith | gmann: okay, I remember there was another one, just... two days notice with no time poll is kinda :/ | 15:55 |
| clarkb | there was a time poll https://framadate.org/atdFRM8YeUtauSgC ? | 15:56 |
| dansmith | hah, right, okay, I forgot about that, fair enough | 15:57 |
| fungi | dansmith: there was a time poll. you even filled it out: https://framadate.org/atdFRM8YeUtauSgC | 15:57 |
| dansmith | lots of time between "is this free on your calendar" and the reserving of that spot | 15:57 |
| dansmith | so the poll is pretty much no longer accurate | 15:57 |
| fungi | i gave everyone two weeks to fill it out, then picked the top three choices and provided those to the board chair who then worked with the board members to select their preference, after which i forwarded the meeting invite the board chair sent me | 15:58 |
| dansmith | ack, my fault for not linking the two events across three weeks | 15:58 |
| fungi | i understand that things change. maybe trying to start organizing these things so far in advance is the problem | 15:59 |
| dansmith | two weeks to fill out a time survey is a pretty wide window.. most of the non-skippable things (i.e. non periodics) are scheduled in less than two weeks time anyway, | 15:59 |
| fungi | there were also delays on the board of directors end, unfortunately, which led the meeting invite to not go out until less than a week ahead | 16:00 |
| dansmith | which is why my availability was pretty solid, because none of the non-periodic meetings were even schedule there | 16:00 |
| dansmith | anyway, my fault for missing the connection | 16:00 |
| fungi | and yeah, i get that giving people two weeks to fill out a survey seems like a lot, but i wanted to catch people who might be on vacation the week i sent the survey out | 16:00 |
| fungi | especially since this is the height of european vacation season | 16:01 |
| dansmith | by the same token, | 16:01 |
| dansmith | only 2 days between the scheduling of the final slot and the actual thing doesn't let those people even have a chance to change things | 16:02 |
| dansmith | I guess that's the thing that's hardest.. things scheduled on wednesday of this week are already pretty well set | 16:02 |
| dansmith | anyway, I know it's a hard problem | 16:02 |
| dansmith | sounds like if I can't move things it won't be the end of the world | 16:03 |
| fungi | yeah, i think TheJulia had a hard time getting feedback from board members on the proposed schedule for all the projects too | 16:03 |
| TheJulia | hard time is a bit of an understatement | 16:03 |
| fungi | and also, yes, the idea is we'll do this a few times a year, so missing one is fine, you can always hopefully catch the next instead | 16:03 |
| TheJulia | ++ | 16:04 |
| TheJulia | It is more about building connections than anything else. | 16:04 |
| TheJulia | Spreading mutual context :) | 16:05 |
| fungi | next time i'm tempted to try a different approach: ask to get a general idea of what days of week and times of day work well for people months out, then pick a date minimizing holiday/event conflicts and publish that well in advance. if people are available they can show up, if they aren't then there'll still be another a few months after that | 16:09 |
| gmann | as this exercise is to build connection also, we should directly finalize the time for next call between board and each project governance. that should minimize the effort and gap | 16:12 |
| dansmith | fungi: yeah, knowing the final date well in advance is what I'm asking for I guess | 16:13 |
| gmann | added it in etherpad to select the next call time. if that need poll we should plan well in advance | 16:13 |
| dansmith | filling out a random time survey (which I do constantly) definitely didn't let me play defense for all those possibilities for three weeks ;) | 16:13 |
| fungi | gmann: great idea. i like picking the next meeting as soon as we hold this one, just be wary that there's a possible selection bias favoring the people for whom this meeting time worked out | 16:16 |
| fungi | so might result in picking a bad date/time for people who were unable to make the first meeting too | 16:17 |
| gmann | fungi: yeah but if we have next call time selected then other members can make them available. at least that will be more than one month in advance | 16:17 |
| gmann | and also, we can publish the call time and if it is objection from large group then we can change | 16:17 |
| fungi | yep | 16:18 |
| fungi | at a minimum, let's make sure we leave a little time at the end of the call to discuss how soon to hold the next one | 16:19 |
| fungi | like whether we want a quarterly cadence or something else | 16:19 |
| gmann | that also we can select. but I think most of the time audience will be same so selecting the exact time can also work | 16:20 |
| fungi | sounds good to me. thanks | 16:23 |
| TheJulia | fungi: I like the idea as far out as possible. It seems ot be getting harder and harder to schedule mutually agreeable times easily. | 16:39 |
| opendevreview | Elod Illes proposed openstack/governance master: Add Python3 zed unit tests https://review.opendev.org/c/openstack/governance/+/852463 | 17:36 |
| *** tosky_ is now known as tosky | 19:25 | |
| *** dasm is now known as dasm|off | 22:03 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!