-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Community TOC Nominations 2025 #32429
Comments
Nominating incumbents: @jolheiser @delvh @6543 |
I nominate @6543 |
Nominating @jolheiser @delvh @6543 as well |
I mean… I accept the nomination. |
Nominating @wxiaoguang (although I know he might refuse again, I believe he deserves it), @yp05327, and @silverwind. |
Yup, so no need to nominate me |
I nominate myself, others are already mentioned :) |
@go-gitea/maintainers we are about a week and a half away, so I'm going to ping one more time to collect nominations. There may be a few more pings/emails once voting begins, but otherwise I'll try not to spam everyone. I will be stepping down for 2025, so I am politely declining my nomination for now. @yp05327 and @silverwind if you could confirm (or deny) your nomination as well. I'll try to keep current nomination status in the OP. |
I'm not standing for TOC, but I'm happy to continue to contribute :) |
In my mind, TOC should have wide range knowledges, but I'm not sure I have enough knowledges. There are still too many things to learn. If it is not required/cared, I can accept it. |
Nominees are locked in, I'll prepare the vote. 🙂 |
I'll confirm my nomination, just note that if some other nominees have for sure dedicated time I'll step in fa-four down for them ... Through I at least could spread the word at a lot of conferences ... through that is not visible in code contributions or reviews :0 :) |
@go-gitea/maintainers sorry for another ping, but I wanted to ensure everyone is notified and I still am not 100% sure whether Helios emails make it to everyone.
Unless something goes awry, hopefully the next ping/notification will be the election results in early January. 🙂 |
It's time for the yearly election for community TOC members!
https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#technical-oversight-committee-toc
This issue is only for collecting nominations, the actual vote will be done with helios (or some other mechanism, suggestions welcome) as we did last year to ensure no one is pressured to vote a certain way.
Please put your name forward or nominate another (willing) maintainer, ideally along with a simple description of why said person would make a good candidate. We will send out a separate notification once we have the vote ready after collecting nominations.
If you are nominated by someone else, please accept/deny the nomination as well so we can constrain the ballot to people interested in running.
Anyone who hasn't confirmed their nomination by the end of November will not be placed on the ballot.
If you are not a Gitea maintainer, please refrain from commenting, we will be marking them as off-topic. Any conversation regarding this issue can happen on one of our other social platforms.
cc @go-gitea/maintainers
Current nominees (confirmed, also assuming a ❤️ means you accept):
The text was updated successfully, but these errors were encountered: