Thursday, 2020-08-06

*** tetsuro has joined #openstack-tc00:32
*** njohnston has quit IRC00:47
openstackgerritNate Johnston proposed openstack/governance master: Resolution to define distributed leadership for projects  https://review.opendev.org/74499501:23
*** markvoelker has quit IRC02:26
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-tc04:33
*** dklyle has quit IRC06:39
*** slaweq has joined #openstack-tc06:52
*** tetsuro has quit IRC07:09
*** e0ne has joined #openstack-tc07:30
*** tosky has joined #openstack-tc07:46
*** ralonsoh has joined #openstack-tc07:47
*** ralonsoh has quit IRC07:48
fricklergmann: I don't understand https://etherpad.opendev.org/p/tc-retirement-cleanup , why do we need to have a .gitreview? and what's the bonus of renaming all .md to .rst? seems like some big waste of resources to me07:54
*** ralonsoh has joined #openstack-tc08:06
*** belmoreira has joined #openstack-tc08:25
*** iurygregory has quit IRC08:51
*** iurygregory has joined #openstack-tc09:02
openstackgerritJean-Philippe Evrard proposed openstack/ideas master: New communication tools proposal  https://review.opendev.org/71893209:10
openstackgerritJean-Philippe Evrard proposed openstack/ideas master: Project Stopwatch  https://review.opendev.org/71892909:12
openstackgerritMerged openstack/ideas master: Teapot: Add correction about Cinder CSI support  https://review.opendev.org/73622009:27
*** markvoelker has joined #openstack-tc10:11
*** markvoelker has quit IRC10:21
*** tkajinam has quit IRC10:33
*** markvoelker has joined #openstack-tc10:57
*** markvoelker has quit IRC11:09
gmannfrickler: because of this - https://docs.opendev.org/opendev/infra-manual/latest/drivers.html#step-2-remove-project-content12:21
gmannfrickler: and we want to be consistent on all retired repos with README format and all12:22
*** ralonsoh has quit IRC12:26
*** ralonsoh has joined #openstack-tc12:26
gmannfrickler: this is previous discussion on these - http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2020-06-23.log.html#t2020-06-23T15:12:3012:29
fricklerwell the format of the README is just plain text anyway, it's just the filename you want to change. I personally would value not touching a long-retired project higher than 100% consistency, but whatever12:33
fricklerI just stumbled about this because the cookbook changes were noted in the chef channel, I couldn't approve them anyway even if I wanted to12:34
gmannfrickler: we have changed the acl for all retired repos to tc memebes for these kind of cleanup + repo retired but their code still exist like draganflow etc.12:36
gmannhttps://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/retired.config12:37
gmannmain point here is how we can avoid these inconsistent retirement in future and mnaser new job can help it but we need to cleanup all old one first - https://review.opendev.org/#/c/737559/312:38
gmannand for README format change we still need .gitreview to add.12:39
*** cloudnull has quit IRC12:43
*** cloudnull has joined #openstack-tc12:44
fungifrickler: the main reason to switch those readmes to rst is that we want to be able to use a simple apache redirect from the old project docs so if they all use the same filename it becomes much easier12:45
fungiotherwise we have to maintain a mapping somewhere of which ones use rst and which are md12:46
fungiso that we can redirect to the correct file12:46
*** ralonsoh has quit IRC13:22
fricklerfungi: do you really need to redirect to the readme explicitly? for example https://opendev.org/openstack/cookbook-openstack-database/ seems to display the readme just fine, even with the "wrong" extension13:24
fungifrickler: that's a good point, we could make the redirect just go to the root of the retired repository13:27
*** Luzi has joined #openstack-tc13:40
*** ralonsoh has joined #openstack-tc13:44
mnasertc-members: 10 minute warning :)13:51
*** diablo_rojo has joined #openstack-tc13:56
diablo_rojoo/13:56
knikollao/13:58
belmoreirao/13:59
mnaser#startmeeting tc14:00
openstackMeeting started Thu Aug  6 14:00:12 2020 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: tc)"14:00
openstackThe meeting name has been set to 'tc'14:00
mnaser#topic rollcall14:00
*** openstack changes topic to "rollcall (Meeting topic: tc)"14:00
gmanno/14:00
mnasero/14:00
belmoreirao/14:00
knikollao/14:00
diablo_rojoo/14:00
jungleboyjo/14:00
mnaser6/11 means we're good14:00
mnaserif i did math correctly14:01
mnaserright, i guess we can get going14:02
mnaser#topic Follow up on past action items14:02
*** openstack changes topic to "Follow up on past action items (Meeting topic: tc)"14:02
jungleboyj:-)14:02
mnaserevrardjp & njohnston to start writing resolution about how deconstructed PTL role14:02
mnaserdoes anyone know if there's anything about this?14:02
mnaseras both are not present right now14:02
evrardjpthere is14:02
diablo_rojoI thought I saw a paqtch last night14:02
evrardjpsomething up14:02
mnaseroh neat14:02
evrardjpplease review14:02
diablo_rojo#link https://review.opendev.org/#/c/744995/14:03
evrardjpsorry I was away last week, so I didn't prepare this meeting correctly14:03
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016336.html14:03
mnasertc-members ^ please dig into this14:03
gmannML also14:03
jungleboyjInteresting.  I will take a look.14:04
mnaser#action tc-members to follow up and review "Resolution to define distributed leadership for projects"14:04
mnasernext up14:04
mnasermnaser to find owner to start using facing API pop-up team over ML14:04
mnaserdiablo_rojo: helped me with this14:04
mnaserperhaps could fill in here? :)14:05
belmoreirayes, I can help on this14:05
mnasercool14:06
mnaserso afaik belmoreira has volunteered to help get this started and progressed14:06
belmoreiraI replied to the TC PTG summary, that I would like to own this. Will start discussing in the ML soon14:06
mnaserawesome.  thank you14:06
evrardjpthank you belmoreira :)14:06
mnasernext up, gmann update goal selection docs to clarify the goal count14:06
diablo_rojoI'll also probably be around to help and support belmoreira :)14:06
belmoreirafor sure I will need your guidance on this14:06
jungleboyjbelmoreira: Thanks!14:07
belmoreirathanks diablo_rojo14:07
gmanngoal doc update is merged #link https://review.opendev.org/#/c/739150/14:07
mnasergeat14:08
mnasergreat*14:08
mnasernext up14:08
mnasergmann start discussion around reviewing currenet tags14:08
mnaseri think this was revolving the actual tc tags14:08
gmannyeah14:09
diablo_rojoYeah that sounds right.14:09
gmannfirst is tc:approved-release. manila patch to claim tc:approved-release tag is merged so i can start removal of tc:approved-release as first step14:09
gmannand next will be assert:supports-zero-downtime-upgrade where we do not have any projects having this tag and i think no testing way also14:10
jungleboyj++14:10
jungleboyjIf it isn't be used shouldn't keep it around.14:10
diablo_rojoThere's still zaneb's open patch on adding the k8s tag as well.14:10
mnaseryeah, that seems good14:10
mnaseri'm hoping to get the k8s people involved into that one.14:10
mnaserbut we didn't get a lot of info in the etherpad14:11
gmannwe need to either have some testing framework if that is doable otherwise remove14:11
zanebmnaser: to what end?14:11
jungleboyjmnaser: ++14:11
mnaserzaneb: https://etherpad.opendev.org/p/kubernetes-cross-community-topics is what we had14:11
jungleboyjWonder if I should put out another call to the ML on that one?14:11
mnaserwe already have traction and a response from them14:11
zanebso is that session scheduled?14:11
mnaserit's up to us to do that, i haven't done it because not much has been filled14:12
mnaseri'll go ahead and do it anyways14:12
gmann+114:12
mnaser#action mnaser schedule session with sig-arch and k8s steering committee14:12
evrardjpI think holidays, plus the fact that the call was close to a release didn't help. Maybe we can be lenient on waiting an answer?14:12
mnaser#action gmann continue to audit and clean-up tags14:12
mnaserthey did already answer, they're waiting for us :)14:12
evrardjpha14:13
evrardjpmy bad, sorry.14:13
zanebfrom my perspective we have more than enough expertise here to answer the question, and I would expect that very few of the sig-arch folks know anything about openstack14:13
jungleboyjmnaser:  When you have it scheduled would be good to send an ML note and encourage people to look at the etherpad again.14:13
mnaserwill do14:13
mnaserand perhaps we should share knowledge with them and explain to them that nova = ec2 and hear their feedback on things14:13
mnaserit doesn't hurt, instead of us going about our way and doing things in a silo14:14
zanebof course starting a regular dialog with them would be valuable for other reasons14:14
mnaser++14:14
gmanntrue14:14
mnaserso that they do eventually know what's going on here :)14:14
mnaseri'll schedule it14:14
jungleboyj:-)14:14
mnasernext up, "mnaser propose change to implement weekly meetings" -- i did not do this, i do think we need this14:14
gmanni think we should decide it fast as m-2 is already passed for this cycle.14:15
mnaserit's been a bit of an annoyance because there was already a resolution to drop weekly meetings14:16
mnaserso i kinda don't want to go through the whole process only to hear a "no" --  i think it will help our engagement cause things have been quiet lately14:17
diablo_rojoI thought the agreement was that we were settling on changing the times of office hours first.14:17
mnaseranyhow, i'll keep this here for me14:17
mnaser#action mnaser propose change to implement weekly meetings14:17
jungleboyjdiablo_rojo: ++14:17
diablo_rojoAnd seeing how that goes for now14:17
jungleboyjWe know that mnaser  loves meetings.14:17
mnasertrue -- and that's taken us a whole month unfortunately14:17
diablo_rojoAnd then maybe formalizing one of them a bit more, but on rotation because timezones.14:17
diablo_rojomnaser, we've had all the results for a week ;)14:18
jungleboyjdiablo_rojo: Did we get a result from that?14:18
mnaserand this is why we need to meet more often because ML is just not getting the right engagement14:18
knikollado we have new time candidates?14:18
mnaserok, it took 3 weeks :)14:18
gmannyeah14:18
mnaseryes, we do -- so i'll work with diablo_rojo on picking the most popular times14:18
jungleboyj++14:18
mnaserfor "diablo_rojo start discussion on ML around potential items for OSF funded intern" -- i think this one was already done14:18
diablo_rojoEven still, we have them now and can move forward with the plan we agreed on last time rather than jumping ahead?14:18
gmannto continue office hour or converting one of them to meeting?14:18
diablo_rojomnaser, it is, I thought i had removed that, did you not refresh the wiki? ;)14:19
mnaserdiablo_rojo: i go over action items from last meeting -- aka http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-07-02-14.00.html14:19
diablo_rojogmann, yeah that was what we agreed on last time I thought.14:19
diablo_rojoOHHH my bad14:19
diablo_rojogot it14:19
mnaserwhatever we end up doing needs to be consistent, i don't really mind what we call it14:19
mnaseras long as we have quorum in that period of time, i'd be happy for a start14:20
mnasernext we have "njohnston and mugsie to work on getting goals groomed/proposed for W cycle"14:20
gmanni think there is no agreement on weekly meeting yet. we said to re-schedule the office hour to see how that can be more active14:20
mnaseri'll hold on to the weekly meeting idea then14:20
gmannhumm14:20
gmannand we might finish the cycle while deciding itself :)14:21
mnaseranyone know anything on the 2 points above?14:21
mnaseras they're not present14:21
gmannon goal, I did not see ML or start collecting the ideas.14:22
mnaseri'll keep it on the list then14:22
mnaser#action njohnston and mugsie to work on getting goals groomed/proposed for W cycle14:22
mnaserfinally "tc and co to help finish properly and cleanly retiring projects" -- i don't think this progressed much14:22
mnaserbut we do have a topic for discussion of this later14:22
mnaserso i dont think we can dive too deep into it14:22
mnaserany other action items we need to follow up on that are not on the agenda?14:22
diablo_rojoNone I can think of.14:24
mnaser#topic OpenStack User-facing APIs and CLIs (belmoreira)14:25
*** openstack changes topic to "OpenStack User-facing APIs and CLIs (belmoreira) (Meeting topic: tc)"14:25
mnaserbelmoreira: all yours :)14:25
belmoreiraAs discussed long ago in the PTG it would be great if we have a consistent CLI14:26
belmoreiraLet's interact with the different teams to understand the problems and missing pieces14:26
belmoreiraI'm happy to help14:26
gmann+114:26
knikolla++14:27
jungleboyj++14:27
belmoreiraWill start with an email to the ML for the discussion14:27
mnaseri think that's a really good step14:27
diablo_rojoYeah I think it would be good to get a state of the union update since the PTG from the SDK/CLI team too14:28
gmannartem is trying it since long, and was ready to volunteer for champion for goal also if we select., he can also definitely help14:28
gmannbelmoreira: will you propose the pop-up team also along with ML?14:29
diablo_rojoYes definitely a good resource. His input will be really valuable.14:29
*** njohnston has joined #openstack-tc14:29
jungleboyj++14:29
gmannyeah14:29
njohnstono/14:29
belmoreiragmann Initially I was just thinking in start the discussion. I think that will come naturally after14:30
gmannok, make sense.14:30
mnasersounds good14:30
fungithe way i've viewed the relation between pop-up teams ang goals is that the end result of a pop-up team (its dissolution criteria) would often be selection of a cycle goal14:30
mnaser#action belmoreira start discussion around openstack user-facing apis & clis14:31
diablo_rojofungi, selection and not completion of the goal?14:31
fungithe pop-up teams members would likely become goal champions, but the pop-up team doesn't really need to exist once the entire community is on board with getting the work done14:32
knikollahmm, interesting point of view. i've thought of the pop-up team's role as also assisting the various project teams, either through reviews and such.14:33
gmannyeah that is correct. it is both. helping on getting the things started and then propose goal when most of projects are ready14:34
mnaseri thin kwe can carry over the discussion into office hours14:34
mnaseri encourage belmoreira in this effort and happy to chime in when needed14:34
gmannyeah14:34
mnasernext up we have14:34
mnaser#topic W cycle goal selection start14:34
*** openstack changes topic to "W cycle goal selection start (Meeting topic: tc)"14:34
mnaseri think we haven't had any progress on this, right?14:34
gmannnjohnston is here in case he has any14:34
fungi(as far as "continuing discussions during office hours" keep in mind that the osf monthly community meeting is happening at the same time as today's office hour)14:35
njohnstonI have an action item to reach out to mugsie to get the review started this week14:36
gmannnote; we do have one goal (rootwrap) in proposed directory.14:36
*** e0ne has quit IRC14:36
mnaserok, so i guess we will stick to the same action item listed above earlier14:39
gmann+114:39
mnaser#topic Completion of retirement cleanup (gmann)14:40
*** openstack changes topic to "Completion of retirement cleanup (gmann) (Meeting topic: tc)"14:40
mnaser#link https://etherpad.opendev.org/p/tc-retirement-cleanup14:41
mnaserwe probably haven't really done anything on this so far14:41
gmannwe did :)14:41
gmannone is osf repos-14:41
mnaserwell that's good, that's a small dent14:41
fungiyep, project rename maintenance happened14:41
mnaseroh wow14:42
gmannafter interop repos, transparency-policy is also now in osf namespace and cleanup of osf repo is now merged14:42
mnaserthat's an awesome amount of patches up14:42
gmann#link https://review.opendev.org/#/c/739291/114:42
mnaserok so we can land gmann changes14:42
gmannand for other README and gitreview cleanup i have pushed all the required patches14:42
gmann#link https://review.opendev.org/#/q/topic:cleanup-retirement+(status:open+OR+status:merged)14:42
mnaserthat's amazing14:43
gmannnetworking-l2gw is in progress which is little complex #link https://review.opendev.org/#/q/topic:complete-retirement-networking-l2gw+(status:open+OR+status:merged)14:43
mnasertc-members: do we just want to agree to let gmann land their own changes?14:43
fungiit's worth a mention that, as frickler pointed out in here just before the meeting, we don't actually need to rename/convert markdown readmes to rst if we make the docs redirect just go to the root of the retired repository, since gitea will render either readme format there too14:43
mnaserunless you'd rather someone else do it, then i think lets just single core get it over with14:43
mnaserfungi: right except we wouldn't have the job that checks for retirements, or it would have a long list of exceptions14:44
gmannyeah, we had chat with frickler this morning on these14:44
mnaserthis is a good way to just make it consistent properly for good14:44
gmannbut i feel for consistency we should do14:44
gmannyeah14:44
gmannonly repo left, i think not yet initiated is openstack/python-dracclient14:45
mnaseri'd be ok with letting gmann just merge it themselves14:45
fungiyep, the consistency point is still a good one for simplifying the check job (at least if we consider having the check job look for either readme.rst ro readme.md additional complication)14:45
njohnston+114:45
diablo_rojo+114:46
mnasergmann: are you comfortable with that?14:47
gmannmnaser: i am ok14:47
mnaseranyhow, you can recheck my patch and see if it's unhappy after a few merges14:47
mnaserso we don't end up merging a lot that are missing a fix14:47
gmannyeah that is the plan14:47
mnaserperfect14:47
gmannand for openstack/python-dracclient, should we leave this to ironic team to decide the next step?14:48
mnaser#action gmann to merge changes to properly retire projects14:48
mnasergmann: yeah, i think that's the right thing to do14:48
gmannok.14:48
mnaserwell14:51
mnaseri think that's it?14:51
*** dklyle has joined #openstack-tc14:51
gmannyeah, i think so.14:53
mnasercool,14:55
mnaserthanks everyone14:55
mnaser#endmeeting14:55
*** openstack changes topic to "OpenStack Technical Committee office hours: Tuesdays at 09:00 UTC, Wednesdays at 01:00 UTC, and Thursdays at 15:00 UTC | https://governance.openstack.org/tc/ | channel logs http://eavesdrop.openstack.org/irclogs/%23openstack-tc/"14:55
openstackMeeting ended Thu Aug  6 14:55:05 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-08-06-14.00.html14:55
diablo_rojoThanks mnaser!14:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-08-06-14.00.txt14:55
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-08-06-14.00.log.html14:55
gmannthanks14:55
smcginnisRegarding python-dracclient, I'd love to get some input from everyone.14:55
jungleboyjThank you!14:55
belmoreirathanks14:55
smcginnisThere are a couple repos that are Dell specific. They are mostly driven by Dell, but they do occasionally get patches from customers and others interested in it.14:55
smcginnisAnd they are very open to having that and trying to encourage community participation.14:55
smcginnisWould folks here be open to the idea of a Dell Hardware SIG or something like that?14:56
smcginnisThey would like to have it an official OpenStack thing, rather than being off in a quiet corner by themselves doing stuff that would actively discourage broader participation.14:56
smcginnisWe kinda sorta have/had similar precendents with Power and VMware things.14:57
smcginnisTo mixed success.14:57
fungiwe have some fairly ibm-specific repos handled by the multi-arch sig right? (formerly handled by the powervmstackers team or whatever)14:57
fungier, what you just said14:57
smcginnisIf the idea is acceptable, I'd propose the creation of a new SIG that could own some of those repos.14:58
fungialso don't forget folks, community meeting starting in one minute: http://lists.openstack.org/pipermail/foundation/2020-August/002892.html14:59
smcginnisOr heck, even a Hardware Vendors SIG that could own Dell, Lenovo, HPE, etc repos to try to encourage open development by all of these that basically everyone eventually ends up using if you go down the stack far enough.14:59
smcginnisBut we would be happy to at least start with Dell and expand the scope if it actually is useful.14:59
mnaserperhaps even the redfish-y thing14:59
mnaser+s14:59
smcginnisYeah, could be a great home for things like that.14:59
gmannsmcginnis: i think that is good idea of "Hardware Vendors SIG"14:59
fungiwould out-of-tree hardware drivers also be acceptable under that umbrella?15:00
gmannyeah redfish too15:00
smcginnisfungi: As in whether they would want to use that to bring those out-of-tree repos into OpenStack-proper? Participation in the SIG itself would be open to anyone, but yeah, it could also be a way to get the code over to somewhere more open than most have right now.15:01
fungifolks have been looking for a loophole to get out-of-tree drivers hosted in the "openstack" git namespace without needing an affiliation-diverse project team responsible for them15:02
smcginnisThis could be a way for them to do that, and hopefully actually encourage some collaboration across some of these that wouldn't otherwise have much incentive to get diverse participation.15:03
fungiyeah, i don't see how a cinder driver repository for dell arrays is necessarily fundamentally different from a hypervisor driver to allow nova to boot instances on ibm powervm platform15:04
fungiso if the latter is acceptable to be hosted in the openstack git namespace under auspices of a sig, then the former could be as well15:05
*** belmoreira has quit IRC15:06
fungitc-members: reminder, the osf community meeting is underway now. this month's topic is on strategy and planning for the osf15:06
jungleboyjsmcginnis:  ++15:07
smcginnisjungleboyj: Does Lenovo have anything that would be a fit for this? Want to be a co-chair if I propose it?15:07
ricolinHardware Vendors SIG +115:08
ricolinsounds like a good idea to develop15:08
* ricolin is back tracking meeting logs15:08
jungleboyjsmcginnis: Good question.  We might have things that could benefit from this.15:09
jungleboyjI can't think of anything specific at the moment.  I would be willing to work with you on this either way.15:10
smcginnisCool, thanks! Feedback sounds favorable so far, so later I will put together a patch proposing the SIG creation.15:10
gmann+1. thanks15:11
jungleboyjWelcome.15:12
*** Luzi has quit IRC15:22
*** penick has joined #openstack-tc15:54
*** penick has quit IRC16:03
*** penick has joined #openstack-tc16:04
*** iurygregory has quit IRC16:10
*** iurygregory has joined #openstack-tc16:11
fungitc-members: for those who weren't on the community meeting call, you'll probably want to pay attention to follow-up since it was partially about taking openstack-specific references out of the osf bylaws, which also includes some special privileges originally granted to the openstack tc to allow it to participate in governing the foundation which bears the project's name16:18
fungimy takeaway is that the openstack project will be presented with a compromise which allows it some more latitude in how it defines its own governance, but at the same time gives up some direct control over how the foundation is governed16:20
fungii expect it to be a fair deal, but one where you'll want to pay close attention and weigh the options carefully16:22
gmannfungi: mnaser seems like we need some force merge on retirement cleanup as there is no jobs running on those repo after retirement, anything you guys discussed before on this - https://review.opendev.org/#/c/745128/116:38
gmannbecause adding noop jobs will be unnecessary work.16:38
fungigmann: i thought we set that acl up to allow tc members to leave verified +2 and call submit on changes16:39
fungiif we didn't, we could16:39
mnasertc members shouldn be able to verified+216:40
mnaseri can at least16:40
mnasermaybe i did a bad thing16:40
gmanni can. i see now thanks16:40
mnaserok perfect, gmann do you see a 'submit' button appear once that was done?16:40
fungithe idea was to allow tc members to bypass ci on retired repos and merge changes directly (since they don't run any jobs)16:40
openstackgerritSean McGinnis proposed openstack/governance-sigs master: Propose new Hardware Vendor SIG  https://review.opendev.org/74518516:40
mnasercause i don't see it and i think we might need to cover that :(16:40
mnaseryeah, i guess we missed the submit permission16:41
gmannmnaser: no submit button, it is on 'Ready to Submit'16:41
fungiyeah, so maybe need to ass submit for tc members to that acl16:42
fungis/ass/add/16:42
mnaserfungi: do you know of an acl in infra that covers that?16:43
gmannits there though - https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/retired.config#L416:43
gmannthis one need to remove?  https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/retired.config#L1616:44
fungimnaser: gmann: oh! i think the submit permission needs to move down to the [access "refs/heads/*"] section16:48
mnaserah, that is correct16:48
fungiin our all-projects acl we specify it under that ref glob, not under refs/for/refs/heads/*16:48
mnasergmann: can you push that change?16:48
gmannsure16:49
gmannmnaser: fungi:  this way? - https://review.opendev.org/#/c/745187/116:53
fungigmann: yep, perfect16:53
gmannthanks16:54
fungisorry i didn't spot that problem originally16:54
*** markvoelker has joined #openstack-tc16:57
openstackgerritSean McGinnis proposed openstack/governance-sigs master: Propose new Hardware Vendor SIG  https://review.opendev.org/74518517:12
openstackgerritSean McGinnis proposed openstack/governance-sigs master: Remove deprecation warning from docs build  https://review.opendev.org/74519017:15
*** penick has quit IRC17:19
*** e0ne has joined #openstack-tc17:38
*** e0ne has quit IRC17:44
*** e0ne has joined #openstack-tc17:46
*** e0ne has quit IRC17:55
*** ralonsoh has quit IRC18:06
openstackgerritNate Johnston proposed openstack/governance master: Resolution to define distributed leadership for projects  https://review.opendev.org/74499518:21
*** timburke has quit IRC18:30
*** timburke has joined #openstack-tc18:30
openstackgerritMohammed Naser proposed openstack/governance master: Move towards single office hour  https://review.opendev.org/74520018:31
openstackgerritMohammed Naser proposed openstack/governance master: Move towards dual office hours  https://review.opendev.org/74520118:32
*** gmann is now known as gmann_afk18:35
*** tosky has quit IRC19:20
*** slaweq has quit IRC21:23
*** markvoelker has quit IRC22:02
*** dklyle has quit IRC22:04
*** dklyle has joined #openstack-tc22:09
*** gmann_afk is now known as gmann22:35
*** tkajinam has joined #openstack-tc22:55
*** dklyle has quit IRC23:20
*** dklyle has joined #openstack-tc23:20

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!