Due to some procedural problems with the current election for the Board of the Python Software Foundation, the Foundation has taken some steps to make sure that the elections are freely open for nominations and that there are no conflicts of interest. Specifically, today the board adopted the following resolutions:
RESOLVED, due to procedural deficiencies, the Board Election ballots issued on May 1st (AOE)/May 2nd (UTC) be deemed null and void.
RESOLVED, that David Mertz be removed as election administrator, and that Ian Cordasco be appointed as election administrator.
David has been the election adminstrator for quite a while, and designed the "e-vote" system that we use along with Massimo DePierro. He has put in a lot of time and effort, and we thank him for it. David in particular volunteered for a complex voting administration task that needed to be handled as the PSF expanded internationally beyond a primarily US-based membership that could previously realistically vote (in person, or by proxy) at physical meetings held annually at PyCon
US.
Without David's efforts as Election Administrator over that time, it would not have been feasible to expand the membership as we have, including the conversion to an open membership model in the 2014 update to the PSF bylaws.
For anyone who has received a ballot already, or has received a ballot reminder, please ignore it. We will be canceling the election as quickly as possible.
We also wanted to make sure that the procedure for upcoming board elections was clear, particularly with regard to the timelines for nominations and voting eligibility. To address that, we also adopted the following resolution concerning the timing of future votes for the board. For those who aren't familiar with the term "AOE", it means "Anywhere on Earth." As long as it is not before the end of the day in your local timezone, you are ok.
RESOLVED, that the Python Software Foundation adopt the follow procedure for Board elections:
- Day 1: There is announcement of an upcoming board election via public announcement and email to existing voting members.
- Day 10 (AOE): Nominations and voting eligibility closes for the upcoming board election. The list of voting members is updated.
- Day 14-15: Ballots are sent out to voting members.
- Day 25 (AOE): Election closes.
We also are starting a new election using this procedure, so the timeline for the election is as follows:
- May 5: Announcement of a new election via this blogpost and an email to the voting members.
- May 15 (AOE): Nominations and voting eligibility closes for the upcoming board election. The list of voting members is updated.
- May 19-20: Ballots are sent out to voting members.
- May 30 (AOE): Election closes.
This means that in an effort to be inclusive, the nominations will again be open for anyone until May 15 AOE. If you missed the opportunity to nominate for the 2015 Python Software Foundation Board, you will have that chance.
Thanks,
Van Lindberg
PSF Chair
RESOLVED, due to procedural deficiencies, the Board Election ballots issued on May 1st (AOE)/May 2nd (UTC) be deemed null and void.
RESOLVED, that David Mertz be removed as election administrator, and that Ian Cordasco be appointed as election administrator.
David has been the election adminstrator for quite a while, and designed the "e-vote" system that we use along with Massimo DePierro. He has put in a lot of time and effort, and we thank him for it. David in particular volunteered for a complex voting administration task that needed to be handled as the PSF expanded internationally beyond a primarily US-based membership that could previously realistically vote (in person, or by proxy) at physical meetings held annually at PyCon
US.
Without David's efforts as Election Administrator over that time, it would not have been feasible to expand the membership as we have, including the conversion to an open membership model in the 2014 update to the PSF bylaws.
For anyone who has received a ballot already, or has received a ballot reminder, please ignore it. We will be canceling the election as quickly as possible.
We also wanted to make sure that the procedure for upcoming board elections was clear, particularly with regard to the timelines for nominations and voting eligibility. To address that, we also adopted the following resolution concerning the timing of future votes for the board. For those who aren't familiar with the term "AOE", it means "Anywhere on Earth." As long as it is not before the end of the day in your local timezone, you are ok.
RESOLVED, that the Python Software Foundation adopt the follow procedure for Board elections:
- Day 1: There is announcement of an upcoming board election via public announcement and email to existing voting members.
- Day 10 (AOE): Nominations and voting eligibility closes for the upcoming board election. The list of voting members is updated.
- Day 14-15: Ballots are sent out to voting members.
- Day 25 (AOE): Election closes.
We also are starting a new election using this procedure, so the timeline for the election is as follows:
- May 5: Announcement of a new election via this blogpost and an email to the voting members.
- May 15 (AOE): Nominations and voting eligibility closes for the upcoming board election. The list of voting members is updated.
- May 19-20: Ballots are sent out to voting members.
- May 30 (AOE): Election closes.
This means that in an effort to be inclusive, the nominations will again be open for anyone until May 15 AOE. If you missed the opportunity to nominate for the 2015 Python Software Foundation Board, you will have that chance.
Thanks,
Van Lindberg
PSF Chair
Comments