-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 :) |
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):
Unconfirmed:
The text was updated successfully, but these errors were encountered: