The voting period has now opened for the Fedora Linux 40 elections cycle. Please read the candidate interviews and cast your votes in our Elections App. Visit our Voting Guide to learn how our voting system works, and voting closes at 23:59:59 UTC on May 30th.
Fedora Mindshare Committee
Fedora Mindshare has one seat open. Below is the candidate that will be elected at the end of the voting period.
Fedora Council
The Fedora Council has two seats open. Below are the candidates eligible for election.
Fedora Engineering Steering Committee (FESCo)
The Fedora Engineering Steering Committee (FESCo) has four seats open. Below are the candidates eligible for election.
EPEL Steering Committee
The EPEL Steering Committee has four seats open. Below are the candidates eligible for election.
Seems like there are a couple issues with the voting setup.
The former can be trivially fixed, but the latter may not be fixable without re-starting the election. (It might be possible to change it, too, but I don’t know how that would effect the final tallies)
I can’t claim the voting badge, but already voted
there is some bug shows none none
I can change the max range to 6, my thought process for setting it at 4 was that there was only 4 open seats to vote for. It most likely won’t have a huge impact as I know some voters from the f39 cycle didn’t use the ‘range voting’ mechanism anyway. I can change, or leave it as is for a more ‘pure’ result.
Thanks for the fyi on the badges link, will sort that out asap.
The username is definitely a bug and I don’t know if it’s in the app itself or an issue with FAS. This is my view in the app itself. If anyone has any suggestions I’m all ears, and will open a ticket with infra in the meantime.
I might need to restart the EPEL election though because of the bug
It’s due to Troy not having filled in first and last name in FAS as already pointed out on Matrix and the mailing list. Not sure if it will update, though, should he decide to fill it in now.
So this has been nothing short of chaos with the Elections this morning
Sincerest apologies everyone for the confusion. It appears:
This has been quite the Monday and I cant apologise enough for the confusion and thank you all enough for your patience while I try to resolve the issues.
Will keep you updated here and on the devel-list too.
That means a new claim link, assuming the issue with that is fixed in time, will need to be created. For all the links I created so far, I set the expiration date to May 31 00:05. That will need to be adjusted to whatever the new deadline will be.
But first we need working links… (there’s progress on that, it seems
)
All the things should now be fixed!
After much troubleshooting and some wonderful folks working with me to help resolve the issues that littered the elections today, I am pleased to say all issues have been resolved, or at least I live in hope that they are!
If you have voted in either or both FESCo and EPEL elections today, please recast your votes in the new ballot boxes as the previous ones are corrupted.
If you have voted in Council and/or Mindshare, and did not have a claim link for your badge, please revisit your vote as the link has been updated and you should be able to access it. If you can’t, email me directly and I will manually award this to you (I cant see who voted so I can’t do this without knowing who to send it to).
Voting will close at 23:59:59 UTC on 31st May 2024, an extra day has been added and the schedule will be updated accordingly.
Thank you again to @Sandro @Miro Hrončok @Michal Konecny @Aurelien Bompard & @Tomas Hrcka for your help, and to everyone for your patience and understanding while I sorted out the chaos that was this election voting opening day!
Please let me know if you find any other anomalies and after a short sob, I will fix them
Kindest regards,
Aoife
When I click the claim link after voting, I got the below error:
@ersen, I think it’s sufficient to report the issue in one place. It doesn’t make people move faster if the same issue is reported over and over again. It’s rather the opposite, it slows things down.
Since I already left a reaction on the GitHub ticket, I won’t repeat myself here.