| opendevreview | chenker proposed openstack/election master: Add Ke Chen candidacy for Cyborg https://review.opendev.org/c/openstack/election/+/805032 | 00:07 |
|---|---|---|
| opendevreview | chenker proposed openstack/election master: Add Ke Chen candidacy for Cyborg https://review.opendev.org/c/openstack/election/+/805032 | 01:09 |
| opendevreview | chenker proposed openstack/election master: Add Ke Chen candidacy for Cyborg https://review.opendev.org/c/openstack/election/+/805032 | 01:12 |
| opendevreview | Gage Hugo proposed openstack/election master: Add Gage Hugo candidacy for OpenStack Helm https://review.opendev.org/c/openstack/election/+/805095 | 01:32 |
| opendevreview | Takashi Kajinami proposed openstack/governance master: Retire puppet-monasca https://review.opendev.org/c/openstack/governance/+/805105 | 02:37 |
| opendevreview | Lingxian Kong proposed openstack/election master: Adding Lingxian Kong candidacy for Trove in Yoga https://review.opendev.org/c/openstack/election/+/805106 | 03:03 |
| *** pojadhav- is now known as pojadhav | 04:42 | |
| opendevreview | Eyal proposed openstack/election master: Add Eyal Bar-Ilan candidacy for Vitrage PTL https://review.opendev.org/c/openstack/election/+/805112 | 05:11 |
| opendevreview | Brin Zhang proposed openstack/governance master: Venus official project status https://review.opendev.org/c/openstack/governance/+/804824 | 06:19 |
| *** pojadhav- is now known as pojadhav | 07:05 | |
| *** rpittau|afk is now known as rpittau | 07:08 | |
| opendevreview | Radosław Piliszek proposed openstack/election master: Add Masakari Yoga yoctozepto candidacy as PTL https://review.opendev.org/c/openstack/election/+/805163 | 08:37 |
| *** pojadhav is now known as pojadhav|lunch | 09:01 | |
| *** poojajadhav is now known as poojadhav | 12:39 | |
| *** poojadhav is now known as poojajadhav | 12:39 | |
| *** poojajadhav is now known as pojadhav | 12:40 | |
| fungi | https://openinfra.live/ episode on "openstack basics" airs in 10 minutes! | 13:49 |
| spotz | I'm on Youtube to help if needed | 13:57 |
| yoctozepto | same here | 13:58 |
| yoctozepto | hint: change the chat to live stream instead of filtered top comments | 13:59 |
| yoctozepto | spotz: is it only me or manuel is using both Spanish and English? | 14:09 |
| spotz | yoctozepto: I've only seen one English response | 14:09 |
| yoctozepto | ack | 14:11 |
| yoctozepto | so far, I would say the presentation is not overly useful for OpenStack beginners because it is too much around the cloud | 14:16 |
| spotz | Yeah, I was expecting more like a how to do stuff like I used to teach | 14:17 |
| fungi | i hope he's working up to that | 14:17 |
| yoctozepto | fungi: I hope too but it does not look like it | 14:18 |
| yoctozepto | spotz: me too | 14:18 |
| yoctozepto | spotz: btw, https://pasteboard.co/KgCpzTg.png <- this is how I see the chat | 14:19 |
| yoctozepto | it's amusing | 14:19 |
| yoctozepto | I can read Spanish but can't write (sanely) so I'm replying in English | 14:19 |
| spotz | yoctozepto: me too:) | 14:19 |
| yoctozepto | :-) | 14:19 |
| yoctozepto | by the 20 min mark I am worried folks have already decided it's not going to be the "OpenStack Basics" they expected | 14:21 |
| fungi | yeah, as i understand it he's trying to explain the "why cloud/openstack" and "what is cloud/openstack" questions first | 14:25 |
| yoctozepto | yup | 14:25 |
| fungi | hopefully that's useful to people who don't yet know what these concepts are or why they're important | 14:25 |
| yoctozepto | I would assume it's not really our main audience for those live events though | 14:27 |
| yoctozepto | and AWS is probably more effective in explaining why people need some cloud ;-) | 14:27 |
| opendevreview | chenker proposed openstack/election master: Add Ke Chen candidacy for Watcher https://review.opendev.org/c/openstack/election/+/805232 | 14:28 |
| yoctozepto | I would say Murano is far from PaaS in the sense of Heroku and friends... as it's just an application catalogue | 14:30 |
| fungi | yeah, it was a slightly inaccurate over-generalization | 14:32 |
| yoctozepto | "a wild Ilidko appeared" | 14:34 |
| yoctozepto | Ildiko* | 14:34 |
| * yoctozepto can't type | 14:34 | |
| spotz | I'm hungry now:( | 14:35 |
| yoctozepto | spotz: I'm just having a chocolate cake | 14:35 |
| yoctozepto | so I'm protected against that pizza | 14:35 |
| fungi | chocolate pizza | 14:36 |
| spotz | IIt's almost time for bacon, eggs, and coffee:) | 14:36 |
| mnaser | breakfast pizza wee | 14:36 |
| spotz | I could make keto breakfast pizza I think:) | 14:38 |
| yoctozepto | lol | 14:39 |
| spotz | I don't feel like making crust. Just bacon, eggs, and coffee it is! | 14:40 |
| yoctozepto | but are bacon and eggs coming into coffee? | 14:52 |
| gmann | tc-members: meeting in 8 min from now | 14:52 |
| yoctozepto | because Ildiko had mango in coffeee | 14:53 |
| spotz | We have flavored coffee Cannolli, irish cream, chocolate salted caramel:) | 14:54 |
| fungi | neutrinos don't bounce, they pass through pretty much everything. neutrons *do* bounce (leading to fission reactions) | 14:55 |
| yoctozepto | fungi: yeah, I confirm | 14:56 |
| yoctozepto | spotz: https://store.steampowered.com/app/386940/Ultimate_Chicken_Horse/ | 14:57 |
| spotz | cute:) | 14:58 |
| gmann | #startmeeting tc | 15:00 |
| opendevmeet | Meeting started Thu Aug 19 15:00:05 2021 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'tc' | 15:00 |
| gmann | #topic Roll call | 15:00 |
| gmann | o/ | 15:00 |
| mnaser | bonjour | 15:00 |
| mnaser | o/ | 15:00 |
| dansmith | o/ | 15:00 |
| spotz | o/ | 15:00 |
| ricolin | o/ | 15:00 |
| gmann | absence: Belmiro Moreira (belmoreira) | 15:01 |
| yoctozepto | o/ | 15:01 |
| gmann | #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions | 15:01 |
| gmann | ^^ Today agenda | 15:01 |
| gmann | let's start | 15:01 |
| gmann | #topic Follow up on past action items | 15:02 |
| gmann | three action item | 15:02 |
| gmann | gmann to drop skyline pre-check topic from agenda - done | 15:02 |
| gmann | ykarel to add centos8 vs centos8-stream testing for old stable in PTG etherpad - done | 15:02 |
| gmann | mnaser to send the murano retirement proposal n openstack-discuss ML - this is also sent | 15:02 |
| mnaser | yup :) | 15:03 |
| gmann | and we will talk about it in next topics | 15:03 |
| gmann | thanks ykarel mnaser | 15:03 |
| gmann | Gate health check (dansmith/yoctozepto) | 15:03 |
| gmann | dansmith: yoctozepto any updates | 15:03 |
| gmann | #topic Gate health check (dansmith/yoctozepto | 15:03 |
| dansmith | so I haven't really been experiencing any systemic issues lately, | 15:03 |
| dansmith | glance is struggling with something that seems specific to glance's tests, | 15:04 |
| dansmith | so we've been doing a bunch of rechecks | 15:04 |
| dansmith | and so things seem pretty stable overall | 15:04 |
| gmann | and for py36 especially | 15:04 |
| mnaser | there was one thing i found interesting that i can bring up if that's ok | 15:04 |
| gmann | I am wondering if we should continue on py36 testing or move to py37-py38 in next release? | 15:04 |
| dansmith | gmann: I dunno, but it's not like this is actually py36, | 15:05 |
| gmann | k | 15:05 |
| fungi | what's the default python3 in centos-8 stream at the moment? | 15:05 |
| dansmith | I think it's just because it's 18.04, different mysql versions, etc and that's making it happen | 15:05 |
| gmann | yeah py36 jobs run on 18.04 | 15:05 |
| dansmith | it's likely a legit race and that's just where it's manifesting right now | 15:05 |
| yoctozepto | mnaser: bring it on :D | 15:05 |
| mnaser | http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024236.html | 15:06 |
| fungi | if centos is still going to be python 3.6 then dropping 3.6 support next cycle could be problematic | 15:06 |
| mnaser | this seems like the sort of thing that would be good to help drive i think | 15:06 |
| ykarel | centos 8 stream is python3.6 | 15:06 |
| fungi | will it ever move to newer python minor releases or does that require centos 9? | 15:06 |
| yoctozepto | mnaser: thanks, I'm coordinating them already | 15:07 |
| gmann | mnaser: agree. in our gate tempest tests use cirros image (default) in most of the job so clarkb suggestion make sense to try in that | 15:07 |
| spotz | fungi you'd have too moove to a newer release | 15:07 |
| gmann | yoctozepto: +1 | 15:07 |
| ykarel | fungi, i don't think it will move to new python3 minor, need to go with centos 9 stream , which i think includes python3.9 | 15:07 |
| fungi | but anyway, claiming we target centos/rhel means we probably need to continue not breaking python 3.6 | 15:08 |
| mnaser | yoctozepto: great, i just wanted to put some eyes at as well | 15:08 |
| gmann | fungi: +1 | 15:08 |
| mnaser | and also agreed on needing to continue to support 3.6 | 15:08 |
| dansmith | agreed we should not drop py36, and especially not just because of this glance test race thing | 15:08 |
| mnaser | or else tripleo world would break i guess | 15:08 |
| dansmith | because it has nothing to do with py36 most likely | 15:08 |
| gmann | yoctozepto: mnaser and i think some tempest test do modify it at runtime for image meta or so. | 15:08 |
| fungi | there is however some potential struggle coming, since pip and friends want to drop python 3.6 support when it reaches eol in a few months (and are already breaking 3.6 compatibility and not concerned with fixing the regressions there) | 15:08 |
| dansmith | we can't reproduce it on 18.04 outside of the gate either | 15:09 |
| gmann | ok | 15:09 |
| yoctozepto | yeah, py36 is going eol in the python community soon | 15:09 |
| gmann | let's continue on py3.6 | 15:09 |
| gmann | yoctozepto: when? | 15:09 |
| mnaser | 4 months apparently | 15:09 |
| mnaser | 23 dec 2021 | 15:09 |
| dansmith | if py36 goes eol and that actually prevents us from testing, then that's fine, and it's on RH to be supporting such an old thing anyway, but no reason to drop it until it's broken, IMHO | 15:10 |
| mnaser | "3.6 will receive bugfix updates approximately every 3 months for about 24 months. Sometime after the release of 3.7.0 final, a final 3.6 bugfix update will be released. After that, it is expected that security updates (source only) will be released as needed until 5 years after the release of 3.6 final, so until approximately 2021-12." | 15:10 |
| mnaser | src: https://www.python.org/dev/peps/pep-0494/#lifespan | 15:10 |
| gmann | yeah 23 Dec 2021 | 15:10 |
| fungi | there will come a point when we want to continue working on python 3.6 but our dependencies and toolchain utilities are dropping support for it, which will probably force us to carry a lot of pins or support multiple versions of some deps | 15:10 |
| clarkb | the pypi annotations for supported python versions help a lot with that | 15:11 |
| clarkb | if you get apckages to properly set those values it simplifies things greatyl | 15:11 |
| dansmith | we already have some | 15:11 |
| mnaser | i think the natural involvement of rh/tripleo will help navigate those 3.6 problems given they have to continue to support it | 15:11 |
| fungi | yes, that may make it not necessary to pin things, since pip will try to avoid downloading versions of things which say they don't support your version of python | 15:11 |
| yoctozepto | we already pin a lot with u-c | 15:12 |
| yoctozepto | it's just that we will need to pin pip | 15:12 |
| yoctozepto | pin the pinmaster 8-) | 15:12 |
| fungi | and possibly tox and so on | 15:12 |
| gmann | I think we should discuss it in PTG as dec is not so far | 15:12 |
| yoctozepto | yeah, possibly virtualenv, setuptools too | 15:12 |
| yoctozepto | but it's fine, we know the drill | 15:12 |
| yoctozepto | though for Yoga it trulye makes little sense to test py36 | 15:13 |
| mnaser | why? | 15:13 |
| mnaser | centos 8 stream has 3.6 | 15:13 |
| ricolin | gmann, agree, better comes up with plan for community guide | 15:13 |
| dansmith | yeah not getting that | 15:13 |
| yoctozepto | mnaser: testing on something going eol in 2 months? ;d | 15:13 |
| gmann | if we have centos8-stream keep supporting it then no need to drop | 15:14 |
| yoctozepto | but I agree that we keep it as distro has it | 15:14 |
| gmann | anyways we have lot of topic today let's discuss this in detail in PTG? | 15:14 |
| mnaser | yeah if we're going to keep centos 8 stream in listed of supported/tested distros, we need to test py36 | 15:14 |
| mnaser | but i agree with gmann wrt ptg discussion | 15:14 |
| gmann | #action gmann to add py3.6 testing plan (after its EOL -Dec 2021) in PTG etherpad | 15:14 |
| yoctozepto | perhaps we need to reword that page | 15:14 |
| gmann | #topic Murano project health (gmann) | 15:14 |
| mnaser | #link http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024120.html | 15:15 |
| gmann | #link http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024120.html | 15:15 |
| mnaser | :) | 15:15 |
| yoctozepto | two chairs | 15:15 |
| gmann | :) | 15:15 |
| mnaser | old habits die hard | 15:15 |
| gmann | +1 | 15:15 |
| gmann | so murano PTL replied to maintain it, continue maintain it | 15:15 |
| gmann | last reply #link http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024240.html | 15:15 |
| yoctozepto | yeah, it seems he strongly wants to keep it alive | 15:16 |
| gmann | I feel we should let them to decide on retirement and if they want to continue on maintaining it it should be ok | 15:16 |
| mnaser | i think the reason we wanted to do a 'tc-initiated retirement' is because we didnt get any responses | 15:16 |
| gmann | community wide goal patches are merged for murano | 15:16 |
| gmann | mnaser: yeah for many months | 15:16 |
| yoctozepto | it is a very edge case | 15:17 |
| gmann | but this is good trigger to convey the message to keep up the basic maintenance at least | 15:17 |
| mnaser | i think there are some good points that were brought up | 15:17 |
| mnaser | which is quality of the software we ship | 15:17 |
| yoctozepto | mnaser: ++ | 15:17 |
| mnaser | but that diverges the topic | 15:18 |
| yoctozepto | not drastically I guess? | 15:18 |
| fungi | i worry that if they don't respond until the tc starts a thread about retiring the project, that's not a particularly compelling reason to expect it to be actively maintained | 15:18 |
| yoctozepto | fungi: ++ | 15:18 |
| mnaser | which leaves two: 1) do we continue with the retirement of murano and 2) do we need to come up with a discussion of a 'standard' for openstack shipped software | 15:18 |
| yoctozepto | my point is that we might want to explain to the PTL | 15:19 |
| yoctozepto | that they can still develop this software | 15:19 |
| yoctozepto | using opendev tooling | 15:19 |
| yoctozepto | but outside openstack itself | 15:19 |
| gmann | yeah, there might be lot more project in that category | 15:19 |
| fungi | but per tc policy they will have to fork it to another namespace once it's retired | 15:19 |
| yoctozepto | because perhaps they are worried | 15:19 |
| yoctozepto | that it's just going to vanish with a click of a button | 15:19 |
| gmann | mnaser: +1 on 2nd point and take it from there and drop the murano retirement now | 15:19 |
| yoctozepto | like it's happened to others | 15:19 |
| yoctozepto | fungi: yeah | 15:20 |
| yoctozepto | but we can link there | 15:20 |
| mnaser | because imho if we're going with the "this thing doesnt make sense in the current landscape" as retirement reasons | 15:20 |
| mnaser | this would mean a lot of other openstack projects might see a similar story | 15:20 |
| gmann | and that is not in our policy of now | 15:20 |
| mnaser | right | 15:20 |
| yoctozepto | mnaser: although they exhibit better observable behaviour | 15:20 |
| mnaser | but maybe that's just because they have a bit more contributors | 15:21 |
| yoctozepto | yup, more general interest | 15:21 |
| mnaser | i agree that 'our current policy is not to drop projects that dont fit the landscape or seem inactive' and we've gotten a response from murano | 15:21 |
| mnaser | so maybe drop the retirement for now but open this for a ptg discussion | 15:22 |
| gmann | yeah make sense | 15:22 |
| yoctozepto | I agree with mnaser | 15:22 |
| gmann | mnaser: would you like to add it in PTG etherpad ? | 15:22 |
| mnaser | sure | 15:22 |
| gmann | I will respond to ML on we are fine on not to retire murano | 15:23 |
| gmann | thanks | 15:23 |
| mnaser | and i added to ptg list | 15:23 |
| gmann | cool thanks | 15:23 |
| gmann | anything else on this topic ? | 15:24 |
| gmann | #topic New project application: 'Venus' | 15:24 |
| gmann | there is new project application | 15:24 |
| gmann | #link http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019748.html | 15:24 |
| gmann | #link https://review.opendev.org/c/openstack/governance/+/804824 | 15:24 |
| gmann | ML is on Jan month but I think they put all the info and answer the yoctozepto query on gerrit too | 15:25 |
| gmann | please review or ask query if you have any | 15:25 |
| yoctozepto | yeah, they are responsive | 15:25 |
| gmann | Two thing to note is: 1. current repo are not in openstack namespace and can be added later or before our agreement on gerrit | 15:26 |
| gmann | 2. if we add this projetc now, there will not be any release in Xena | 15:26 |
| gmann | both looks ok to me | 15:26 |
| mnaser | it still feels very vague to me, i don't quite understand fully what it is exactly | 15:26 |
| fungi | yeah, renaming the repos into the openstack namespace will need a gerrit outage scheduled, like any rename maintenance | 15:26 |
| mnaser | it seems like some sort of mix of monasca... | 15:26 |
| yoctozepto | mnaser: query them | 15:27 |
| fungi | i recommend not planning for renaming until after the tc has approved inclusion of the project | 15:27 |
| yoctozepto | the more we know, the better | 15:27 |
| yoctozepto | fungi ++ | 15:27 |
| gmann | yeah, ML or gerrit will be good to add query | 15:27 |
| yoctozepto | I suggest focusing on gerrit | 15:27 |
| spotz | And if it won't make Xena maybe noot rename until after rellease? | 15:27 |
| gmann | fungi: yeah we are getting TC agreement first and then we will ask them to propose renaming | 15:27 |
| mnaser | yeah i think the rename is the easy bit :) | 15:28 |
| yoctozepto | yeah, let's focus on the why | 15:28 |
| gmann | yeah | 15:28 |
| fungi | right, more suggesting that you don't consider the fact that the repos are in a different namespace as a blocker to the governance change | 15:28 |
| yoctozepto | ++ | 15:29 |
| yoctozepto | I *think* I understand their perspective | 15:29 |
| gmann | so please put your query on ML or gerrit. | 15:29 |
| fungi | it should be governance approval first, then rename maintenance, then update governance for the new repo names | 15:29 |
| yoctozepto | to have log analysis tailored to OpenStack | 15:29 |
| yoctozepto | without the complexity of Monasca | 15:29 |
| gmann | and we will continue this topic in case anything we need to decide on that or any strong objection | 15:29 |
| ricolin | yoctozepto, yeah, I guess something like that | 15:29 |
| yoctozepto | I am looking forward to seeing this working with kolla | 15:30 |
| yoctozepto | but we are working on that with inspur now | 15:30 |
| gmann | +1 | 15:30 |
| yoctozepto | or more so: they are working on answering my queries | 15:30 |
| gmann | yoctozepto: did you decide on non-openstack repo to include in kolla as you said you will discuss in kolla meeting | 15:30 |
| gmann | or just trying to see if it work | 15:30 |
| yoctozepto | gmann: yeah, we decided we can add it even if it was unofficial as long as it actually does something useful | 15:31 |
| gmann | ok. +1 | 15:31 |
| yoctozepto | it looks healthy as it's brand new and inspur poured a lot of work into it | 15:32 |
| yoctozepto | but we'll see of course | 15:32 |
| gmann | yeah | 15:32 |
| yoctozepto | I understand it can get popularity in China due to mothertongue marketing :-) | 15:32 |
| gmann | let's see | 15:33 |
| gmann | anything else on this topic? | 15:33 |
| yoctozepto | not from me | 15:33 |
| gmann | #topic PTG Planning | 15:33 |
| * yoctozepto initially happy | 15:33 | |
| gmann | #link https://etherpad.opendev.org/p/tc-yoga-ptg | 15:33 |
| yoctozepto | gmann going fast | 15:33 |
| gmann | :) | 15:33 |
| yoctozepto | like a tempest :D | 15:33 |
| gmann | we are copiously adding topics there which is great | 15:34 |
| gmann | please keep adding if you find something to discuss there | 15:34 |
| gmann | nothing else to discuss on this | 15:34 |
| gmann | #topic Moving weekly meetings to video/voice calls. | 15:34 |
| gmann | there is cinder feedback on this | 15:35 |
| mnaser | i'm a big supporter of this in terms of increased engagement of meetings | 15:35 |
| mnaser | i think the longer an irc meeting goes on, the more.. things slow down | 15:35 |
| dansmith | this is for the tc meeting presumably? | 15:35 |
| mnaser | ^ yes | 15:35 |
| gmann | #link http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024260.html | 15:35 |
| gmann | dansmith: yes only TC meeting | 15:36 |
| yoctozepto | I think it makes sense to do it monthly | 15:36 |
| dansmith | oh I see, cinder feedback on video meetings in general | 15:36 |
| yoctozepto | you know, even just to see each other | 15:36 |
| dansmith | yeah I'm cool with some video meetings | 15:36 |
| gmann | logging is bit issue as brian mentioned | 15:36 |
| gmann | I am also in favor of that | 15:36 |
| yoctozepto | we can mitigate logging slightly but picking topics wisely | 15:36 |
| yoctozepto | by* | 15:36 |
| yoctozepto | by* picking | 15:37 |
| gmann | and try to summarize more in the summary email | 15:37 |
| gmann | currently I just add logs link | 15:37 |
| mnaser | yeah, i just think it's a good way to increase our overall meeting engagement | 15:37 |
| yoctozepto | yeah, your mails, gmann, are being praised ;-) | 15:37 |
| mnaser | (i sound very business-y saying that, ha) | 15:37 |
| yoctozepto | (mnaser: you do indeed!) | 15:37 |
| yoctozepto | (but we need this layer too) | 15:37 |
| mnaser | we will get better sYnErGy | 15:37 |
| gmann | yoctozepto: happy to see someone reading that and it is helpful :) | 15:38 |
| yoctozepto | mnaser: omg, I'm melting | 15:38 |
| gmann | mnaser: +1 | 15:38 |
| mnaser | no, but i really do think having a video meeting will be more engaging overall | 15:38 |
| yoctozepto | ++ | 15:38 |
| gmann | so seems no objection on video call | 15:38 |
| ricolin | We can do video meeting +etherpad (PTG like) | 15:38 |
| fungi | engaging tc members, or engaging non-tc-members? | 15:38 |
| gmann | so question is should we do every week or monthly first ? | 15:38 |
| spotz | As long as we have better notes then we get from the video meetings we do for RDO:) | 15:38 |
| gmann | and see how it goes | 15:38 |
| mnaser | fungi: i think perhaps both | 15:38 |
| yoctozepto | gmann: monthly | 15:38 |
| spotz | We do ours first meeting of the month | 15:38 |
| mnaser | folks might join in and listen | 15:38 |
| yoctozepto | mnaser, fungi: yeah, we need to at least let them join as well | 15:39 |
| gmann | yeah | 15:39 |
| fungi | as mentioned last week, i will certainly be less engaged, because i'm double and sometimes triple-booked, so while i can opportunistically participate in irc meetings, i will skip the videocalls. i may be in a minority however | 15:39 |
| yoctozepto | I guess we could optimise the schedule? | 15:40 |
| spotz | I have a CentOS Cloud SiG conflict first week of the month | 15:40 |
| fungi | i may reply in irc to things people log here as meeting notes, so maybe that's "good enough" | 15:40 |
| yoctozepto | in the worst case, you will be losing one meeting a month | 15:40 |
| gmann | let's try it on first meeting of every month. which will be 2nd sept meeting on video. and if it goes well then we can make weekly video call too | 15:40 |
| yoctozepto | fungi: ++ | 15:40 |
| spotz | But that's IRC | 15:40 |
| ricolin | gmann, +1 | 15:40 |
| mnaser | i have a few suggestions | 15:41 |
| gmann | sure | 15:41 |
| mnaser | google meet has excellent transcription, and it works in a way of recognizing who is speaking, so it is _SUPER_ accessible for anyone who's not a native speaker and rather read if they don't hear something well | 15:41 |
| mnaser | so it'll actually be like | 15:41 |
| mnaser | Rico: ....., Jeremy: ..., etc | 15:42 |
| mnaser | and there are chrome extensions which save those transcripts to publish them | 15:42 |
| gmann | NEC has some in-progress scripting tool to convert video call to text, at some time I can try to see if we can use that | 15:42 |
| mnaser | so we can have a _full_ transcript of the discussion, and it helps with accessiblity for those who might not be able to understand some things | 15:42 |
| fungi | also remember that if you're going to hold the call on a google service, you will be excluding participants from mainland china (or expecting them to break national laws in order to participate) | 15:43 |
| fungi | i don't know whether that's a concern | 15:43 |
| gmann | yeah, that is my main worry about google meet | 15:43 |
| mnaser | fungi: ah right, i wonder if dial-in works for them.. | 15:43 |
| mnaser | i've not found zoom to be good when it comes to transcription | 15:43 |
| mnaser | ok well | 15:44 |
| mnaser | we've got another meeting in place to be able to nail down the logistics | 15:44 |
| gmann | yeah and first can try on zoom or so and with the some feedback we can also discuss the best tool in PTG | 15:44 |
| ricolin | TBH it's 11:00 pm for China, so you shouldn't expect to have much access from China anyway | 15:45 |
| gmann | but having few meeting before PTG will be good to know pros and cons | 15:45 |
| gmann | ricolin: and you can access google meet right? | 15:45 |
| ricolin | yes | 15:45 |
| gmann | cool | 15:45 |
| mnaser | i'm happy to host the link/etc because we pay for it | 15:46 |
| mnaser | so no issues with time limits / etc wrt gmeet | 15:46 |
| gmann | so we agreed on monthly video call and in next meeting we can finalize the channel | 15:46 |
| mnaser | +1 | 15:46 |
| ricolin | +1 | 15:46 |
| spotz | +1 | 15:46 |
| gmann | anything else on this topic ? | 15:47 |
| mnaser | gmann: do we want to make that more official in a governance change to get the proper tc okay? | 15:47 |
| mnaser | i dont want to go through too much back and forth in a governance change | 15:47 |
| mnaser | but just so we have it put down, unless we want to make this informal | 15:47 |
| gmann | mnaser: humm, I was thinking to do it after PTG with few try feedback | 15:47 |
| mnaser | sounsd good to me | 15:47 |
| yoctozepto | yeah, let's start informal | 15:47 |
| gmann | and as per byLaw we still have more meeting now as weekly so monthly on video should be ok in any case | 15:48 |
| yoctozepto | indeed | 15:48 |
| gmann | #topic Board informal Brainstorming sessions about "community health and resource management" | 15:48 |
| mnaser | egg-cellent | 15:48 |
| gmann | :) | 15:48 |
| gmann | Allison sent invite for brainstorming session | 15:48 |
| gmann | #link http://lists.openstack.org/pipermail/foundation/2021-August/002998.html | 15:48 |
| *** pojadhav is now known as pojadhav|out | 15:49 | |
| gmann | its on Aug 24th, 2021 14:00 UTC | 15:49 |
| mnaser | i should be there | 15:49 |
| gmann | thanks | 15:49 |
| gmann | all the details are in ML including the etehrpad link | 15:50 |
| gmann | etherpad | 15:50 |
| gmann | #link https://etherpad.opendev.org/p/board-scratchpad-2021-08-24 | 15:50 |
| mnaser | my ac is broken down and they're scheduled 'between 8 and 4pm' (love that) so hopefully they don't show up during it | 15:50 |
| spotz | hehe | 15:50 |
| gmann | :) | 15:51 |
| gmann | #topic TC Election | 15:51 |
| gmann | #link https://governance.openstack.org/election/ | 15:51 |
| gmann | as you know, we have tc election for 4 seats | 15:51 |
| gmann | nomination is going on | 15:51 |
| *** rpittau is now known as rpittau|afk | 15:51 | |
| yoctozepto | 0 candidates so far | 15:51 |
| yoctozepto | worrying | 15:52 |
| dansmith | I've been waiting for someone else to do theirs so I can copyit | 15:52 |
| gmann | please check/encourage people to run for it or add your nomination if you are thinking to re-run | 15:52 |
| dansmith | I think I'm up, aren't you also gmann ? | 15:52 |
| gmann | I will re-run, might add nomination tomorrow or weekend | 15:52 |
| gmann | dansmith: yeah | 15:52 |
| mnaser | yep alongside diablo_rojo_phone and jungleboyj | 15:52 |
| ricolin | I can send message out for most Asia user groups tomorrow and see how that goes:) | 15:52 |
| spotz | I received a message from someoonoe interrested in maybe running and had suggested they attend a meeting to see what we do but their nick isn't in the channel list:( | 15:53 |
| yoctozepto | :-( | 15:53 |
| gmann | ricolin: that will be great | 15:53 |
| gmann | spotz: +1, please guide them if they need any help | 15:53 |
| dansmith | I'll do mine today | 15:53 |
| gmann | dansmith: thanks | 15:54 |
| gmann | and PTL nomination is also going on, so other action item for us until election official want to bring to us | 15:54 |
| gmann | #topic Open Reviews | 15:55 |
| gmann | #link https://review.opendev.org/q/projects:openstack/governance+is:open | 15:55 |
| spotz | gmann Always. Bad part is nominations will end before we meet again | 15:55 |
| gmann | mostly we talked about open review but if you have not voted/review yet please do | 15:55 |
| gmann | spotz: yeah, but feel free to bring in between also. we do not need to wait for meeting | 15:56 |
| gmann | we have one topic from ricolin to cover | 15:56 |
| gmann | time is less but we can continue that for couple of min if needed | 15:56 |
| yoctozepto | but not enough time | 15:56 |
| spotz | true we're just more talking during meetings so a better idea of what we do for someone who doesn't knoow | 15:56 |
| gmann | ricolin: go ahead | 15:56 |
| ricolin | #link https://etherpad.opendev.org/p/pain-point-elimination | 15:56 |
| ricolin | tc-members, so we have a lot of projects answering pain point collect action, we kind of need some brain storming about how should we keep that forward | 15:57 |
| mnaser | dang, that document is wild | 15:57 |
| ricolin | and how we can make community goal out of it | 15:57 |
| ricolin | mnaser, exactly | 15:57 |
| ricolin | even we didn't make a goal, still is something we can try to targeting on | 15:58 |
| gmann | ricolin: +1 on brainstorming. should we have few of them before PTG. some informal video call sessions ? | 15:58 |
| ricolin | gmann, yeah, I do like that a lot | 15:59 |
| gmann | and in PTG we can check if anything common and we can get some goal wide topic/things to improve | 15:59 |
| ricolin | I guess it's also up to us to figure out how to help teams to get a goal out out that etherpad | 16:00 |
| spotz | I'd be curioous thoughts on the Client as we were moving towards fully functional and then some projects went back to using their own | 16:00 |
| gmann | yeah, I feel goals depends on the common issue every or most of the project facing | 16:00 |
| fungi | i thought the suggestion which originated this exercise was that projects would focus on their individual user pain points rather than expecting the tc to provide a common goal across projects | 16:01 |
| * yoctozepto off; thanks gmann and others | 16:02 | |
| gmann | spotz: yeah that is one of the key issue we need to continue working . I do not have clear or current status on that | 16:02 |
| opendevreview | Dan Smith proposed openstack/election master: Add Dan Smith TC candidacy for Yoga https://review.opendev.org/c/openstack/election/+/805247 | 16:02 |
| gmann | anyways | 16:02 |
| gmann | I think time is less to discuss or plan those. so let's continue it in next meeting, I will add it in agenda. | 16:02 |
| gmann | ricolin: is it ok? | 16:02 |
| ricolin | yes | 16:02 |
| ricolin | thanks gmann | 16:02 |
| gmann | cool | 16:02 |
| gmann | thanks everyone for joining | 16:02 |
| ricolin | I will added it to next week's agenda | 16:02 |
| gmann | ricolin: +1 thanks | 16:03 |
| gmann | #endmeeting | 16:03 |
| opendevmeet | Meeting ended Thu Aug 19 16:03:02 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:03 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2021/tc.2021-08-19-15.00.html | 16:03 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2021/tc.2021-08-19-15.00.txt | 16:03 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2021/tc.2021-08-19-15.00.log.html | 16:03 |
| spotz | Thanks gmann and everyone! | 16:03 |
| TheJulia | mnaser: unfortunately that document has also turned into a partial complaint forum, but hey... it is someone's pain point. | 17:22 |
| fungi | yeah, i don't see complaints and pain points as being an entirely disjoint set ;) | 17:22 |
| gmann | I think we should be filter those in brainstorming time. I saw less contributors issue also there which is something many project facing | 17:35 |
| TheJulia | I was hoping more for scale/performance related things honestly, but definitely operator/use pain points. The whole original idea was setup projects or expect projects to take one and work it to elimination in the next cycle. | 17:37 |
| TheJulia | which could take entirely different pictures, but at a minimum it would be paying down debt or pain | 17:38 |
| TheJulia | and may result in backports and whatnot since surely it is not all pure feature items | 17:38 |
| gmann | agree | 17:39 |
| opendevreview | Andrey Pavlov proposed openstack/election master: Add Andrey Pavlov candidacy for Ec2 API https://review.opendev.org/c/openstack/election/+/805293 | 20:22 |
| opendevreview | Pierre Riteau proposed openstack/election master: Add Pierre Riteau's candidacy for Blazar PTL (Yoga) https://review.opendev.org/c/openstack/election/+/805306 | 21:09 |
| opendevreview | Martin Kopec proposed openstack/election master: Add Martin Kopec candidacy for Quality_Assurance PTL https://review.opendev.org/c/openstack/election/+/805313 | 22:48 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
