| opendevreview | Jeremy Stanley proposed openstack/election master: Add affiliation lookup functionality https://review.opendev.org/c/openstack/election/+/876738 | 14:13 |
|---|---|---|
| opendevreview | Jeremy Stanley proposed openstack/election master: Add affiliation lookup functionality https://review.opendev.org/c/openstack/election/+/876738 | 14:25 |
| knikolla[m] | gmann: did you have an etherpad where you were doing the virtual ptg planning? | 14:39 |
| bauzas | btw. this time I'd like to attend the TC sessions. When you folks are going to attend those during the week ? I can try to avoid booking a Nova slot at the same time | 14:54 |
| *** blarnath is now known as d34dh0r53 | 14:58 | |
| knikolla[m] | found the etherpad https://etherpad.opendev.org/p/tc-2023-2-ptg | 15:01 |
| knikolla[m] | bauzas: I see the time slots as TBD, so it looks like we haven't booked them yet. | 15:01 |
| bauzas | knikolla[m]: yup, likewise for nova | 15:02 |
| knikolla[m] | I scheduled an agenda item for that tomorrow in the tc meeting. | 15:02 |
| bauzas | I'll book them later in the afternoon once we agree on the needed slots | 15:02 |
| bauzas | but okay, you haven't discussed it yet | 15:02 |
| bauzas | cool cool, will attend then tomorrow's TC meeting | 15:02 |
| bauzas | and in case both nova and tc slots are conflicting, I'll ask someone else in the nova community to chair | 15:03 |
| fungi | yeah, it's sort of a catch-22... i'm in a holding pattern booking the security sig session so that i have some idea of whether it will conflict with other sessions i need to be in | 15:04 |
| bauzas | I could try to book the Diablo room in advance as this is the release I started with :D | 15:41 |
| gmann | bauzas: +1 | 18:19 |
| gmann | knikolla[m]: Yeah that one. | 18:20 |
| gmann | knikolla[m]: I think we can go for 17-19 UTC slot again this time to give more community members chance to attend TC discussion. even PTG organizer does not support it but I feel we can do like we did last time and it was successful even those slots were not in PTG bot. | 18:21 |
| gmann | and we can open poll also to select the best available time | 18:22 |
| gmann | knikolla[m]: added leaderless project topic in agenda. I thought agenda addition will be open till today 2100 UTC but i saw you sent agenda in email already. but i feel like we need to work on leaderless projects as cycle is going to start | 19:03 |
| gmann | also, I will not be able to join meeting tomorrow due to some personal work | 19:03 |
| knikolla[m] | gmann: thank you! | 19:09 |
| knikolla[m] | Noted, no worries. | 19:09 |
| gmann | FYI, board meeting in ~50 min from now https://board.openinfra.dev/meetings/2023-03-07 | 20:08 |
| opendevreview | Merged openstack/governance master: Fix doc referencing 'admin_api' rule https://review.opendev.org/c/openstack/governance/+/875860 | 21:29 |
| opendevreview | Merged openstack/governance master: Move heat-translator and tosca-parser to tacker's governance https://review.opendev.org/c/openstack/governance/+/876012 | 21:34 |
| fungi | gmann: i don't know if you were involved in the discussions when we added the new project support to the foundation bylaws, but at the time we talked at length about the implications for openstack and concluded that removing openstack-specific sections from the bylaws would result in handing more control over openstack to the foundation board of directors, removing more of the openstack | 21:47 |
| fungi | project's own autonomy | 21:47 |
| fungi | i suppose if things have changed and the tc is interested in giving up some of the control it currently has over openstack, then it's worth revisiting | 21:49 |
| fungi | the other openinfra projects don't have as much power granted to their individual governance bodies as what the bylaws grant to the openstack tc | 21:50 |
| gmann | fungi: right but I am more proposing to make it generic for all projects at least what all applicable say affiliation diversity etc not removing it for OpenStack. but that is something we need to discuss that what all applicable and what all not depends on project community size etc | 21:51 |
| * JayF is now extremely curious about what the governance-diff is between OpenStack and !OpenStack OpenInfra projects | 21:52 | |
| gmann | and defining the things as common and telling the criteria of applicability will help for existing and future projects | 21:53 |
| gmann | board/bylaw level we should define common policy and let project governance handle the project specific things. | 21:54 |
| gmann | but this is what we can discuss in June meeting | 21:54 |
| gmann | June board meeting. I just want to give thoughts on those | 21:54 |
| fungi | JayF: if you read the bylaws, the board of directors is basically in charge of approving governance changes for all other projects. for openstack the tc and board have to agree, and also sections of the of the bylaws require tc approval of any changes | 22:01 |
| JayF | fungi: thanks; I assumed it'd be more complex than that. | 22:02 |
| fungi | yeah, most of it is that the bylaws allow the tc to write and change its own charter without oversight (for anything not specified in the bylaws), other projects are not guaranteed that | 22:10 |
| fungi | though also there are things like the tc can put items on the agenda for board meetings (at least that used to be in there, i don't think it got dropped in later revisions but i'd have to reread to confirm) | 22:11 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!