-
Notifications
You must be signed in to change notification settings - Fork 228
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
🗳 2023 Technical Steering Committee (TSC) Elections 🗳 #1175
Comments
cc @graphql/tsc |
My term is expiring this year, and since my day-to-day work hasn't involved GraphQL as of late, I'm not planning on renominating myself so that my seat can open up for a new TSC member. The community and the TSC are clearly in good hands, and I'm excited to see how GraphQL continues to grow and evolve in the years ahead! |
I will not be renominating myself so that someone else can have a chance to work with this amazing group and drive the GraphQL ecosystem forward. However, I plan on staying an active member of the working group. |
Similarly I will not be renominating myself. Second Dan's sentiment that this is clearly in good hands and it's exciting to see the GraphQL continue to grow, expand, and mature!
…On Mon, Nov 28, 2022 at 3:04 PM, Robert Zhu < ***@***.*** > wrote:
I will not be renominating myself so that someone else can have a chance
to work with this amazing group and drive the GraphQL ecosystem forward.
However, I plan on staying an active member of the working group.
—
Reply to this email directly, view it on GitHub (
#1175 (comment)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AG3IK6JWR6YEWX2NU5NE5T3WKUF4NANCNFSM6AAAAAASCRS7DE
).
You are receiving this because you are on a team that was mentioned. Message
ID: <graphql/graphql-wg/issues/1175/1329691969 @ github. com>
|
Thank you to everyone who nominated themselves for a TSC role, and for our now emeritus TSC members for creating space for a host of new members. We had ten excellent nominees, and last week the remaining TSC members voted by way of preference ordering (using Meek STV) Next elected members are (in alpha order)... 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 🥁 Andi Marek @andimarek 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 Huge congratulations to this group, and thank you for helping us keep the GraphQL project organized and effective! |
I hope you're not tired of elections, because it's time to run our own.
Please see the 2022 TSC Elections process for context from last year.
While our charter calls for Elections concluding by the end of the year, since we're opening nominations late, we'll shift the elections schedule by one month to allow for more time for nominations (and extend existing terms by the same).
The GraphQL technical project is governed by our technical steering committee (TSC).
The TSC was initially seeded in Nov 2020 with ten individuals plus the exec director (myself). Elections are held for five seats per year with each elected member to serve a 2 year term.
TSC election process overview:
Please read the complete rules for this elections process. However here is a brief overview:
Upcoming dates:
Expiring TSC member terms:
Members voting in this election:
TSC responsibilities overview:
Please read the complete TSC scope. However here is a brief overview of expectations:
Note: Working group meetings remain open to all who wish to join and contribute. The RFC process by which GraphQL evolves uses a consensus model, and TSC rarely intervene with this model. Our goal remains to maintain open contribution.
Important links:
I'm happy to answer any questions within this issue!
The text was updated successfully, but these errors were encountered: