Fedora-Council/tickets ticket #470: Two proposals regarding elected Fedora Council reps

@mattdm filed Fedora-Council/tickets ticket #470. Discuss here and record votes and decisions in the ticket.

Ticket text:


+1 :+1:

The continuity and easier annual planning make sense. I support a single election round for the Fedora Council.

I am -1 to Option B. 18 months is a long time and there is a whole lot of $LIFE that can happen in that time.

I am +0 to either option A or C.

-1 :-1:

We need to do more to ensure our existing elected reps are better supported and empowered to do good work in the Council. Our past few elections were low turnout in candidates who ran. I prefer that we iterate and build on what we have first to make it successful, before adding more people onto it.

Also worth noting, I am monitoring at least two emerging Community Initiatives that would come to the Council for review in a month or two. This also means two additional Council seats added from the Community Initiatives themselves.

1 Like

Option A is the best approach. Asking someone to commit to a volunteer position for 18 months is a lot and Option C is bad optically.

The difficulty here is that this needs to go through the Policy Change Policy, which means the election process should be well underway by the time this gets comment and final votes.

As a procedural matter, this should be a separate ticket. On the substance, I’m opposed. Historically, we’ve had a lot of trouble with sustaining Council member engagement, so I don’t see a benefit to adding a third seat. It adds a cost, though, because it means paying for more travel and hotel for in-person Council meetings. It seems like a poor use of our project resources.


Adding another seat was kind of an afterthought, and I’m persuaded it’s generally a bad idea. However, putting the procedural-separate matters together into one gives me an idea for another option:

D. Run this election as normal, but elect two more candidates in April/May. There would be three elected positions from May until the end of term at the F41 election cycle.

This would let us make the change without postponing for another year and half, and without disrupting the current election or short-circuiting the Policy Change Policy.

And because of the timing, it would avoid increasing the Council F2F cost. It might mean another person for Flock, but I think anyone likely to be elected would also probably be eligible to ask for travel funds for that anyway.

1 Like

Coming back to this, with less urgency since we’re past the immediate election… but I’d like this to be in place well ahead of the next one.

Proposal: In April/May, elect two representatives. There will be three elected positions from May for about half a year, until the end-of-term at the F41 election cycle (at which point Akashdeep’s normal term ends). After that, we’ll continue with two elected representatives, with both terms ending and beginning in April/May every year.

I am curious, why not just keep it to one seat with a 6-month term in April/May? Why should it be two seats? I didn’t follow that.

My concern is that our past few elections have been single candidate elections. I’m not sure adding more seats will get us the results we want. I could be convinced otherwise though.