Two proposals regarding elected Fedora Council reps #470

Closed
opened 2023-11-08 16:14:25 +00:00 by mattdm · 13 comments
  1. Currently, we elect one Council representative every six months, for a twelve-month term. I think the idea was to provide continuity. However:
    • In practice, this stagger is more confusing than useful. We have a lot of longer-term Council positions.
    • It doubles the election overhead. Likewise, it's actually easier to bring on two new people at once.
    • I have an unsupported intuition that we'd get more interest and attention when it's not just one seat available.
    • A new person elected in November makes it hard to plan for our annual in-person meeting in January or early February.

Therefore, I propose that we move to having both elected reps aligned with the April/May release -- still a 1-year term, but both at the same time. We could either

A. Make the presently-to-be-elected term a short one, ending in 6 months.
B. Go the other way, and make it 18 months.
C. Extend the current term by six months, skipping the current election.

My suggestion would be C, presuming the current representative (@bookwar) is up for it.

  1. While we're at a it, what do you all think about expanding the number of elected reps from two to three? With the new Executive Sponsor duty, and with everything we've got planned, I feel like more is merrier.
1. Currently, we elect one Council representative every six months, for a twelve-month term. I think the idea was to provide continuity. However: * In practice, this stagger is more confusing than useful. We have a lot of longer-term Council positions. * It doubles the election overhead. Likewise, it's actually easier to bring on two new people at once. * I have an unsupported intuition that we'd get more interest and attention when it's not just one seat available. * A new person elected in November makes it hard to plan for our annual in-person meeting in January or early February. Therefore, I propose that we move to having both elected reps aligned with the April/May release -- still a 1-year term, but both at the same time. We could either A. Make the presently-to-be-elected term a short one, ending in 6 months. B. Go the other way, and make it 18 months. C. Extend the current term by six months, skipping the current election. My suggestion would be C, presuming the current representative (@bookwar) is up for it. 2. While we're at a it, what do you all think about expanding the number of elected reps from two to three? With the new Executive Sponsor duty, and with everything we've got planned, I feel like more is merrier.

I've created a topic on Fedora Discussion for this ticket.

Please keep this ticket focused. Discuss there, and record votes and decisions here. Thanks!

I've created a [topic on Fedora Discussion](https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-470-two-proposals-regarding-elected-fedora-council-reps/95410) for this ticket. Please keep this ticket focused. Discuss there, and record votes and decisions here. Thanks!
Owner

Metadata Update from @jflory7:

  • Issue priority set to: Next Meeting (was: Needs Review)
  • Issue tagged with: elections, policies, ticket-vote
**Metadata Update from @jflory7**: - Issue priority set to: Next Meeting (was: Needs Review) - Issue tagged with: elections, policies, ticket-vote
Author

Based on the discussion, here's my current proposal ("option D"):

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.

Based on the discussion, here's my current proposal ("option D"): 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.

+1 (option D)

+1 (option D)

+0 (option d)

+0 (option d)
Owner

+0 Option D

+0 Option D
Owner

+0 Option D

+0 Option D

+1 Option D

+1 Option D
Owner

+1 Option D

+1 Option D

+1 Option D

+1 Option D
Owner

+1

+1
Owner

After discussing this at the Fedora Council hackfest in 2024, the council has decided:

Agreed: Move the council elections to once per year, targeting the April/May timeframe. To enact this now, we will allow for two candidates to be elected to the council in April/May 2024 for one year, and the council will have an extra member until the November/December 2024 elected members term has ended.

Council documentation relating to elections will be updated to reflect this change.

After discussing this at the Fedora Council hackfest in 2024, the council has decided: Agreed: Move the council elections to once per year, targeting the April/May timeframe. To enact this now, we will allow for two candidates to be elected to the council in April/May 2024 for one year, and the council will have an extra member until the November/December 2024 elected members term has ended. Council documentation relating to elections will be updated to reflect this change.
Owner

Metadata Update from @amoloney:

  • Issue close_status updated to: resolved
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @amoloney**: - Issue close_status updated to: resolved - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
10 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
council/tickets#470
No description provided.