| opendevreview | Ghanshyam proposed openstack/governance master: Add timeline to remove enforce_scope in RBAC goal https://review.opendev.org/c/openstack/governance/+/915179 | 02:51 |
|---|---|---|
| opendevreview | Ghanshyam proposed openstack/governance master: Move distributed-project-leadership model into doc https://review.opendev.org/c/openstack/governance/+/916822 | 02:55 |
| opendevreview | Ghanshyam proposed openstack/governance master: Add DPL model & liaison reset policy https://review.opendev.org/c/openstack/governance/+/916833 | 03:24 |
| gmann | tc-members ^^ after feedback ion gerrit, I am going with the approach of TC liaison for DPL model which will address the concern of TC inactivity. | 03:25 |
| gmann | tc-members ^^ also, I updated a few of my changes (a few for nits), please re-review/vote them | 03:26 |
| opendevreview | Ghanshyam proposed openstack/governance master: Add TC liaison in DPL model implementation https://review.opendev.org/c/openstack/governance/+/917516 | 03:43 |
| gmann | tc-members ^^ also adding tc-liaison in DPL implementation. I volunteer to serve a liaison for existing DPL projects. if any other TC member would like to help, please comment in gerrit. | 03:47 |
| opendevreview | hongbin proposed openstack/governance master: Move openstack/kuryr and openstack/kuryr-libnetwork to Zun https://review.opendev.org/c/openstack/governance/+/917517 | 03:56 |
| opendevreview | do3meli proposed openstack/openstack-manuals master: update get image guide for latest ubuntu release https://review.opendev.org/c/openstack/openstack-manuals/+/917536 | 06:55 |
| *** zbitter is now known as zaneb | 08:09 | |
| frickler | tc-members: please have a look at https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/917504 regarding the interaction between the PTI and the Charm project | 09:36 |
| opendevreview | Merged openstack/openstack-manuals master: update get image guide for latest ubuntu release https://review.opendev.org/c/openstack/openstack-manuals/+/917536 | 09:38 |
| jamespage | frickler: hmm that's odd - let me check on the motivations for that - 3.12 is the default Python in 24.04 so I would expect those issues to be worked on, rather than ignored | 09:39 |
| jamespage | the charm python targets are an intersection between the OpenStack supported Pythons and those provided in supported Ubuntu releases | 09:39 |
| jamespage | I would expect 3.12 and 3.10 in the list for 2024.1 and master branches - I'llcheck with Jadon | 09:41 |
| frickler | jamespage: please excuse my ignorance, but are Charms only targeting Ubuntu? if so, then dropping py3.11 testing would actually be fine, since there is no Ubuntu release with that python version. it still might need some amending of the PTI rules | 09:44 |
| jamespage | frickler: well there is one with 3.11 (mantic) but that only has a month or so of life left now | 09:45 |
| jamespage | but yes they do only target Ubuntu | 09:45 |
| opendevreview | James Page proposed openstack/governance master: Retire all single charm repositories https://review.opendev.org/c/openstack/governance/+/903490 | 09:53 |
| opendevreview | James Page proposed openstack/governance master: Retire all single charm repositories https://review.opendev.org/c/openstack/governance/+/903490 | 10:35 |
| jamespage | that review includes a change to deal with the use of a main named branch in retiring repositories but the ones being retired need another round of retirement | 10:39 |
| opendevreview | Takashi Kajinami proposed openstack/openstack-manuals master: Remove reference to ZeroMQ https://review.opendev.org/c/openstack/openstack-manuals/+/917683 | 12:26 |
| opendevreview | Takashi Kajinami proposed openstack/openstack-manuals master: Remove reference to retired projects https://review.opendev.org/c/openstack/openstack-manuals/+/917684 | 12:31 |
| opendevreview | James Page proposed openstack/governance master: Retire all single charm repositories https://review.opendev.org/c/openstack/governance/+/903490 | 13:36 |
| gmann | frickler: jamespage: irrespective of they test python 3.12 or what distro they target, python 3.11 should be voting there on master as well as on stable/2024.1 | 16:47 |
| gmann | -1 on that change, even that was removing testing from already released stable/2024.1 also | 16:47 |
| gouthamr | tc-members: the weekly IRC meeting begins here in ~13 mins | 17:47 |
| gouthamr | #startmeeting tc | 18:00 |
| opendevmeet | Meeting started Tue Apr 30 18:00:51 2024 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
| opendevmeet | The meeting name has been set to 'tc' | 18:00 |
| spotz[m] | o/ | 18:01 |
| gouthamr | #topic Rollcall | 18:01 |
| gmann | o/ | 18:01 |
| JayF | o/ | 18:01 |
| dansmith | o/ | 18:01 |
| slaweq | o/ | 18:01 |
| frickler | \o | 18:01 |
| noonedeadpunk | o/ | 18:01 |
| gtema | o/ | 18:01 |
| * gouthamr wow that's a full house :) | 18:02 | |
| frickler | wow, full house ;) | 18:02 |
| gouthamr | hey there everyone; Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct. | 18:02 |
| gouthamr | #chair frickler | 18:02 |
| opendevmeet | Current chairs: frickler gouthamr | 18:02 |
| gouthamr | ^ i will do this with each meeting; in case i get disconnected :) | 18:02 |
| frickler | ack | 18:02 |
| gouthamr | Today's meeting agenda can be found at | 18:03 |
| gouthamr | #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee (TC meeting agenda for 30th Apr 2024) | 18:03 |
| gouthamr | lets get started | 18:04 |
| gouthamr | a procedural topic | 18:04 |
| gouthamr | #topic Monthly video meeting updates | 18:04 |
| gouthamr | i was chatting with JayF about this; and i thought lets get a wider consensus on the platform we use for our monthly video meetings | 18:05 |
| gouthamr | i'd like to thank the Open Infra Foundation for letting us use a pro Zoom account so we can keep longer meetings and do other fancy things | 18:05 |
| gouthamr | but i know a lot of you were never happy with doing this; and i think the problem was with the feature gap we had in the past with Jitsi | 18:06 |
| dansmith | a lot? | 18:06 |
| gouthamr | but, having successfully used meetpad.opendev.org in the last PTG, i think its time to consider it again for our monthly meeting | 18:06 |
| gmann | also, has anyone tested the recording? because we need recording for TC meeting to be published on public youtube channel | 18:07 |
| gouthamr | dansmith: /me made an assumption based on how the community feels about non-opensource tools | 18:07 |
| JayF | ==gmann that's my only concern; that we're able to get a high quality recording | 18:07 |
| noonedeadpunk | I think we did last time we evaluated meetpad | 18:07 |
| noonedeadpunk | and it was far from being usable | 18:07 |
| gmann | yeah, we should test that before trying in meeting directly | 18:07 |
| spotz[m] | Does meetpad now record? | 18:07 |
| noonedeadpunk | It did, but smth was completely off there | 18:08 |
| dansmith | desktop integration is a big one for me, i.e. mute and other button sync, which meetpad doesn't do properly (or at all) | 18:08 |
| JayF | spotz[m]: recording on meetpad is done locally aiui | 18:08 |
| dansmith | yeah, still no recording support, you have to do it locally, AFAIK | 18:08 |
| gouthamr | gmann JayF: ++ i agree on recording; and we (in the manila team) have tested meetpad well enough this past PTG and have recorded things and things have gone swimmingly well | 18:08 |
| JayF | you're the person who is going to be responsible for recording it, so if you're onboard I am | 18:09 |
| dansmith | gouthamr: I thought cinder and glance used something else for ptg specifically for that reason? | 18:09 |
| JayF | but I'll note I don't have a strong opinion one way or the other -- in terms of issues before the TC, what platform we use for video meeting is not a large priority imo | 18:09 |
| * frickler just takes the opportunity to note again that I'm not happy with video meetings at all and would support a motion to stop them completely. and while I am +1 with the change to meetpad, I likely won't join those either | 18:09 | |
| gouthamr | ah i didn't know; but https://www.youtube.com/watch?v=Bhg4aT1B_vE&list=PLnpzT0InFrqCHg9lfMcPe136BU-27jt-x is a testament | 18:09 |
| gouthamr | dansmith ^ | 18:10 |
| dansmith | ack, just saying | 18:10 |
| dansmith | if frickler isn't going to join the video meetings anyway, is there anyone else feeling strongly about moving away from zoom? | 18:10 |
| JayF | frickler: I too would prefer no video meetings whatsoever out of the three options of "jitsi", "zoom", or "no video" :) | 18:10 |
| gmann | I am ok with zoom as it has been very smooth | 18:11 |
| JayF | frickler: I appreciate the built-in logging of text-based collaboration | 18:11 |
| slaweq | zoom is fine for me | 18:11 |
| clarkb | the recording support is built into meetpad but it records a file to your local machine | 18:11 |
| clarkb | just to clarify that it is supported but it doesn't auto upload to say youtube | 18:11 |
| clarkb | (or anywhere else) | 18:11 |
| dansmith | clarkb: or handle the recorder dropping from the call, presumably' | 18:11 |
| clarkb | yes that is the case I think | 18:12 |
| clarkb | the client has to be connected to record | 18:12 |
| gouthamr | dansmith: if there's a disconnection, the recording still gets downloaded.. but yes, it gets fragmented | 18:12 |
| dansmith | anyway, +1 for staying with zoom from me | 18:12 |
| slaweq | can it be recorded by more than one person in the same time maybe? | 18:12 |
| clarkb | yes | 18:13 |
| gouthamr | slaweq: yes | 18:13 |
| slaweq | so that could be eventually workaround if we would have e.g 2 people recording it just in case one would be disconnected | 18:13 |
| slaweq | just saying | 18:13 |
| spotz[m] | I like the idea of moving to meetpad | 18:14 |
| slaweq | it is not perfect of course but can be more likely to be fine then | 18:14 |
| gouthamr | my proposal is that we try it; if it becomes too painful, lets go back | 18:14 |
| noonedeadpunk | so basically that boils down to you and frickler | 18:15 |
| gouthamr | but, if you're against trying it, i'd like to know :) no need to stir the pot.. | 18:15 |
| dansmith | I've tried it plenty and prefer zoom, FWIW | 18:15 |
| noonedeadpunk | as in case of your absence there should be someone who can do recording as well | 18:15 |
| gouthamr | noonedeadpunk: +1 | 18:15 |
| dansmith | I'm not sure what trying we need to do, unless you mean "see how often we fail to get a usable recording" or something :) | 18:15 |
| gouthamr | ^ that | 18:16 |
| dansmith | seriously? :) | 18:16 |
| JayF | I will comment that: 1) our TC videos on yt get minimal views and 2) I got zero complaints the one time I failed to start recording directly | 18:16 |
| slaweq | sounds good for me, we are using meetpad in e.g. neutron for the ci meetins every other week and it works fine for us | 18:16 |
| JayF | so I don't think it's a large risk to try something | 18:16 |
| gmann | I am very concern on 'no/fail recording' which can be a issue with TC video call being public | 18:16 |
| dansmith | I totally don't get the mix of "we must have text-based archives of everything" and also "meh, if we fail to record no big deal" | 18:17 |
| JayF | dansmith: IME the utility of recordings is minimal compared to the utility of searchable text-based archives/notes | 18:18 |
| gmann | JayF: I have seen many people in past complaining about TC meeting transparency of video call. if it was not recorded by mistake it is fine but if do it bcz of tool we use then its issue | 18:18 |
| noonedeadpunk | yeah, despite limited interest, I believe that all recording must be safe | 18:18 |
| noonedeadpunk | otherwise we should pretty much neglect all non-recorded part... | 18:18 |
| noonedeadpunk | and yes, I also have heard some complaints about non-transparency of video calls - potentially in the same discussion as gmann did :D | 18:19 |
| fungi | fwiw, most complaints about lack of transparency of meetings was about in-person meetings, vs irc where there's a skimmable log of the discussion (skimming a video recording is nontrivial) | 18:19 |
| fungi | not about lack of recordings | 18:20 |
| JayF | fungi: ++ that's basically what I meant re: video recordings having minimal utility | 18:20 |
| noonedeadpunk | well, frankly, with todays LLMS getting audio to text (with like whisper) makes things way more trivial... | 18:20 |
| dansmith | yeah, not everyone watches every meeting, but people do need to fill-in in case they miss one, so one data point about a missing recording is not really very representative, IMHO | 18:20 |
| gmann | same with logs. not everyone ready all logs and they can complain thesame | 18:20 |
| gmann | the same | 18:20 |
| dansmith | well, it's easy to not complain if you usually don't need them, but when you do and they're not there, it's a problem | 18:21 |
| gmann | yeah | 18:21 |
| gouthamr | +1 ; so while the youtube video recording viewership may be low.. there's an archive to go back to for _something_ in case we need to | 18:21 |
| dansmith | anyway, this seems like a solution in search of a problem, because nobody that is currently not attending would if we move, and we've spent 21 minutes on this so far | 18:21 |
| gouthamr | hmmm; true | 18:22 |
| gouthamr | alright; we were split between people wanting to try it, and sticking with the solution | 18:22 |
| gouthamr | we have.. | 18:22 |
| gouthamr | so lets table this for now; honestly i did hope that we'd be more accepting of a non-commercial/open source tool and yes, it'd increase participation amongst the TC... if that's not going to happen with this tool change, i don't mind sticking to what we have | 18:23 |
| gouthamr | thank you for sharing your views on this! | 18:24 |
| gouthamr | lets jump right into the meat of this meeting | 18:24 |
| gouthamr | #topic 2024.2 TC Tracker | 18:24 |
| gouthamr | oh | 18:24 |
| gouthamr | #undo | 18:24 |
| opendevmeet | Removing item from minutes: #topic 2024.2 TC Tracker | 18:24 |
| gouthamr | #agreed The next video meeting will be on Zoom; gouthamr will share details on the ML.. we can continue to dissect the meeting tool/platform outside of the TC meeting | 18:25 |
| gouthamr | #topic 2024.2 TC Tracker | 18:25 |
| gouthamr | #link https://etherpad.opendev.org/p/tc-2024.2-tracker (Technical Committee activity tracker) | 18:25 |
| gouthamr | ^ there's been some movement on many open governance items | 18:26 |
| gouthamr | beyond proposals to the governance repo, there is ML activity captured in that tracker as well | 18:26 |
| gmann | gouthamr: ++ for adding date wise status tracking. I added the status on my item in etherpad. | 18:27 |
| gouthamr | +1 it would help me keep the ticker on things; and allow things to merge in a timely manner | 18:28 |
| gouthamr | there may be missing activities on this etherpad | 18:29 |
| gouthamr | please add them if you were keeping tab of them :) | 18:30 |
| gouthamr | i think one thing i had a question about was gate stability that a lot of work went into.. i don't know if we meant to keep checking in during this release | 18:31 |
| dansmith | honestly the work we put in was mostly in the checking, and I think the highlighting is what actually made things progress | 18:31 |
| dansmith | I mean, I think it's been that way for a couple years now | 18:32 |
| dansmith | "gate health dies in darkness" or some such | 18:32 |
| gmann | I think that is worth to continue and has helped us on progressing on gate stability even it is not stable yet | 18:32 |
| gmann | at least having TC eyes on big breaking things help | 18:32 |
| slaweq | +1 | 18:33 |
| gouthamr | +1 agreed! i'll take a stab at filling the details thus far and ask questions; is there an update anyone would like to share now? | 18:33 |
| gouthamr | taking silence as no.. | 18:34 |
| dansmith | I've been stuck on something not very upstream the last few weeks, | 18:34 |
| dansmith | so I don't have the same "butt dyno" feeling I would normally | 18:34 |
| dansmith | but I think it's been relatively decent of late, but things are starting to pick up for the cycle and that's when things will happen | 18:35 |
| slaweq | I was also off for quite some time recently but after I came back I didn't saw any major issues there | 18:36 |
| gmann | i have not seen blocking failure in this week but there are less activities so far | 18:36 |
| gmann | fixed one issue in tempest jobs but that is for victoria/wallaby branches | 18:37 |
| gouthamr | +1 i think this thingy may drive up some activity | 18:37 |
| gouthamr | #link https://canonical.com/blog/canonical-releases-ubuntu-24-04-noble-numbat (Ubuntu 24.04) | 18:37 |
| frickler | well, I was going to mention this later, but the QA team has no volunteer yet to make devstack run on that | 18:38 |
| dansmith | yeah, when do we get 24.04 jobs? | 18:38 |
| dansmith | ah | 18:38 |
| gmann | not yet | 18:38 |
| gmann | I mean no volunteer yet as frickler mentioned so not sure when we will have | 18:38 |
| frickler | also the opendev team may be thankful for help for getting mirrors set up and images built | 18:38 |
| dansmith | has someone tried and it fails, or just no known attempts yet? | 18:39 |
| frickler | no attempts afaik | 18:39 |
| dansmith | ack | 18:39 |
| fungi | some things needed updating in underlying components first (glean, dib...) | 18:39 |
| noonedeadpunk | well, in osa we tried, but it failed way before, so not representative yet. | 18:39 |
| noonedeadpunk | But I was wondering about 1 thing - I guess 24.04 is shipped with py3.12? | 18:39 |
| fungi | big thanks to frickler for helping work out a lot of that | 18:40 |
| dansmith | yeah, as I understand | 18:40 |
| noonedeadpunk | and there was some struggle with it? | 18:40 |
| noonedeadpunk | At least according to what is written in PTI | 18:40 |
| noonedeadpunk | (and plenty of ML discussions) | 18:40 |
| JayF | I think most outstanding items preventing py3.12 from running at all have been resolved | 18:40 |
| frickler | noonedeadpunk: what's written in the PTI iiuc is mainly due to 24.04 not being available when the reqs for 2024.2 were to be finalized | 18:40 |
| JayF | if that's not true I'd be interested to know what specific items still exist | 18:40 |
| fungi | note that we do already have python3.12 jobs available, they just don't run on ubuntu noble yet | 18:41 |
| dansmith | I know taskflow has some stuff that is going to explode, but I don't know if that is in 3.12 or later | 18:41 |
| gtema | Jayf: sure? Sometime ago even docs build jobs were failing for some projects | 18:41 |
| noonedeadpunk | aha, ok, gotcha | 18:41 |
| fungi | 3.13 is going to be a more painful version, due to the "removing dead batteries" effort | 18:42 |
| dansmith | fungi: yeah | 18:42 |
| JayF | gtema: I have not tested docs builds; mainly focusing on unit tests and known-broken-issues (e.g. eventlet-related stuff, sslcontext changes) | 18:42 |
| gmann | this is result for unite testing on py3.12 #link https://zuul.openstack.org/builds?job_name=openstack-tox-py312&skip=0 | 18:42 |
| gmann | I think more failing than passing | 18:43 |
| JayF | To be clear; my comment was meaning | 18:43 |
| JayF | nothing should be blcoking those projects from being 3.12 compatible now | 18:43 |
| dansmith | ah yep, taskflow is broken: https://zuul.openstack.org/build/915772d7ce8e4af191f0abf30ec22acd | 18:43 |
| dansmith | which means glance | 18:43 |
| dansmith | and probably others, cinder maybe | 18:43 |
| dansmith | can't even import it, so that'll be a problem | 18:44 |
| dansmith | (in 3.12) | 18:44 |
| noonedeadpunk | octavia? | 18:45 |
| dansmith | ah here we go, problem solved :) https://github.com/simonrob/pyasyncore | 18:45 |
| johnsom | We are just going to remove that code from taskflow | 18:46 |
| johnsom | No one is using it | 18:46 |
| dansmith | I thought it ran deeper than trivial removal | 18:46 |
| johnsom | Nope | 18:47 |
| dansmith | if not, then cool, | 18:47 |
| johnsom | There is a patch up already | 18:47 |
| dansmith | excellent | 18:47 |
| gouthamr | #link https://bugs.launchpad.net/taskflow/+bug/2026183 (taskflow shouldn't be using asyncore / asynchat anymore) | 18:47 |
| noonedeadpunk | that sounds too trivial :D | 18:47 |
| gouthamr | #link https://review.opendev.org/c/openstack/taskflow/+/916147 (Python3.12: disable process_executor, which depends on asyncore) | 18:47 |
| gouthamr | alright; do we have a recommendation on how to approach this? we have a two part problem - python3.12 and the using the latest LTS | 18:48 |
| gouthamr | maybe we tell project teams to look at their failing 3.12 jobs because we intend to switch the default to voting? | 18:49 |
| dansmith | not in this release right? | 18:50 |
| gouthamr | yeah, E would be the focus; but start now? | 18:50 |
| frickler | well one option would be to resort to only using Debian as LTS platform | 18:50 |
| dansmith | PTI says it's advisory only, so we can't do that until next release at the earliest, AFAIK | 18:50 |
| JayF | I think it's to the point of project team responsibility now, we've enabled py3.12 support in libraries we use and in oslo stuff | 18:50 |
| gmann | this release, it will be non voting only and voting in next one | 18:50 |
| JayF | it never hurts to encourage people to pay attention now though :) | 18:50 |
| gmann | but we expect project to work on issues in this release so that no issue in making it voting in next cycle | 18:50 |
| gmann | yeah | 18:51 |
| frickler | maybe jamespage has some colleagues that could be motivated ... cf. the earlier discussion about Charms | 18:52 |
| gouthamr | ^ ++ | 18:52 |
| gmann | that's even on python 3.11 which is voting job | 18:53 |
| gmann | not sure if anything py 3.12 has solution for and they want to avoid py3.11 testing | 18:53 |
| frickler | from what I read in that review the real issue was broken constraints pinning | 18:54 |
| gouthamr | we'll gather that info over the ML | 18:54 |
| gouthamr | alright; we're 5 mins to close | 18:55 |
| gouthamr | and i wanted to leave some space for open discussion | 18:55 |
| gouthamr | #topic Open Discussion | 18:55 |
| frickler | I wanted to also shortly mention the topic of global-requirements.txt cleanup that came up earlier today | 18:56 |
| frickler | stephenfin made some work in the reqs repo to clean things up, one patch removed old constraints (excludes), which now causes reqs check in other projects to fail | 18:56 |
| frickler | see e.g. the lively discussion in the nova meeting earlier | 18:57 |
| frickler | not sure yet whether some actual action on the TC side is needed, but likely worth watching at least | 18:57 |
| JayF | I took the action of approving like 10 patches in Ironic projects fixing them :D | 18:58 |
| gouthamr | #link https://meetings.opendev.org/irclogs/%23openstack-requirements/%23openstack-requirements.2024-04-30.log.html (discussion on openstack-requirements regarding dropping exclusions) | 18:58 |
| gouthamr | #link https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2024-04-30.log.html (discussion on openstack-nova regarding dropping exclusions) | 18:58 |
| frickler | #link https://review.opendev.org/c/openstack/requirements/+/916006 the relevant patch | 18:59 |
| spotz[m] | Thanks Goutham! | 18:59 |
| frickler | as, I think the fallout was a bit unexpected | 18:59 |
| frickler | s/as/yes/ | 18:59 |
| gmann | one more thing. we have now 23 open reviews. I would request to get more vote and merge the one already eligible https://review.opendev.org/q/project:openstack/governance+status:open | 19:00 |
| gouthamr | ^ gmann yes; i've a post meeting AI on this | 19:00 |
| gmann | thanks | 19:00 |
| gouthamr | perfect; we're at the hour.. the chariot turns into a pumpkin, or something | 19:00 |
| gouthamr | thank you all for attending! | 19:01 |
| gouthamr | #endmeeting | 19:01 |
| opendevmeet | Meeting ended Tue Apr 30 19:01:10 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:01 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-30-18.00.html | 19:01 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-30-18.00.txt | 19:01 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-30-18.00.log.html | 19:01 |
| slaweq | o/ | 19:01 |
| frickler | thx gouthamr and all | 19:02 |
| gtema | Thks, see ya | 19:02 |
| gmann | thanks | 19:03 |
| gouthamr | i'd like some feedback on the tc summary that went out earlier today... do you find it lacking in something? the intention is to provide an update on the meetings, and proposals in action and also include any call outs like the one about election officials | 19:25 |
| gouthamr | if you think i can add anything else into the email or structure it differently, let me know :) | 19:26 |
| gouthamr | my running notes will be here: https://etherpad.opendev.org/p/tc-weekly-update | 19:26 |
| gouthamr | i mean to send this out every monday; i slacked off a bit yesterday ... but if you have a suggestion on a good day/time let me know as well.. | 19:27 |
| gmann | gouthamr: ++, that looks good to me. thanks for restarting the weekly summary email. it was helpful especially for community members not actively involved in TC activities. | 19:40 |
| spotz[m] | ++ | 19:43 |
| gouthamr | thanks gmann and spotz[m] | 19:47 |
| fungi | oh, i meant to remind everyone at the end of the meeting that the cfp deadline for openinfra summit in september is only a month away, may 29: https://openinfrafoundation.formstack.com/forms/openinfra_asia_summit_2024 | 21:17 |
| fungi | i'm told that tickets for admission will be a mere us$60 per person (or free if you're giving a talk), and that if anyone needs travel assistance the foundation does have budget for that too | 21:19 |
| fungi | also, if you're interested in the open compute project, they'll be having their conference together with us, so one ticket gets you access to talks on both | 21:21 |
| gouthamr | i didn't know about the collocated open compute event; that is very cool | 22:42 |
| opendevreview | Merged openstack/governance master: Appoint Wenxiang Wu as PTL of Skyline https://review.opendev.org/c/openstack/governance/+/915108 | 22:57 |
| spotz[m] | Yeah I found it a litle hard to find, the links on the site don't stand out. That said put in 2 talks, 1 might not be in the right track but figured they could move it | 23:07 |
| fungi | awesome! | 23:12 |
| fungi | travel support applications can be submitted at https://openinfrafoundation.formstack.com/forms/openinfra_tsp | 23:15 |
| fungi | if your employer won't fund your travel to korea, don't hesitate to fill out an application for travel support | 23:16 |
| fungi | that's what it's there for | 23:16 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!