2022 Election Announcements #1173
Comments
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you! |
|
We invite everyone tagged here to vote between now and 20 Oct 2022 23:59 UTC using this link: https://vote.heliosvoting.org/helios/elections/76558134-3384-11ed-8688-02871af94755/view Please log in using your GitHub account and let us know if you have any troubles. If you believe you have the right to vote but haven't being tagged on this issue, please fill the registration form: https://forms.gle/mEDWyn6G7iCe4bvJ7 |
|
I have heard from different users that they are having trouble voting, and I believe this is happening because their usernames use a mixed case, where our data source (devstats) only provides usernames in lower case. If you are attempting to vote and receive a "permission denied" message from Helios and your username has a mixed case, please ping me directly on Slack with your username, and I'll fix it right away. I'm sorry for this inconvenience (and for this new broadcast, I promise I'm trying to keep this at a minimum). |
|
@jpkrohling it may be worth explaining the voting steps with pictures somewhere. It took me a while to understand how to do it. I could not figure out how to login for example and then almost failed to click the last "Cast Ballot" button. And this is my 3rd Otel vote. The first time voters may have even more trouble. |
|
@devrimdemiroz, @mhausenblas, @RichiH, @felixge, @ramthi, @musingvirtual, your exemption requests have been approved, you should now be able to vote on Helios. @vjsamuel, @vmarchaud, @ymotongpoo, @hcoona, @rauno56, @vincentfree, @pmm-sumo, @alolita, you also filled out the form, but you were eligible already. Please let me know if you have trouble voting. |
|
Thanks for clarifying @jpkrohling As Tigran mentioned, the instructions were not clear initially :-) |
|
This is a friendly reminder to cast your vote for the OpenTelemetry Governance Committee Election 2022. If you are listed in one of the first comments on this issue, you are eligible for voting. IMPORTANT: remember to click "cast your vote" in the final step, or your ballot will not be received. If you have trouble voting, let me (@jpkrohling) know in whatever media you can find me, although I prefer to be contacted via CNCF Slack for this purpose. When doing so, please inform your GitHub handle. |
|
This is a final reminder to cast your vote for the OpenTelemetry Governance Committee Election 2022. If you are listed in one of the first comments on this issue, you are eligible for voting. IMPORTANT: remember to click "cast your vote" in the final step, or your ballot will not be received. Please, check the following screenshots, showing how to successfully cast your ballot. In the second step, make sure to select your candidates. If you have trouble voting, let me (@jpkrohling) know in whatever media you can find me, although I prefer to be contacted via CNCF Slack for this purpose. When doing so, please inform your GitHub handle.
|
|
The OpenTelemetry project is proud to announce the winners of the 2022 OpenTelemetry Governance Committee (GC) election! Before we get into the results, I’d like to share some statistics about the election! This year, 513 project members were eligible to vote. Of those, 219 cast ballots, for a participation rate of nearly 43%! For comparison, the 2021 election saw 169 ballots cast with 386 eligible voters. Participation was roughly flat year-over-year, and we’re thrilled that we’ve welcomed so many new project members and maintained a high participation rate. With that out of the way, please join me in congratulating @alolita, @dyladan, and @mtwo on their re-election! They will be joined by long-time contributor and maintainer of OpenTelemetry Java Instrumentation @trask! All will serve a two-year term. We’d like to thank everyone who participated – candidates, voters, and the election organizers – for their efforts. You can find the full results of the election here. (originally posted here: https://opentelemetry.io/blog/2022/gc-election-results/) |
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
|
We invite the people mentioned in this comment to vote in the OpenTelemetry Governance Committee, as they have provided more than 20 contributions to the project over the last year via GitHub. Your contributions were comments, code reviews, pull requests, among others. Thank you!
|
This issue will contain election announcements and the complete list of eligible voters. Subscribe to this issue if you wish to be notified of changes. Contact @open-telemetry/otel-elections if you have questions.
If you are not automatically detected as a member of standing and believe your contributions should make you eligible to vote, you may request an exemption by filling out a registration form.
People mentioned in this issue have been detected as members of standing, as defined in the project's governance charter.
You can find more information about the voting process here
Due to the potential notification storm that this issue may cause, the conversation is locked. If you have concerns, please contact the group @open-telemetry/otel-elections, or any of the members (@jpkrohling or @bogdandrutu) individually. They are also available on the CNCF Slack.
The text was updated successfully, but these errors were encountered: