-
Notifications
You must be signed in to change notification settings - Fork 4
Update README and add Steering Committee Chairperson nomination guide… #146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
wesley83
wants to merge
1
commit into
DevRel-Foundation:main
Choose a base branch
from
wesley83:wesley83-gov-update
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| # Steering Committee Chairperson Nomination and Election Guidelines | ||
|
|
||
| The Developer Relations Foundation outlines Steering Committee authority and voting rules in its [technical charter](https://github.com/DevRel-Foundation/governance/blob/main/Technical_Charter.adoc). Per the charter, the Steering Committee (SC) may elect an SC Chair to preside over SC meetings, and routine SC ballots pass with a simple 50% majority of all voting members. | ||
|
|
||
| ## Eligibility Requirements | ||
|
|
||
| 1. Must be a current voting member of the Developer Relations Foundation Steering Committee. | ||
| 2. Must be in good standing with DRF governance, including adherence to the Code of Conduct and charter obligations. | ||
| 3. Must be willing to serve as meeting chair and coordination lead for SC operations. | ||
|
|
||
| ## Nomination Process | ||
|
|
||
| 1. Any current SC voting member may nominate themselves. | ||
| 2. Any current SC voting member may nominate another eligible SC voting member. | ||
| 3. At the close of nominations, the final candidate list is shared with all SC voting members before ballots open. | ||
|
|
||
| ## Election Process | ||
|
|
||
| 1. Voting body: current SC voting members. | ||
| 2. Voting method: one-person, one-vote secret ballot or recorded vote, as determined by the SC for that cycle. | ||
| 3. Passage threshold: simple majority (50%+) of all SC voting members. | ||
| 4. If no candidate reaches the threshold in the first round, the SC should run additional round(s) with the top candidate(s) until a candidate reaches the threshold. | ||
| 5. Election results should be documented in the governance repository and announced through standard DRF communication channels. | ||
|
|
||
| ## Term and Vacancy | ||
|
|
||
| Per the charter, the SC Chair serves until resignation, term limit, or replacement by the SC. | ||
|
|
||
| If the Chair resigns or is replaced, the SC should start a new nomination and election cycle promptly to avoid extended vacancy. | ||
|
|
||
| ## Responsibilities | ||
|
|
||
| The SC Chair is expected to: | ||
| * Preside over SC meetings and keep discussions aligned to agenda and charter scope. | ||
| * Coordinate with SC members to ensure decisions, votes, and action items are tracked and closed. | ||
| * Provide budget oversight for Foundation operational priorities, in coordination with the Steering Committee and LF project support. | ||
| * Coordinate budget review and approval workflows within the Steering Committee, ensuring decisions are documented transparently. | ||
| * Support partnerships and industry outreach priorities approved by the Steering Committee. | ||
| * Support transparent communication of SC decisions to the broader DRF community. | ||
| * Help maintain continuity across SC transitions and annual planning cycles. | ||
|
|
||
| ## Partnerships and Industry Outreach | ||
|
|
||
| The SC Chair supports the Steering Committee in developing and maintaining external relationships that align with the DRF mission. This includes coordinating with SC members and LF project support to: | ||
|
|
||
| * Identify strategic partnership opportunities with organizations, communities, and ecosystem stakeholders relevant to Developer Relations. | ||
| * Prioritize outreach efforts that advance DRF working group outcomes, community growth, and adoption of DRF frameworks. | ||
| * Ensure partnership and outreach proposals are reviewed by the Steering Committee and documented with clear owners, timelines, and expected outcomes. | ||
| * Track progress of approved partnership initiatives and provide regular status updates during SC meetings. | ||
| * Promote transparent communication with the DRF community about partnership goals, activities, and outcomes. | ||
|
|
||
| ## Time Commitment and Expectations | ||
|
|
||
| The Chairperson role is an added responsibility on top of normal SC duties. Candidates should be prepared for recurring coordination work between meetings, including agenda preparation, follow-up on action items, and communication support with DRF participants and working groups. | ||
|
|
||
| Occasional periods of reduced availability due to personal or professional reasons are understandable; however, these should be the exception rather than the norm. Individuals considering this role should evaluate their capacity before accepting a nomination. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to be prescriptive about the platform used for the sake of transparency? There were discussions around using Gitvote.