Considering the upcoming election, perhaps we can postpone this?

Let's discuss this during the meeting. We're already in the nomination period for elections and it ends 2026-05-21. The results come in 2026-06-15.

We can also have an interim council rep until the election is over, not having anyone seems problematic

... also that way if we mess up the procedure, there's a learning opportunity and we get to do a do-over with the new FESCo members post-election

Let's discuss this during the meeting. We're already in the nomination period for elections and it ends 2026-05-21. The results come in 2026-06-15.

BTW https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations currently says it isn't:

Nomination period is not open yet.
This period will start on 2026-05-07 at 00:00:00 UTC.

And I can't find any emails announcing such either.

(To be clear, yes, today is the 12th so it should have opened but is still saying it's not yet.)

Anyway. My 2 things:

• Dave suggested, in his resignation email, to consider rotating out this position on the Council.
• Perhaps the position could benefit from a better-defined set of expectations. In my time at FESCo, no matter who was the FESCo rep at Council, I hardly ever heard from them anything wrt Council business.

If we wish to rotate the person in the role, we will probibly want to amend the current policy around that.

The problem with rotating frequently is that sometimes there's things like council face to face sessions, which require travel planning and such (at least I think the fesco repo has attended some of those).

As for expectations, we could perhaps add a short thing to each meeting: report from the council rep on anything of note, or concerns from fesco for the rep to take to the council?
I hate to make meetings longer, but having a dedicated time to it might result in more communication? Or perhaps just a 'nothing to report, move on' waste each week... hard to say. :)

A potential issue with rotating the position is that rotating every 6 months is maybe a bit too frequent (as mentioned, potential travel planning) - but 12 months doesn't line up with ~50% of FESCo members' terms - so maybe 6 months is still better. Other than that note, I agree with comments at HEAD~2 and HEAD~1.

I think we should rotate. I think we should misalign this with the schedule by aiming for an average 9 months with a single representative, but then when we figure out who can be the next representative, let the two people involved figure out when the transition happens in a way that is most convenient based on personal schedules and avoiding unnecessary travel, etc.

Hi folks, I'm not back just yet (I will be for real back on Monday) but while I'm skimming through emails etc in an (unsuccessful) effort to calm the return to work anxiety :sweat_smile: I saw this ticket and had a thought. It might be worth considering two FESCo reps for council. I was thinking one person from each election cycle. FESCo is involved with sucha huge part of the project so I think having additional engineering representation would not be a bad thing. Plus it gives a little more coverage between council and FESCo, and more flexibility for each representative to miss or attend council meetings, both in person and online. David was not kidding when he said it can take a lot of someone's time to be an active part of these groups, so maybe two reps from FESCo could be a potential solution?

That would possibly also give FESCo a little bit more voting power in the Council, which I believe is a good thing.

BTW Welcome back!

Welcome back!

I guess that part would be up to the council if they were willing to add 2 fesco reps?

That would need to be approved by the Council. But is that something FESCo would want?

For the record, we agreed on 2026-05-12 that Fabio Valentini will serve as interim Engineering Representative on the Council. From the full log:

2026-05-12 17:27:27 <@zbyszek:fedora.im> Cool. Proposal: Fabio V. will serve as interim FESCo Council rep.
2026-05-12 17:30:19 <@zbyszek:fedora.im> !agreed (+6, 0, 0)

We discussed this during the last meeting:
AGREED: Revisit this topic after the elections (+7, 1, -0)

This ticket is now obsolete. We are tracking nominations for the new representative in https://pagure.io/fesco/issue/3620