Meeting started at 2026-03-05 17:00:23 UTC

The Meeting name is 'Infrastructure (2026-03-05)'

!chair @nirik:matrix.scrye.com @zlopez:fedora.im @jnsamyak:matrix.org @james:fedora.im @gwmngilfen:fedora.im @patrikp:matrix.org

The Meeting Name is now infrastructure

Hello!

!hi

Michal Konecny (zlopez)

morning

Do we have any new folks with us today?

Doesn't seem like it.

Any takers for 19th?

I can take it then.

Any other announcements?

Seems like not and I don't see anything in the "we should discuss" section either so moving on...

!oncall

● @Zlopez:matrix.org (zlopez) Current Time for them: 18:11 (Europe/Prague)

The following people are oncall:

If they do not respond, please file a ticket (https://pagure.io/fedora-infrastructure/issues)

Set 🙂

Any takers for the week starting March 13th?

Since we set the oncall during the meeting itself should the date ranges be adjusted?

Not much folks here and two of us are already listed there

Yup, doesn't have to be decided right now since we have next week covered.

I can take it again easily enough

and I still actually should open a discussion about if it's useful anymore.

no pings that I can recal

no pings that I can recall

Coolio. Monitoring!

not much on the nagios side.

on the zabbix side Gwmngilfen has been adding things and tweaking things and proposing more nagios removals.

I did open a discussion about dashboards. Please do chime in if you like...

https://discussion.fedoraproject.org/t/zabbix-dashboards/182459/2

I'm not sure what else we have on this... any quesitons?

I don't have anything for monitoring, it's quiet during freeze

yeah, which is nice. :)

Moving on then.

I have a few small topics at some point...

Go ahead.

Finally getting things done from my TODO list 🙂

First, the US moves to DST on this sunday. ;( So, expect confusion with meetings. I think we were all ok with just tieing this meeting to 9am pacific time, so it would then move 1 hour next week for non us folks...

I don't have anything against that

Works for me.

next monday is the start of our next sprint and sprint planning meeting. I am not sure when the meeting is... we should probibly try and figure that out before monday. ;)

also this time per request, don't move things to the next sprint in advance, and we can dicuss them in the meeting...

I'm aware of that, will not do it this time

Just adding new things I want to work on to next sprint

right.

It was hard to finish something during freeze

yeah, we have a number of pr's waiting for after freeze now. ;)

but thats fine

anyhow, those were the things I had off hand.

Backlog refinement?

I hope I will finish at least one of the tasks I have assigned to me in progress in next sprint

sure, we can do a few tickets.

So, there's progress on https://forge.fedoraproject.org/infra/tickets/issues/12817 I can update the ticket.

That would be great to have in one place

We should probably also re-tag these as we go over them as part of being "agile".

As the older tickets use the old system.

"So, there has been progress here. A initial workflow has been figured out and @jbley is going to see what information can be migrated from the old spreadsheet here. After we do a few of these and get the data needed well known, we can spread this out to other interested folks to contibute to."

yes, we should! good catch

remove all the old tags and add pri / points ... I'd guess this is low pri and... 3 points? 5?

remove all the old labels and add pri / points ... I'd guess this is low pri and... 3 points? 5?

So to be clear the priorities are in relation to the sprint? "Low" = unlikely to be worked on in the next couple of sprints?

Also when I hover over the `backlog` tag it says "tasks that will take more than 4 hours to do" but not sure how length of time is related to it being in backlog.

One thing regarding priority tags, I stopped adding them to day to day tasks, as it doesn't make sense there, at least for me. I just add day_to_day label

see the description...

This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

yeah, good point

thats the wrong one I think?

I think 5 and low sounds good

it should be the 'priority: low' label...

I guess we could nuke the old labels... but I hate to do that for historical reasons.

We can just remove them from old tickets when we start working on them

I suppose that history is still in the ticket.

sure, but it's confusing to have some of them.... ie, 'priority low' is the one we want here, but the's also a old 'low priority' one

I can look at cleaning up the confusing ones.

I don't remember the low priority one

What about the "Priority: waiting for assignee" tag? Should that be in the tickets?

no, we don't use that anymore

it should only be points: whatever, priority: whatever, and a few more... day-to-day or app specific things like zabbix or openshift..

IMHO... we can always adjust to what people think would be the most useful

all the ones with descriptions are the global forgejo ones. we should try and use those over our custom ones where we can

Re-tagged and you gave an update in the comments. 👍️

so, this I think is still a problem.

I would love someone to work on this. ;)

pri low, 3pts ?

this is ./roles/supybot/files/meetings_by_team.sh script in ansible and value01 /srv/meetbot content

We can add it to next sprint backlog and ask if somebody wants to take it

sure.

3 points description says "the steps are well defined".

yeah, I guess not here. ;)

5 seems high tho

What does it mean to add something to the backlog? Is it the backlog tag?

it's just a shell script and needs some error checking and/or some cleanup of content

not a backlog label...

just in the backlog of the next sprint... but I am not sure it should be placed there now or only after someone takes it in the next sprint planning

BTW, the next sprint is messed up. It looks like it was created without the kanban board.

This is one of the scenarios I had in mind when I created the backlog project for releng.

shall I delete it and readd it?

yeah, the problem then becomes picking things out of the sea of backlog... which in the old setup was meant to be our trouble vs gain stuff... but it never really worked there I don't think.

I remember trying that for all our repositories, it was few thousand tickets, nobody wants to go through that

I suppose using priority is what we could do now... ie, find all 'high' from backlog and see if any of them can be worked on, then med then low...

or just oldest first

it's pretty complex to come up with a flow really.

That is how it should be, but there are things like knowledge of systems and so on

The backlog in this context means the column in the individual sprints?

Yes

yeah

I think in this case it means 'if there's spare capacity these specific things from the backlog are things we would like to have worked on this sprint'

so choose from there before the larger 'all tickets' backlog

at least thats my take on it

I was just surprised that even backlog items should be assigned

If there are on sprint board

that seems odd to me.

I remember rcalwoo saying that everything on the board should have assignee

well, we can ask about why thats desired.

I'm gonna recreate the next sprint board.

Maybe backlog is exception

ok, it's there.

I think it should be.

anyhow, shall we wrap up then?

Open floor?

Just wanted to let people know that the move of flatpaks from registry.fedoraproject.org to quay.io is moving forwards

Still few things to discuss, but moving forward

Good stuff. And with that I think it's a wrap.