| adriant | Not sure the best place to talk about this, but I'm leaving Catalystcloud, and while I plan to keep an eye on Adjutant stuff upstream a little (and may contract back for a short while) the project will ultimately not be something related to my new role, so either Catalystcloud will need to have someone step up eventually, or someone in the community will need to. | 03:38 |
|---|---|---|
| adriant | Not that I've had much time to work upstream in ages :( | 03:38 |
| *** ykarel|away is now known as ykarel | 04:44 | |
| *** pojadhav is now known as pojadhav|ruck | 05:34 | |
| *** ykarel is now known as ykarel|lunch | 08:55 | |
| yoctozepto | tc-members: it seems we have an in-cycle ptl vacancy | 09:47 |
| *** ykarel|lunch is now known as ykarel | 10:56 | |
| *** tosky_ is now known as tosky | 11:25 | |
| *** pojadhav|ruck is now known as pojadhav|brb | 11:45 | |
| fungi | adriant: per https://docs.openstack.org/project-team-guide/ptl.html#handing-over-ptl-duties i guess you don't have any successor identified and need the tc to find someone to lead adjutant before the next election? | 11:57 |
| *** pojadhav|brb is now known as pojadhav|ruck | 12:04 | |
| jungleboyj | :-( | 12:55 |
| *** lbragstad6 is now known as lbragstad | 13:28 | |
| gmann | adriant: thanks for the updates. is there anyone you know currently working Adjutant and would like to step up? | 13:45 |
| *** pojadhav|ruck is now known as pojadhav|out | 15:15 | |
| *** ykarel is now known as ykarel|away | 15:16 | |
| ade_lee | hey all, is there a template or process for proposing a possible community goal? | 18:57 |
| ade_lee | I'd like to consider having fips compatibility/compliance as a goal over the next couple of cycles. | 18:58 |
| fungi | ade_lee: https://opendev.org/openstack/governance/src/branch/master/goals/template.rst | 19:01 |
| ade_lee | I guess I would just need to upload something to https://opendev.org/openstack/governance/src/branch/master/goals/proposed ? | 19:01 |
| fungi | see also https://governance.openstack.org/tc/goals/ | 19:01 |
| ade_lee | fungi, cool thanks | 19:02 |
| gmann | ade_lee: yes, please propose in https://opendev.org/openstack/governance/src/branch/master/goals/proposed | 20:25 |
| adriant | gmann, maybe oklhost? but unsure. There are a few clouds that are using it but not contributing, and no one has enough real context to truly be PTL, but given no one other than me or some former Catalystcloud devs have that context... anyone will do. | 20:29 |
| gmann | adriant: I see, can you please put this on openstack-discuss ML in case anyone interested to drive/maintain it. and then TC will take that forward in weekly meetings or so. | 20:31 |
| adriant | I'll be moving all my OpenStack contributor emails to a personal-ish one so I will probably still get review pings etc and will be happy to help a little in my own time because I do care about the project. | 20:31 |
| adriant | cool, will send out a mailing list email today | 20:32 |
| gmann | adriant: +1, that is helpful in transition time in case we get new people would like to maintain it. | 20:32 |
| gmann | adriant: thanks | 20:32 |
| adriant | imo, it's not a bad codebase, but there definitely is a lot of work that I wanted to do :( | 20:34 |
| opendevreview | Lance Bragstad proposed openstack/governance master: Rework the yoga secure RBAC community goal https://review.opendev.org/c/openstack/governance/+/815158 | 20:50 |
| lbragstad | gmann ^ | 20:50 |
| lbragstad | gmann that's the updates at a high-level, i'd like to get some feedback on the overall structure and reworked goal, then i can clean everything up | 20:51 |
| gmann | lbragstad: thanks. I will check that. also I will send poll options for call by today or tomorrow to continue the discussion. | 20:53 |
| lbragstad | gmann awesome | 20:54 |
| gmann | lbragstad: we can do like single goal and divide it in step-wise (1st target the things you mentioned for 'yoga cycle goal') so that projects know this goal is not over until we finish all the steps but also continue working on it step-wise | 20:55 |
| gmann | which is what overall direction we are going for any community-wide goal. | 20:55 |
| gmann | tc-members: FYI, Board of Direction meeting in 5 min https://wiki.openstack.org/wiki/Governance/Foundation/26Oct2021BoardMeeting | 20:57 |
| gmann | parallel discussion if any will be in #openinfra-board | 20:57 |
| TheJulia | s/Direction/Director/ | 21:00 |
| TheJulia | :) | 21:00 |
| gmann | :) sorry for typo | 21:00 |
| lbragstad | gmann yeah - we could do that | 21:14 |
| lbragstad | i'm open to whatever so long as it's clear what exactly we need to do for each release | 21:15 |
| gmann | yeah | 21:27 |
| clarkb | Just a heads up that https://review.opendev.org/c/openstack/pbr/+/815563 illustrates an issue that other release independent projects might have with the tested runtimes specifications. Bsaically if you are library you may be expected to run against runtimes for older releases and should continue to test against those runtimes. fungi though I should mention it here as more than | 22:32 |
| clarkb | PBR may be affected | 22:32 |
| gmann | yeah, even we can have all those stable project template there instead of explicitly adding jobs to run all defined testing version they need to support stable branch. | 22:38 |
| fungi | well, also libraries like pbr which are used outside openstack may want to have voting jobs for newer interpreters before openstack's cycle-based deliverables do | 22:40 |
| gmann | sure, doing extra testing or from n-v to voting is all good. | 22:41 |
| clarkb | gmann: the problem with using templtes is the non voting stuff | 22:47 |
| clarkb | gmann: some stable releases have job as voting and others as non voting and I don't want to rely on zuul to do the right thing for us there. Instead just be explicit | 22:48 |
| clarkb | (I don't actually know what zuul will do in that case) | 22:48 |
| gmann | clarkb: ah i see. that is good point. | 22:54 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!