frickler | what has happened to the action item of fixing zuul config errors? is there someone still working on this? if not, I'd like to propose a new approach to finally get rid of at least most of them | 07:24 |
---|---|---|
frickler | o.k., I had to go back to last year's channel logs to rediscover https://etherpad.opendev.org/p/zuul-config-error-openstack | 08:13 |
frickler | I updated the current status there, it comes likely as no surprise that the largest offenders there are the same projects that lack in CI maintainance also in other metrics, see e.g. https://review.opendev.org/q/topic:reno-2023.1+status:open | 08:17 |
frickler | tc-member: so my proposal is: someone (hopefully another volunteer, but possibly me) generates patches to fix these errors (first gate: queue: issue, then project renames), then I volunteer to force-merge them | 08:18 |
frickler | this would work around both issues: lack of PTL activity and lack of CI health | 08:19 |
frickler | please let me know what you think about this and whether a formal resolution would be needed | 08:20 |
frickler | it seems elod has already started some patches, the open ones here would be the first one to be handled this way https://review.opendev.org/q/topic:fix-zuul-queue-syntax | 08:23 |
frickler | (didn't check in detail, but it looks like those are the cases where even the master branch is still broken) | 08:24 |
frickler | I guess the highlight should have been tc-members? just making sure to ring your alarm bells properly :D | 08:25 |
frickler | for context, the reason I'm pushing this again now is that I've recently found some other config errors that were almost impossible to find in this huge pile of old crap, e.g. https://review.opendev.org/c/openstack/project-config/+/884563 and https://review.opendev.org/c/openstack/devstack/+/884562 | 08:27 |
frickler | while we're at it, I'd like to also alert you of another issue: the backlog in updating upper-constraints | 08:40 |
frickler | if you look at e.g. https://review.opendev.org/c/openstack/requirements/+/881897 you'll see a growing number of libs that cannot be updated because some projects didn't adapt to them yet | 08:41 |
frickler | which of course is a self-enforcing feedback loop, since those libs are capped by u-c, projects most often don't even see the need to adapt, because all their u-c capped tests keep on working just fine | 08:42 |
frickler | in addition, there are some updates that even aren't appearing at all, because projects have capped things, thus blocking even proposed u-c updates | 08:43 |
frickler | most prominent example is sphinx, which we still cap at 4.5.0, most recent release is 7.0.1 | 08:43 |
knikolla | o/ | 13:20 |
knikolla | frickler: related to zuul config errors, i was the one who volunteered to work on that but I deprioritized the work and haven't been able to spare the time yet. | 13:21 |
jrosser | frickler: it seems quite hard to stumble across the list of config errors if you don't know where to look | 13:47 |
TheJulia | frickler: I long for a return to the bot proposing new versions, personally :) | 13:51 |
frickler | TheJulia: that's happening again since last cycle, see the patch I cited, but that's not enough if nobody follows up on those patches | 13:53 |
frickler | jrosser: not sure what you mean to say by that | 13:54 |
jrosser | well, i can't obviously navigate to it from zuul.opendev.org | 13:54 |
jrosser | i tried the other day and failed, and just now used the url from your etherpad | 13:55 |
TheJulia | frickler: I was thinking project side, not just g-r | 13:55 |
jrosser | not saying it can't be done, but there might be some UI improvement to make it easier to find | 13:55 |
frickler | TheJulia: ah, but projects don't have local pinned constraints any more. so the best a bot could do would maybe propose dummy patches for each affected project with a depends-on on the u-c bump | 13:57 |
frickler | maybe a script that does that for failing tox-cross jobs could be made | 13:58 |
TheJulia | ... which could serve as a launching pad to fix issues. You don't know what to fix if you can't see the failure | 13:58 |
TheJulia | And if the delta in versions is invisible... well back to that self fulfilling loop. | 13:59 |
frickler | well, people could follow/check the reqs updates. like have that be part of their weekly PTL routine | 13:59 |
TheJulia | That requires a context switch | 14:00 |
TheJulia | (to the bigger picture) | 14:00 |
frickler | that's a good thing to do in general, not only look at your single own project | 14:01 |
TheJulia | But if if it all people have time to focus on... | 14:01 |
frickler | knikolla: so what was your plan for proceeding? continue trying to work with PTLs? https://review.opendev.org/c/openstack/zaqar/+/861188 seems to have worked out after some time, that would need stable backports as follow-up | 14:02 |
fungi | jrosser: you mean the non-popup version of it? there is a popup you can show by clicking the bell icon along the top of the dashboard | 14:09 |
fungi | and clicking on any entry in the popup takes you to https://zuul.opendev.org/t/openstack/config-errors | 14:10 |
fungi | maybe that's not as intuitive as it could be | 14:10 |
frickler | and for completeness https://zuul.opendev.org/api/tenant/openstack/config-errors is the json version of it that is much easier to parse, like I showed for the current state in the etherpad | 14:12 |
fungi | ah, yes, i suppose that might eventually be findable through https://zuul.opendev.org/openapi but is currently incomplete | 14:14 |
* frickler instead just looked at what the UI is fetching | 14:15 | |
frickler | because doing curl on the UI page isn't really helpful and I got tired of doing copy/paste from the browser | 14:16 |
fungi | makes sense | 14:18 |
jrosser | fungi: ahha there it is! i was looking in here https://zuul.opendev.org/tenants, and my expectation was to find a config errors count and click it | 14:48 |
knikolla | frickler: yes, initially I was planning on working with PTLs. But I'm open to your approach in the cases where that doesn't work out. | 14:51 |
frickler | jrosser: adding a config error column in that table looks like a good idea to me. maybe you can propose it in the zuul matrix channel yourself? | 15:07 |
frickler | knikolla: o.k., so let's get this process started again, I can do backports for zaqar and then check the other projects one by one | 15:08 |
gmann | frickler: I am ok to force merge those, but if we can get zuul throwing error while those renaming happening can be great but do not know if that is possible. | 15:19 |
gmann | and ++ on restarting the work, knikolla I am not sure how it got remove from agenda (I think I moved it to tracker during last cycle ) but I feel we should have it in tc meeting agenda or 2023.2 tacker if you have preapred that | 15:20 |
knikolla | gmann: i have blocked 2 hours on my calendar Thursday to push through finishing the tracker. | 15:23 |
knikolla | apologies for the delay. | 15:23 |
frickler | knikolla: oh yeah, this is going to be fun, clean one config error, get the next one for free ... :-( https://review.opendev.org/c/openstack/zaqar/+/884547 | 15:37 |
knikolla | tc-member: reminder, meeting in ~1hour. | 17:01 |
knikolla | frickler: i'll take a look later today, thanks for proposing the backport. | 17:02 |
knikolla | tc-members: reminder, meeting in ~1hour. | 17:02 |
knikolla | I had a missing "s" in the previous ping :) | 17:02 |
opendevreview | Vladimir Kozhukalov proposed openstack/governance master: Add openstack-helm PTLs missing irc nick name https://review.opendev.org/c/openstack/governance/+/884757 | 17:34 |
knikolla | #startmeeting tc | 17:59 |
opendevmeet | Meeting started Tue May 30 17:59:44 2023 UTC and is due to finish in 60 minutes. The chair is knikolla. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:59 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:59 |
opendevmeet | The meeting name has been set to 'tc' | 17:59 |
knikolla | #topic Roll Call | 17:59 |
dansmith | o/ | 17:59 |
noonedeadpunk | o/ | 17:59 |
slaweq | o/ | 17:59 |
knikolla | Hi all, welcome to the weekly meeting of the OpenStack Technical Committee | 18:00 |
knikolla | A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct | 18:00 |
knikolla | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 18:00 |
knikolla | o/ | 18:00 |
gmann | o/ | 18:00 |
noonedeadpunk | I'd say it's missing important point which is PTG timeslots for Vancouver? | 18:00 |
knikolla | Before we quickly move on to the agenda item's I'm going to capture some todo items under my name, to keep me accountable | 18:00 |
knikolla | noonedeadpunk: yep, that being one of those action items. | 18:01 |
knikolla | #action knikolla Book timeslots for PTG in Vancouver | 18:01 |
gmann | and also what we are going to discuss, some pre captured topics | 18:01 |
knikolla | #action knikolla Prepare PTG agenda for Vancouver | 18:01 |
knikolla | #action Finish TC Tracker 2023.2 | 18:01 |
knikolla | I have blocked off time in my calendar for all of those topics this week | 18:02 |
* rosmaita sneaks in | 18:03 | |
knikolla | Sorry for the delay | 18:03 |
knikolla | We can circle back at the end of the meeting if there's further to discuss about that | 18:03 |
knikolla | #topic Follow up on past action items | 18:03 |
knikolla | There is 1 action item from the previous meeting | 18:03 |
knikolla | dansmith: backport memory reduction patch for devstack to yoga and look useful doing it | 18:04 |
dansmith | first part is done, haven't figured out how to do the second part yet | 18:04 |
knikolla | Depends on the audience, haha. You look pretty useful to us. I don't know if that applies to your supervisor too. | 18:04 |
knikolla | #topic Broken docs due to inconsistent release naming | 18:06 |
knikolla | There are no updates on this and I failed to capture the to do item that arose from the previous discussion | 18:06 |
knikolla | #action knikolla To fix link redirect to release from docs | 18:06 |
knikolla | #topic Gate health check | 18:07 |
knikolla | Any updates on the state of the gate? | 18:07 |
JayF | o/ | 18:07 |
dansmith | still having guest kernel crashes on cirros 0.6.1 but they look different | 18:08 |
dansmith | still waiting for enough data to say if it's better or not | 18:08 |
dansmith | otherwise I don't know of any major gate issues myself, other than the combined effect of the usual bunch of small issues | 18:08 |
knikolla | Thanks dansmith, anything else on this or gate status in general? | 18:09 |
gmann | yeah, I have also not seen very visible difference with new cirros | 18:09 |
gmann | but overall there are less timeout because of multiple fixes happened in this cycle | 18:09 |
noonedeadpunk | Yeah, I would say that gates are really goodlately | 18:09 |
dansmith | maybe worth mentioning that I did backport the flag, but it has not yet merged: https://review.opendev.org/c/openstack/devstack/+/883970 | 18:09 |
dansmith | but I just pinged some people to remind them | 18:10 |
noonedeadpunk | except nasty CentOS bumping libvirt version to 9.3... | 18:10 |
noonedeadpunk | But yeah, nothing from our side at least | 18:10 |
noonedeadpunk | haven't seen any timeouts last couple of weeks | 18:11 |
knikolla | dansmith: I +1ed that to look useful too | 18:12 |
dansmith | is that all it takes? | 18:12 |
fungi | also a reminder that opendev is working on dropping package mirrors for fedora (and possibly fedora images after that) | 18:12 |
dansmith | anyway, nothing else from me | 18:12 |
spotz | o/ | 18:12 |
knikolla | fungi: are there actions to do on our part or things that we need to monitor? | 18:13 |
fungi | other than speak up if you're heavily reliant on fedora testing, no | 18:13 |
fungi | so far the arguments for keeping fedora around have been fairly minor | 18:13 |
fungi | and what we have in opendev is a couple releases behind and ~nobody noticed/cared | 18:14 |
noonedeadpunk | I think we're missing rocky mirrors as of today? | 18:14 |
* noonedeadpunk thinks of utilizing freed space :D | 18:14 | |
knikolla | roger | 18:15 |
fungi | yes, we've been discussing what would be needed to add rocky linux mirroring | 18:15 |
fungi | but also we're trying to free space for the upcoming debian release | 18:15 |
fungi | anyway, join the discussion in opendev if you're interested in those topics | 18:15 |
knikolla | anything else on gate? | 18:16 |
noonedeadpunk | We've switched most of testing from CentOS to Rocky nowadays, so we'd use these mirrors in OSA at very least... | 18:16 |
knikolla | that seems useful and as fungi mentioned, worth discussing further in the opendev channel | 18:17 |
noonedeadpunk | ++ | 18:17 |
knikolla | #topic Keeping Python 3.8 support and clarifying Python version support | 18:17 |
knikolla | #link https://review.opendev.org/c/openstack/governance/+/882165?usp=search | 18:18 |
knikolla | #link https://review.opendev.org/c/openstack/governance/+/882154?usp=search | 18:18 |
gmann | thanks noonedeadpunk for updating those | 18:18 |
knikolla | Thanks noonedeadpunk for updating the proposals. | 18:18 |
dansmith | thanks noonedeadpunk for updating those | 18:18 |
* dansmith jumps on the bandwagon | 18:19 | |
noonedeadpunk | I've jsut noticed that commit msg for 882165 is wrong.... | 18:19 |
knikolla | lol | 18:19 |
gmann | ah | 18:19 |
gmann | it still says library | 18:19 |
noonedeadpunk | I wonder if I should update it.... | 18:19 |
noonedeadpunk | likely good to do... | 18:19 |
gmann | yeah, I think better to update to avoid confusion | 18:19 |
knikolla | I think it should be updated, yes. | 18:19 |
slaweq | ++ | 18:20 |
dansmith | do it now and we can all re-vote real quick | 18:20 |
gmann | +1 | 18:20 |
slaweq | I was just reading it now and confused by that commit message :) | 18:20 |
opendevreview | Dmitriy Rabotyagov proposed openstack/governance master: Add py38 as a PTI requirement for Python projects https://review.opendev.org/c/openstack/governance/+/882165 | 18:20 |
knikolla | ++ | 18:20 |
noonedeadpunk | oh, wow, roll-call vote is not reseted on commit msg update o_O | 18:21 |
dansmith | well, good this time :) | 18:21 |
knikolla | Yay. | 18:21 |
gmann | humm but why | 18:21 |
gmann | this is not good right | 18:22 |
noonedeadpunk | yeah, but I wonder if we should have `changekind:NO_CODE_CHANGE` | 18:22 |
noonedeadpunk | for copying votes | 18:22 |
noonedeadpunk | it's not reflecting content.... but commit message could be completely changed and nobody will notice that | 18:22 |
knikolla | I think NO_CODE_CHANGE will still have this same behavior | 18:23 |
fungi | will need to take a closer look at the current acl | 18:23 |
knikolla | we might want NO_CHANGE | 18:23 |
gmann | and depends-on can be removed which is actually kind of change | 18:23 |
noonedeadpunk | yeah | 18:23 |
knikolla | #link https://gerrit-review.googlesource.com/Documentation/config-labels.html#label_copyCondition | 18:23 |
gmann | not sure it keep Code-Reviewor its just RC voting only | 18:24 |
noonedeadpunk | it's about RC only | 18:24 |
gmann | k | 18:24 |
* noonedeadpunk trying to find that in project-config now | 18:24 | |
fungi | #link https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/governance.config | 18:24 |
fungi | i was already looking at it | 18:24 |
knikolla | Thanks fungi | 18:24 |
noonedeadpunk | #link https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/governance.config#L29 | 18:25 |
noonedeadpunk | yeah | 18:25 |
gmann | it is same for Code-Review | 18:25 |
noonedeadpunk | huh, yes, we override default behaviour of CR | 18:25 |
fungi | clarkb: ^ do you recall seeing this happen with other less-common review labels? | 18:25 |
clarkb | fungi: no, but that comes from gerrit's migration default iirc. TRIVIAL_REBASE is a superset of NO_CODE_CHANGE I want to say | 18:26 |
clarkb | or at least is documented to be, but maybe they are wrong | 18:26 |
clarkb | its all configurable though so just set it to what you want | 18:26 |
fungi | for the openstack/releases PTL-Approved label we used "changekind:NO_CODE_CHANGE OR changekind:TRIVIAL_REBASE" | 18:27 |
gmann | so it is changed in all repo config files ? | 18:27 |
clarkb | gmann: no | 18:27 |
knikolla | Commit messages are important for governance patches, so I think we should change the current behavior for Roll-Call Votes for governance. | 18:27 |
fungi | most projects inherit the default Code-Review label definition and don't override it | 18:27 |
gmann | https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/tempest.config#L12 | 18:28 |
fungi | git history for that file will probably provide some rationale | 18:28 |
clarkb | fungi: it was the conversion from the old function which was deprecated/removed | 18:28 |
clarkb | and it is based on what gerrit itself converts it as iirc | 18:28 |
clarkb | basically its the 1:1 per gerrit to what you had with afunction | 18:28 |
fungi | i mean reason for why it's got an override for code-review | 18:28 |
clarkb | its beacuse the have custom labels | 18:29 |
clarkb | I don't know why the governance repo needs custom labels though | 18:29 |
fungi | looks like https://review.openstack.org/187326 from 2015 | 18:29 |
JayF | Is this something we need to fix live in the meeting? Or can we action item a fix to check up on next week | 18:30 |
fungi | er, no, that mainly just renamed the vote, nevermind | 18:30 |
fungi | JayF: it is not, no | 18:30 |
fungi | we can pick this up in #openstack-infra | 18:30 |
knikolla | alright, anything else to discuss on Python 3.8? | 18:30 |
knikolla | both patches got a sufficient number of votes. thank you all | 18:31 |
knikolla | #topic Open Discussion and Reviews | 18:31 |
knikolla | Floor is open for any other matters to discuss | 18:31 |
fungi | oh, well i continued researching and posted in #openstack-infra, but short answer is that the reason code-review is overridden stems from a change in 2015 to intentionally make it not required for merging | 18:32 |
fungi | #link https://review.openstack.org/185785 "Alter governance repo voting rules" | 18:33 |
clarkb | I think the in person board meeting attendance for yvr needs to be requested real soon now | 18:33 |
fungi | hopefully that at least provides some background on wht it's different from other acls | 18:33 |
gmann | but copyAllScoresIfNoChange was not there | 18:33 |
clarkb | for anyone intending to go that hasn't rsvpd | 18:33 |
gmann | it says it was default true for everyone but we did not see this behavior earlier https://review.opendev.org/c/openstack/project-config/+/880115 | 18:34 |
gmann | either old flag was not working or new one added it | 18:34 |
noonedeadpunk | clarkb: I've asked Alison to count me in, but I'm not aware of details (in terms of where/when exactly) | 18:35 |
rosmaita | which day is the board meeting? | 18:35 |
noonedeadpunk | Monday | 18:35 |
clarkb | noonedeadpunk: http://board.openinfra.dev/meetings/2023-06-12 | 18:35 |
gmann | other repo where new flag NO_CODE_CHANGE is added had copyAllScoresIfNoCodeChange to true explicitly | 18:35 |
spotz | Board meeting is Monday at Microsoft | 18:35 |
clarkb | that has all the details | 18:35 |
knikolla | Thanks clarkb, spotz | 18:36 |
slaweq | spotz (@_oftc_spotz:matrix.org) in Vancouver, right? | 18:36 |
knikolla | slaweq: yes | 18:36 |
spotz | slaweq: Yeah | 18:36 |
gmann | yes | 18:36 |
spotz | It's in Gastown section so not far | 18:37 |
slaweq | ok, I will be there :) | 18:37 |
spotz | But as mentioned you need to let Allison know so you can be on the list for entrance | 18:37 |
slaweq | should I get any email with details or something like that? I already asked aprice (@_oftc_aprice:matrix.org) that I would like to be there | 18:37 |
spotz | I would assume you'd get added to the invite but not sure | 18:37 |
gmann | there is space constraints I think good to get confirmation from aprice | 18:38 |
slaweq | ok, I will confirm with aprice (@_oftc_aprice:matrix.org) to be sure that I'm on the list | 18:38 |
slaweq | thx | 18:38 |
* noonedeadpunk needs to do the same | 18:38 | |
knikolla | If there's nothing else, we can all get back 20 minutes | 18:39 |
noonedeadpunk | btw, talking about the event - does anybody knows if gold memebers rsvp dinner is only through org list or there's a path for tc? | 18:39 |
knikolla | oh, a dinner | 18:40 |
knikolla | i don't know anything about it. | 18:40 |
gmann | melwitt: it needs to be from company list i think aprice mentioned she will contact company representative to give passes | 18:40 |
gmann | but not sure if TC can get too :) | 18:40 |
noonedeadpunk | It's on Tuesday 13/6 | 18:41 |
gmann | it was for all members company getting some passes to participate in that | 18:41 |
* noonedeadpunk was thinking if to occupy place in company list or not :D | 18:41 | |
knikolla | enjoy it for the rest of us :D | 18:42 |
spotz | I don't think TC is included. Board and sponsors | 18:42 |
gmann | spotz: board also? I think it was member company and foundation staff ? | 18:42 |
noonedeadpunk | Board as well, yes | 18:42 |
dansmith | if I'm not going to be in vancouver, can I be excused now? :) | 18:42 |
spotz | There's something on Tuesday, I wouldn't have called it a dinner though:) | 18:43 |
gmann | yeah that one might be different | 18:43 |
gmann | but anyways | 18:43 |
knikolla | #endmeeting | 18:43 |
opendevmeet | Meeting ended Tue May 30 18:43:18 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:43 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2023/tc.2023-05-30-17.59.html | 18:43 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2023/tc.2023-05-30-17.59.txt | 18:43 |
opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2023/tc.2023-05-30-17.59.log.html | 18:43 |
knikolla | Enjoy dansmith | 18:43 |
slaweq | o/ | 18:43 |
dansmith | thanks | 18:43 |
knikolla | We still have the room, no need to stop the discussion about events in Vancouver | 18:44 |
noonedeadpunk | thanks and sorry, I was sponsor of offtopic discussions today... | 18:45 |
noonedeadpunk | can not stop myself | 18:45 |
spotz | heheh | 18:45 |
knikolla | No that's great, haha | 18:45 |
noonedeadpunk | I'm slightly confused though by amount of PTG teams who has signed up vs booked slots | 18:46 |
spotz | Well they need to PTGbot:) | 18:46 |
fungi | also the usual catch-22 of everyone waiting to see what slots everyone else schedules so they can avoid confilcts | 18:47 |
fungi | conflicts | 18:47 |
noonedeadpunk | as it's literally nova, designate, publiccloud-sig, security and osa as of today. | 18:47 |
diablo_rojo_phone | noonedeadpunk: there definitely hasn't been as much activity in signing up for rooms as I thought there would be. | 18:47 |
spotz | oh and if in Vancouver... https://eventyay.com/e/231a963f | 18:47 |
diablo_rojo_phone | I plan on sending a reminder out to moderators today. | 18:47 |
spotz | Yeah I just got a conflict for during the TC and leadership session so said I'd get over there if I could | 18:48 |
fungi | also if you're working on booking ptg sessions, don't forget to bring up both the summit/forum schedule and the ptg schedule side by side when you try to work around potential conflicts | 18:48 |
spotz | I grabbed the spot right after breakfast for D&I:) | 18:48 |
aprice[m] | slaweq: you are on the list | 18:48 |
* noonedeadpunk only worried about TC PTG slot | 18:48 | |
spotz | Well right after Speed Mentoring:) | 18:48 |
aprice[m] | for the vancouver board meeting | 18:48 |
fungi | i booked the two slots prior to thursday lunch for the security sig so we have the option to move our discussions to a restaurant if we want | 18:49 |
spotz | noonedeadpunk: Yeah except the D&I slot I'm just paying attention to the TC slots | 18:49 |
spotz | fungi: Good plan! | 18:49 |
slaweq | Thx for confirmation aprice | 18:49 |
noonedeadpunk | aprice[m]: can you kindly check if I am as well ? :) | 18:50 |
knikolla | How many slots do we think we need for the TC PTG? | 18:50 |
aprice[m] | noonedeadpunk: yes, you are as well | 18:50 |
knikolla | I was thinking of them being more office-hours sorts of events considering not the entire TC will be there | 18:50 |
spotz | There's also the 2 remote capable rooms if we need as well but we'd need to book a slot here and there vs claim one | 18:51 |
gmann | knikolla: depends on topics we want to cover there | 18:51 |
aprice[m] | noonedeadpunk: for the member event, i can speak to that as well. that is for silver, gold and platinum members of the foundation as well as the board and staff. We have limited space so couldnt do the technical leadership for each project, but you should check with your company as each company has a set number of passes. | 18:52 |
gmann | aprice[m]: so board members are included in that right ? | 18:53 |
aprice[m] | gmann: yep! | 18:53 |
fungi | spotz: knikolla: the remote capable rooms are, as i understand, already spoken for wednesday and half of thursday for forum sessions, but diablo_rojo_phone can probably confirm | 18:53 |
gmann | aprice[m]: thanks for confirmation | 18:53 |
aprice[m] | we will be sending more information on the member event and the board meeting this week | 18:54 |
gmann | ++, great | 18:54 |
spotz | It's getting so close! | 18:54 |
spotz | And come eat ice cream(or an alternative for dietary restrictions) after the Marketplace Mixer, link posted above:) | 18:55 |
fungi | spotz: knikolla: also i believe it's not really that the rooms are "remote capable" but rather that they're dedicated rooms, so less background noise that the giant ptg room if you want to fire up a teleconference on someone's computer | 18:55 |
spotz | Ahh, that makes sense:) | 18:55 |
noonedeadpunk | Yeah, as I'd love to do so on one of timeslots | 18:56 |
knikolla | thanks fungi | 18:56 |
fungi | but very limited availability, and maybe just for thursday afternoon at this point? i'll defer to the organizers on that part though | 18:57 |
fungi | basically it's that the forum rooms are available for select ptg sessions on request when there's not a forum session booked in them | 18:57 |
aprice[m] | is this about reservable PTG space? | 18:57 |
aprice[m] | sorry, hopping between a few thigns | 18:57 |
fungi | yes | 18:57 |
aprice[m] | ah yes | 18:57 |
spotz | yeh | 18:57 |
diablo_rojo_phone | There will be separate rooms from the main PTG room that can be reserved. | 18:58 |
diablo_rojo_phone | They do not have hardware set up for conferencing. We can however provide zoom rooms if necessary for use. | 18:58 |
aprice[m] | yeah, there are two rooms on Thursday afternoon (maybe a little Thursday morning) | 18:58 |
diablo_rojo_phone | I will be contacting moderators today for that. | 18:58 |
fungi | diablo_rojo_phone: are those the same rooms that are the forum session rooms? | 18:58 |
aprice[m] | + what diablo_rojo_phone said | 18:58 |
aprice[m] | fungi: yes | 18:58 |
fungi | thanks, that's what i thought i had heard | 18:58 |
diablo_rojo_phone | Lol | 18:58 |
noonedeadpunk | ah, damn, one time I decided not to offtop in chat and missed answer to the question I've jsut emailed.... | 19:00 |
diablo_rojo_phone | Lol no worries. I will email everyone later today. Just out trying to finish a run right now. I've got really excellent timing for scheduling these when there's a flood of questions on IRC lol. | 19:04 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!