Project Lead (PL) Elections
The elected Project Leads are responsible for leading our approved projects, which includes maintaining governance, defining strategy, and upholding our Code of Conduct. They also oversee the development of projects and mentor team members. Each project can have up to three co-project lead appointments available. Both Steering and General members are eligible to become Project Leads.
Project Overview
The Working Groups (WGs) approve Projects to oversee the deliverables that have been approved. Any output created by a Project intended for publication as a GSF deliverable must be approved by the WG and ratified by the Steering Committee before release.
Term
Once a project is approved, the submitter will be installed as the initial Project Lead. Additional project leads can be nominated and elected by their project peers. A Project Lead's term lasts for two years, but it is dependent on the organization's continued membership. If a Project Lead(s) resigns before completing their term, an election process will be triggered to find a suitable replacement.
Project Lead Responsibilities
- The PL has overall responsibility for the management of a project.
- PLs shall:
- Maintain strict impartiality and act in the foundation's interest in performing their tasks.
- Ensure the technical activities of the Group are progressed promptly following the processes and procedures of GSF.
- Organize and run the meetings following the processes and practices of the GSF.
- Ensure the work and progress of the Project are appropriately communicated to the WG.
- Facilitate discussion during the meeting, encouraging all members to participate in decision-making.
Project Lead Role Considerations:
- This role requires 2-3 hours per week, including chairing meetings, preparation time, and offline communications.
- PLs must lead empathetically and create a welcoming space for technical and non-technical contributors.
- PLs represent the GSF, so they must ensure benefits are shared among all.
PL Support
Elected PLs will receive a wide range of support in fulfilling their duties from their Group GSF Ops team, including their own Project Manager.
Call for Lead Nominations
- Forward an email to Project & cc: WG members, inviting members to submit their names for chair consideration.
- Existing chairs are eligible to submit their names for consideration to run for a second term.
- Details are additionally circulated in the GSF Newsletter
- Member nominations are submitted to the GSF WG PM in reply to the circulated email.
- GSF members can self-nominate.
- Include the following information.
- The candidate's name and company
- identify if it is a self-nomination or the nomination of somebody else
- NOTE: The use of GSF email lists shall not be permitted for any campaign purposes by candidates.
Results
- If ≤ 2 names are submitted, they are elected unopposed after the Election Officers have reviewed the nominations. No voting occurs.
- If ≥ 3 names are submitted, it will trigger a *vote, or the project can approve to have 3 Project Leads.
- Recommended tool OpaVote
Voting (Only required IF there are > 3 Nomination)
Each member organization is entitled to one vote at the Green Software Foundation. The official primary representative, or alternate if the primary is unavailable, will vote on their organisation's behalf. However, before the vote is cast, a popular vote will be conducted to determine the majority choice of the WG. The member organization will then be informed of the popular vote and can either cast their ballot in favour or vote independently.
Voting instructions
- Any individual from a Steering or General level is entitled to vote.
- Members are entitled to change their vote as often as they wish until the ballot closes.
- Recommended tool OpaVote
Create an election timeline.
Task | Date | Action | Comment |
Nomination Opens | Open date - MM-DD-YY - 16:00 PT | Email WG & Project | • Nomination period 2 weeks
• Details circulated in Newsletter |
Nomination Closes | Closing date - MM-DD-YY - 16:00 PT | Email WG & Project | |
a. ≤ 2 three names nominations - Nominations ratified by Election Officers, prior to publishing Results.
b. 3 nominations or more, trigger an evote | |||
Ballot Opens | Open date, MM-DD-YY 16:00 PT | Email WG & Project with evote link | Only required if there are more than 2 nominations. - Note:
• Project members can approve to have 3 Project Leads. |
Ballot Closes | Closing date - MM-DD-YY - 16:00 PT | Email WG & Project | Ballot results published in the GSF Newsletter and GSF-All |
Evote results ratified by Election Officers, prior to publishing Results | |||
Results Published | Add to Newsletter
FYI OC & SC |
Election Officers
The election officers for the WG election are GSF WG Project Managers.
Current Project Leads
The following members are in post until December 2025;
Project | Project Lead (Elected date) | Project Lead (Elected date) | Project Lead (Elected date) | Comments |
SCER | Chris Xie (Initial Project Lead) | Marco Valtas (Initial Project Lead) | vacant | |
Real-Time | Adrian Cockcroft. (Initial Project Lead) | Pindy Bhullar (Initial Project Lead) | vacant | |
Toss | Pindy Bhullar (Initial Project Lead) | vacant | vacant | |
SCI | Henry Richardson (Initial Project Lead) | Abhishek Gupta (Initial Project Lead) | vacant | |
Carbon Aware SDK | Vaughan Knight (Initial Project Lead) | Szymon Duchniewicz | ||
Awesome Green Software | Dr Ahmad Antar (4th April) | Dr Abid Ali (4th April) | ||
Carbon CI | Fergus Kidd
(Initial Project Lead) | |||
Impact Framework | Naveen Balani
(Initial Project Lead) | Srinivasan Rakhunathan
(Initial Project Lead) | ||
Students | Thomas Lewis
(Initial Project Lead) | vacant | vacant | |
Patterns | vacant | vacant | vacant | |
Principles | Sarah Hsu (Initial Project Lead) | vacant | vacant | |
Maturity Matrix | Anne Currie (Initial Project Lead) | vacant | vacant | |
Green Software Playbook | Mohammad Haque
(Initial Project Lead) | vacant | vacant |