19:00:11 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:11 <zodbot> Meeting started Thu Jan 20 19:00:11 2022 UTC. 19:00:11 <zodbot> This meeting is logged and archived in a public location. 19:00:11 <zodbot> The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:00:11 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:11 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:11 <nirik> #chair mboddu nirik pingou mobrien nb 19:00:11 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:00:11 <zodbot> Current chairs: mboddu mobrien nb nirik pingou 19:00:11 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:11 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:11 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily 19:00:11 <nirik> #info reminder: speak up if you want to work on a ticket! 19:00:13 <nirik> #topic Tickets needing review 19:00:15 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:00:43 <nirik> .ticket 10490 19:00:44 <zodbot> nirik: Issue #10490: http://fedoraplanet.org/ is not served via HTTPS - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10490 19:01:07 <nirik> low low low low ops. We have gone over this several times, but as smooge notes, perhaps it's time to revisit. 19:02:58 <nirik> thats it for new infra ones. 19:03:46 <nirik> releng has a bunch of epel stalled ones... all low/low 19:03:52 <nirik> .releng 10560 19:03:53 <zodbot> nirik: Issue #10560: Update fails to get pushed to stable - releng - Pagure.io - https://pagure.io/releng/issue/10560 19:05:09 <nirik> this is a duplicate of 19:05:20 <nirik> 10546 19:05:24 <nirik> marked duplicate 19:05:31 <nirik> .releng 10562 19:05:35 <zodbot> nirik: Issue #10562: Can we stop stable queued python-igraph from happening? - releng - Pagure.io - https://pagure.io/releng/issue/10562 19:05:54 <nirik> seems someone did a stable push and it's too late. ;( 19:06:40 <nirik> .ticket 10563 19:06:42 <zodbot> nirik: An error has occurred and has been logged. Check the logs for more information. 19:06:49 <nirik> .ticket 10563 19:06:50 <zodbot> nirik: An error has occurred and has been logged. Check the logs for more information. 19:06:54 <nirik> weird 19:06:58 <nirik> oh right 19:07:03 <nirik> .releng 10563 19:07:04 <zodbot> nirik: Issue #10563: Rename "Cantera" to "cantera" - releng - Pagure.io - https://pagure.io/releng/issue/10563 19:07:20 <nirik> med med ops. But not sure if they shouldn't just retire the one and request the new 19:08:44 <nirik> .releng 10564 19:08:45 <zodbot> nirik: Issue #10564: BuildError: package perl-Test-Name-FromLine not in list for tag epel9-testing-candidate - releng - Pagure.io - https://pagure.io/releng/issue/10564 19:10:56 <nirik> not sure what happened here. 19:10:59 <nirik> med med ops 19:11:50 <nirik> ok, thats it on releng... 19:11:55 <nirik> #topic Planning / Upcoming work 19:12:15 <nirik> I'm starting to catch up on things... hopefully next week I can have some better plans. ;) 19:12:23 <nirik> #topic Discussion / AOB 19:12:27 <nirik> anything to discuss today? 19:13:38 <phsmoura> nothing from me 19:13:49 <nirik> hey phsmoura. How's things? 19:14:39 <salimma> howdy 19:14:40 <phsmoura> fine.. waiting mass rebuild and feedbacks on issues that I worked 19:14:44 <salimma> sorry, just noticed this thing is on 19:14:46 <salimma> .hi 19:14:47 <zodbot> salimma: salimma 'Michel Alexandre Salim' <michel@michel-slm.name> 19:15:48 <nirik> hey salimma 19:15:55 <nirik> phsmoura: cool. 19:17:43 <nirik> ok, if nothing to discuss, will close out in a minute. 19:18:01 <salimma> I have one thing if we're out of topics 19:18:05 <mobrien> How did the work with Matt go nirik 19:18:34 <nirik> mobrien: good. I think we got everything moved to the right vlans. :) 19:18:38 <nirik> salimma: sure, go ahead. 19:18:45 <salimma> so: I think I floated this with nirik in passing last month. what do people think about automating 'fedpkg request-repo / request-branch'? right now it's a batch process that must be run by a human, so it only happens during business hours 19:19:09 <nirik> salimma: we have talked about this a lot. :) 19:19:28 <salimma> it's not urgent, as the current solution works well-ish, so if rel-eng is OK with an intern working on this, we might be able to find one this summer 19:19:28 <nirik> https://pagure.io/releng/issue/9274 19:19:52 <salimma> and while waiting, I can work on scoping the project 19:19:59 <nirik> well, I guess we should figure out how we want to do it to know if it would be a good thing for a intern or not... 19:21:06 <salimma> neat. yeah, we probably should do the figuring out part now - our intern application just opens, but if it's not a good fit I can always rewrite the intern project to be about something else 19:22:12 <nirik> I think the two ways we have talked about recently are 1) keep using tickets, but automate the processing (which should be pretty easy) or 2) move it into pagure-dist-git so it has nice buttons and you don't need to file tickets anymore... but there may be other ways... 19:22:36 <salimma> yeah, from a quick perusing of the ticket that seems correct 19:23:07 <nirik> we might try and rope in pingou sometime to tell us how practical the pagure-dist-git way is... 19:23:08 <salimma> wouldn't 2) be a lot of wasted effort if (stars forbid) we ended up switching away from pagure? 19:23:39 <salimma> I'm willing to attend a super early meeting if that means we can pick pingou's brain 19:23:41 <nirik> well, yeah, it would have to be reimplemented in any new setup, but there's also a bunch of other things there that would need to be reimplemented... 19:24:14 <nirik> so I dunno. Thats a consideration to take into account I guess. 19:24:42 <salimma> so TL;DR - a) let's get the design sorted, and b) conditionally, we're OK having an intern actually do the work ? 19:24:45 <nirik> using a ticketing system for a automated process seems... poor to me. but it does have advantages 19:25:21 <nirik> works for me... :) I don't want to foist it on a inten if it's super complex or something tho... 19:26:00 <salimma> right, but we can always break it down so it's not all-or-nothing. in the end, the intern manager gets to weigh in on if the intern does a good job or not anyway 19:26:12 <salimma> if it turns out to be simple, I actually would have to find /more/ work for the intern anyway 19:26:12 <nirik> sure. 19:26:17 <salimma> * assuming we get one 19:26:45 <nirik> if you dont end up getting one, and we have it ready to go, we could also put in for outreachy or the like... 19:27:17 <nirik> anyhow, if you have cycles to drive it forward, sounds great to me. 19:27:18 <nirik> :) 19:27:58 <salimma> yup, or even do it ourselves 19:28:12 * nirik nods. 19:28:18 <salimma> yup, I'll try and drive this. thanks! 19:28:41 <nirik> cool. Thanks salimma! 19:29:06 <nirik> ok, anything else, or shall we close out? 19:29:42 <nirik> ok, thanks everyone! 19:29:45 <nirik> #endmeeting