*** ykarel is now known as ykarel|lunch | 07:49 | |
opendevreview | Mark Goddard proposed openstack/governance master: kolla-cli: enter retirement https://review.opendev.org/c/openstack/governance/+/814603 | 08:30 |
---|---|---|
opendevreview | Radosław Piliszek proposed openstack/governance master: Update venus repos https://review.opendev.org/c/openstack/governance/+/815254 | 08:45 |
yoctozepto | tc-members: please have a look at and review the gate-fixing patch for governance https://review.opendev.org/c/openstack/governance/+/815254 | 08:47 |
opendevreview | Radosław Piliszek proposed openstack/governance master: kolla-cli: enter retirement https://review.opendev.org/c/openstack/governance/+/814603 | 09:03 |
*** ykarel|lunch is now known as ykarel | 09:35 | |
*** noonedeadpunk_ is now known as noonedeadpunk | 10:36 | |
lbragstad | gmann i'm going to try and summarize everything we discussed last week regarding RBAC | 13:06 |
lbragstad | gmann i was thinking i should propose it to the community goal https://review.opendev.org/c/openstack/governance/+/815158 | 13:06 |
lbragstad | i'm not sure if it should all live there, since some of it sounds like a "theme" that was discussed last week (not associated to any particular release) | 13:07 |
lbragstad | but - figured i could at least get it all down on paper and we can figure out if and how to break it apart | 13:07 |
fungi | it touches enough projects that a goal could make sense if there's a specific implementation target we think all of them can reach in a particular cycle | 13:07 |
lbragstad | yeah - that's where it gets interesting... i think there is an implementation we can reach within a cycle | 13:08 |
lbragstad | but - understanding it requires understanding a lot of the context | 13:08 |
lbragstad | IMO | 13:08 |
lbragstad | i think we talked about some additional details last week that would be really cool to implement, but out of scope for the initial goal, so that feels to me like a separate, follow-on goal or possibly a "theme" that was discussed last week? | 13:13 |
fungi | any cycle goal should probably be just the smallest, first step getting completed across all the projects | 13:15 |
fungi | that unlocks them to complete more, if they have time and interest, but at least keeps things moving in the right direction and gives us a tide marker | 13:17 |
lbragstad | agreed - that makes sense | 13:19 |
lbragstad | there were several times last week where the RBAC discussion felt like an overall multi-release theme and i wasn't sure if that was inline with what the TC was entertaining | 13:20 |
lbragstad | but - i can rework the current goal to include the new direction, and the smallest amount of work necessary to implement it in yoga | 13:21 |
fungi | that was how we tackled the python2.7 to python3 migration. identified individual steps, and had a different step in each cycle | 13:25 |
*** ykarel is now known as ykarel|away | 13:25 | |
fungi | some teams completed future steps early, but at least we had a timeline to reach full implementation that way and it was easier to identify when a particular deliverable was falling behind | 13:26 |
lbragstad | ++ yeah, that sounds good | 13:46 |
*** diablo_rojo__ is now known as diablo_rojo | 14:23 | |
gmann | yoctozepto: thanks. | 14:24 |
gmann | tc-members: need one more vote on this https://review.opendev.org/c/openstack/governance/+/815254 | 14:24 |
gmann | lbragstad: thanks, looking | 14:25 |
gmann | lbragstad: only worry from me is if the next discussions (we are going to have next week call or so) can change the implementation? it should not but just in case | 14:27 |
gmann | lbragstad: then we might end up in same situation like pdf goal or so which was main concern from community in PTG | 14:27 |
lbragstad | that's fair, but i think what we're going to focus on for yoga isn't going to change much | 14:28 |
gmann | lbragstad: I am all fine to do this as goal and as we discussed decouple with release but let's finalize the things next week or so? | 14:28 |
lbragstad | ok | 14:28 |
gmann | lbragstad: you mean for targeting project scope things only and new defaults like johnthetubaguy[m] mentioned? | 14:28 |
lbragstad | kind of - with a caveat | 14:28 |
gmann | +1. | 14:28 |
gmann | lbragstad: I will setup the call next week (will send the poll on ML today or tomorrow) | 14:29 |
lbragstad | gmann this would be easier if we could collaborate on it together quick and then you could at least see what i'm trying to rewrite | 14:29 |
lbragstad | let me port what i have to an etherpad really quick | 14:29 |
fungi | taking it in small steps also means that the teams who do decide to venture on ahead of schedule will discover the pitfalls and help refine those further steps before they become new cycle goals | 14:30 |
gmann | lbragstad: thanks, that will be great and also help for others to understand the direction who were not in PTG | 14:30 |
lbragstad | https://etherpad.opendev.org/p/yoga-secure-rbac-goal | 14:30 |
opendevreview | daniel.pawlik proposed openstack/governance master: Add openstack/ci-log-processing project into TaCT https://review.opendev.org/c/openstack/governance/+/815318 | 14:34 |
gmann | lbragstad:this sounds good to me, one question does "project-admin to project-member " transition impact operators if they move to new rbac first? I think no as it is just a rename right? | 14:34 |
gmann | in term of default access they get after new rbac | 14:34 |
lbragstad | project-admin to project-member? | 14:35 |
gmann | yeah | 14:36 |
lbragstad | gmann just wrapping up a meeting | 14:58 |
gmann | lbragstad: will catch up later, need to go out now. | 15:03 |
lbragstad | gmann ack - i'll get something proposed today | 15:05 |
jungleboyj | gmann: https://review.opendev.org/c/openstack/governance/+/815254 | 16:11 |
opendevreview | Merged openstack/governance master: Update venus repos https://review.opendev.org/c/openstack/governance/+/815254 | 17:22 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!