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) create Projects to oversee the deliverables that have been approved. These Projects are activities that have been approved by one of the following groups: the Open Source Group, the Standards Group, the Policy Group, or the Community Group. Any output created by a Project that is intended for publication as a GSF deliverable must be approved by the WG and ratified by the Steering Committee before it can be released.
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.
Call for nominations
A call for nominations is sent out to all the project-associated WG and Project members to offer an opportunity to submit their names for consideration for a PL appointment.
If ≤ 2 three names are nominated, they are elected unopposed; no voting occurs.
If > 3 names are nominated, it will trigger a vote*.
*Recommended tool OpaVote
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.
The work and progress of the Group are appropriately communicated to the WG through regular status reports.
The PL MAY delegate tasks to the co-PLs, including chairing the Group as necessary.
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.
Create an election timeline.
Task | Date | Action | Comment |
Nomination Opens | Open date - MM-DD-YY - 16:00 PT | Email WG & Project members | Nomination period two weeks |
Nomination Closes | Closing date - MM-DD-YY - 16:00 PT | Email WG & Project members | If ≤ 2 nominations. No vote required, results circulated |
*Ballot Opens | Open date, MM-DD-YY 16:00 PT | Email GSF-All & WG with evote link | *Only required if there are more than 2 nominations. |
Ballot Closes | Closing date - MM-DD-YY - 16:00 PT | Email GSF-All & WG | Ballot results published in the GSF Newsletter and GSF-All |
Results Published | Add to Newsletter FYI OC & SC |
Nomination Process
GSF WG PM Forwards a call for nominations Email to the GSF Project members & CC’s WG members.
The nominations email GSF WG PM, with the following;
The candidate's name and company
identify if it is a self-nomination or the nomination of somebody else
Election Officers
The election officer for the PL election is the GSF WG PM.
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 close of the ballot.
Go to the Recommended tool OpaVote to vote for the nominated PL.
Select your preferred candidate, Project Lead
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 | Ben Logan | |||
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 | vacant | vacant |
STANDARDS WG | OPENSOURCE WG | POLICY WG | COMMUNITY WG |
---|
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.