Community TOC Nominations 2024 #12153

Closed
opened 2025-11-02 10:00:18 -06:00 by GiteaMirror · 22 comments
Owner

Originally created by @jolheiser on GitHub (Dec 4, 2023).

Originally assigned to: @silverwind on GitHub.

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 votesup 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 feel free to accept/deny the nomination as well so we can constrain the ballot to people interested in running.

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 Discord, Discourse, or Matrix.

cc @go-gitea/maintainers

Originally created by @jolheiser on GitHub (Dec 4, 2023). Originally assigned to: @silverwind on GitHub. 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 votesup 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 feel free to accept/deny the nomination as well so we can constrain the ballot to people interested in running. **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 Discord, Discourse, or Matrix.** cc @go-gitea/maintainers
GiteaMirror added the type/miscellaneousskip-changelog labels 2025-11-02 10:00:18 -06:00
Author
Owner

@jolheiser commented on GitHub (Dec 4, 2023):

I would like to run again. I will admit I had far less time this year than I anticipated, however I tried to stay abreast of current issues and to communicate in chat when issues arose. I am extremely fond of this project and would love to continue being a voice for it (which I plan on doing officially or unofficially 😁).

I have been with the project since early 2019 and have accrued a fair amount of org/business/historical knowledge in that time, which I think continues to make me a good fit. I've also been able to help with various documentation and CI issues, along with a smattering of bug fixes.


If I could hijack my own post to nominate someone as well, I think @delvh would be a fantastic choice. I think he has touched nearly every PR in the last year or so and focuses on making our processes better constantly.

@jolheiser commented on GitHub (Dec 4, 2023): I would like to run again. I will admit I had far less time this year than I anticipated, however I tried to stay abreast of current issues and to communicate in chat when issues arose. I am extremely fond of this project and would love to continue being a voice for it (which I plan on doing officially or unofficially :grin:). I have been with the project since early 2019 and have accrued a fair amount of org/business/historical knowledge in that time, which I think continues to make me a good fit. I've also been able to help with various documentation and CI issues, along with a smattering of bug fixes. ----- If I could hijack my own post to nominate someone as well, I think @delvh would be a fantastic choice. I think he has touched nearly every PR in the last year or so and focuses on making our processes better constantly.
Author
Owner

@denyskon commented on GitHub (Dec 4, 2023):

Thanks @jolheiser for organising this and for serving as a TOC member in 2023.

I'd like to nominate the following people:

  • @delvh - through managing the last couple releases and doing lots of other management tasks like issue moderation they have proven the willingness to take a huge responsibility for the project
  • @wxiaoguang - through always ensuring a great code quality and never acting frivolous when it comes to reviews they have shown to me just the right attitude to make decisions which result in a positive technical impact for the project
  • @silverwind - here basically the same reasons as with my previous nominee, from my point of view they are always ensuring that the project is moving in the right direction

I want to thank every current TOC member for their hard work - especially with a demand for PR reviews larger than ever, big changes starting with huge functionality improvements and ending with everything related to Gitea Ltd and all the other challenges which appeared during this year, all of you have been doing a great job managing the project.
I'd like for these nomination choices not to be seen as any sort of criticism towards the current TOC members. I am only involved in Gitea for a few months now and the maintainers nominated by me are those who had the biggest impact on my contributions and my view of the project during these months :)

@denyskon commented on GitHub (Dec 4, 2023): Thanks @jolheiser for organising this and for serving as a TOC member in 2023. I'd like to nominate the following people: - @delvh - through managing the last couple releases and doing lots of other management tasks like issue moderation they have proven the willingness to take a huge responsibility for the project - @wxiaoguang - through always ensuring a great code quality and never acting frivolous when it comes to reviews they have shown to me just the right attitude to make decisions which result in a positive technical impact for the project - @silverwind - here basically the same reasons as with my previous nominee, from my point of view they are always ensuring that the project is moving in the right direction I want to thank every current TOC member for their hard work - especially with a demand for PR reviews larger than ever, big changes starting with huge functionality improvements and ending with everything related to Gitea Ltd and all the other challenges which appeared during this year, all of you have been doing a great job managing the project. I'd like for these nomination choices not to be seen as any sort of criticism towards the current TOC members. I am only involved in Gitea for a few months now and the maintainers nominated by me are those who had the biggest impact on my contributions and my view of the project during these months :)
Author
Owner

@wxiaoguang commented on GitHub (Dec 5, 2023):

Thank you for nominating 🙏, while I'd like to abstain (I also abstained last year) and leave the chance to others 😄

@wxiaoguang commented on GitHub (Dec 5, 2023): Thank you for nominating 🙏, while I'd like to abstain (I also abstained last year) and leave the chance to others 😄
Author
Owner

@denyskon commented on GitHub (Dec 5, 2023):

@wxiaoguang Do you mean that you don't want to accept the nomination or that you won't nominate anybody/vote?

@denyskon commented on GitHub (Dec 5, 2023): @wxiaoguang Do you mean that you don't want to accept the nomination or that you won't nominate anybody/vote?
Author
Owner

@wxiaoguang commented on GitHub (Dec 5, 2023):

Do you mean that you don't want to accept the nomination or that you won't nominate anybody/vote?

Sorry for my unclear comment. I meant "not accept the nomination for me". (ps: I won't nominate or vote either because I don't know how TOC work)

@wxiaoguang commented on GitHub (Dec 5, 2023): > Do you mean that you don't want to accept the nomination or that you won't nominate anybody/vote? Sorry for my unclear comment. I meant "not accept the nomination for me". (ps: I won't nominate or vote either because I don't know how TOC work)
Author
Owner

@6543 commented on GitHub (Dec 6, 2023):

There are 6 members in the TOC, 3 decided by the gitea company and 3 elected as with in here. gitea company members can not be elected.

They do administrative tasks, promote gitea ... and are the last to decide on hard questions/decissions.

@6543 commented on GitHub (Dec 6, 2023): There are 6 members in the TOC, 3 decided by the gitea company and 3 elected as with in here. gitea company members can not be elected. They do administrative tasks, promote gitea ... and are the last to decide on hard questions/decissions.
Author
Owner

@6543 commented on GitHub (Dec 6, 2023):

As jolheiser wrote, i can just copy paste ;) that more or less.

If you have future questions about the TOC just ask on discord/matrix and ping us (people are bussy ;) )

@6543 commented on GitHub (Dec 6, 2023): As **jolheiser** wrote, i can just copy paste ;) that more or less. If you have future questions about the TOC just ask on discord/matrix and ping **us** (people are bussy ;) )
Author
Owner

@puni9869 commented on GitHub (Dec 7, 2023):

Thanks @jolheiser for organising this and for serving as a TOC member in 2023.

I'd like to nominate the following people:

  • @delvh - through managing the last couple releases and doing lots of other management tasks like issue moderation they have proven the willingness to take a huge responsibility for the project
  • @wxiaoguang - through always ensuring a great code quality and never acting frivolous when it comes to reviews they have shown to me just the right attitude to make decisions which result in a positive technical impact for the project
  • @silverwind - here basically the same reasons as with my previous nominee, from my point of view they are always ensuring that the project is moving in the right direction

I want to thank every current TOC member for their hard work - especially with a demand for PR reviews larger than ever, big changes starting with huge functionality improvements and ending with everything related to Gitea Ltd and all the other challenges which appeared during this year, all of you have been doing a great job managing the project. I'd like for these nomination choices not to be seen as any sort of criticism towards the current TOC members. I am only involved in Gitea for a few months now and the maintainers nominated by me are those who had the biggest impact on my contributions and my view of the project during these months :)

Same for me.

@puni9869 commented on GitHub (Dec 7, 2023): > Thanks @jolheiser for organising this and for serving as a TOC member in 2023. > > I'd like to nominate the following people: > > * @delvh - through managing the last couple releases and doing lots of other management tasks like issue moderation they have proven the willingness to take a huge responsibility for the project > * @wxiaoguang - through always ensuring a great code quality and never acting frivolous when it comes to reviews they have shown to me just the right attitude to make decisions which result in a positive technical impact for the project > * @silverwind - here basically the same reasons as with my previous nominee, from my point of view they are always ensuring that the project is moving in the right direction > > I want to thank every current TOC member for their hard work - especially with a demand for PR reviews larger than ever, big changes starting with huge functionality improvements and ending with everything related to Gitea Ltd and all the other challenges which appeared during this year, all of you have been doing a great job managing the project. I'd like for these nomination choices not to be seen as any sort of criticism towards the current TOC members. I am only involved in Gitea for a few months now and the maintainers nominated by me are those who had the biggest impact on my contributions and my view of the project during these months :) Same for me.
Author
Owner

@delvh commented on GitHub (Dec 13, 2023):

I have no idea yet how much time I'll have next year, but yes, I accept the nomination.

@delvh commented on GitHub (Dec 13, 2023): I have no idea yet how much time I'll have next year, but yes, I accept the nomination.
Author
Owner

@delvh commented on GitHub (Dec 16, 2023):

Well… if no one else applies/gets nominated, then we at least have an easy choice since there are only three candidates for three seats at the moment 😆

@delvh commented on GitHub (Dec 16, 2023): Well… if no one else applies/gets nominated, then we at least have an easy choice since there are only three candidates for three seats at the moment :laughing:
Author
Owner

@jolheiser commented on GitHub (Dec 17, 2023):

@6543 was your comment meant to say you also are applying?

If so we have myself, 6543, delvh, and then if @silverwind wishes to confirm their nomination.

@jolheiser commented on GitHub (Dec 17, 2023): @6543 was your comment meant to say you also are applying? If so we have myself, 6543, delvh, and then if @silverwind wishes to confirm their nomination.
Author
Owner

@lunny commented on GitHub (Dec 17, 2023):

I nominate @KN4CK3R . I think he has the ability to resolve complext issues according to his contributions, especially for Packages and Storages.

@lunny commented on GitHub (Dec 17, 2023): I nominate @KN4CK3R . I think he has the ability to resolve complext issues according to his contributions, especially for Packages and Storages.
Author
Owner

@KN4CK3R commented on GitHub (Dec 18, 2023):

Thank you for the nomination, accepting 👍

@KN4CK3R commented on GitHub (Dec 18, 2023): Thank you for the nomination, accepting 👍
Author
Owner

@6543 commented on GitHub (Dec 22, 2023):

I would nominate @lafriks , @jolheiser and @silverwind

@6543 commented on GitHub (Dec 22, 2023): I would nominate @lafriks , @jolheiser and @silverwind
Author
Owner

@pat-s commented on GitHub (Dec 23, 2023):

@delvh @silverwind @KN4CK3R

@pat-s commented on GitHub (Dec 23, 2023): @delvh @silverwind @KN4CK3R
Author
Owner

@jolheiser commented on GitHub (Jan 3, 2024):

A vote has been started and all maintainers should have received an email with instructions to cast a ballot.

If you did not, please let me know here, via email, or on Discord.

/cc @go-gitea/maintainers

@jolheiser commented on GitHub (Jan 3, 2024): A vote has been started and all maintainers should have received an email with instructions to cast a ballot. If you did not, please let me know here, via email, or on Discord. /cc @go-gitea/maintainers
Author
Owner

@kerwin612 commented on GitHub (Jan 4, 2024):

I would nominate @wxiaoguang , @6543 and @silverwind

@kerwin612 commented on GitHub (Jan 4, 2024): I would nominate @wxiaoguang , @6543 and @silverwind
Author
Owner

@denyskon commented on GitHub (Jan 18, 2024):

@go-gitea/maintainers

Another reminder that voting is still open and less than 50% have already voted. We should have a participation of at least 50% for the results of the election to be considered legitimate I think.... so please vote if you didn't already!

@denyskon commented on GitHub (Jan 18, 2024): @go-gitea/maintainers Another reminder that voting is still open and less than 50% have already voted. We should have a participation of at least 50% for the results of the election to be considered legitimate I think.... so please vote if you didn't already!
Author
Owner

@tboerger commented on GitHub (Jan 20, 2024):

I vote for @6543, @lafriks and @silverwind

@tboerger commented on GitHub (Jan 20, 2024): I vote for @6543, @lafriks and @silverwind
Author
Owner

@6543 commented on GitHub (Jan 20, 2024):

Thanks for the nomination.

But the vote is already running: https://vote.heliosvoting.org/helios/elections/cf112912-a5c1-11ee-b29b-026c14065f7c/voters/list

@6543 commented on GitHub (Jan 20, 2024): Thanks for the nomination. But the vote is already running: https://vote.heliosvoting.org/helios/elections/cf112912-a5c1-11ee-b29b-026c14065f7c/voters/list
Author
Owner

@jolheiser commented on GitHub (Jan 22, 2024):

The election is closed, thanks to everyone who voted!
https://vote.heliosvoting.org/helios/elections/cf112912-a5c1-11ee-b29b-026c14065f7c/view

Screenshot as well in case the URL stops working:
election results

@jolheiser commented on GitHub (Jan 22, 2024): The election is closed, thanks to everyone who voted! https://vote.heliosvoting.org/helios/elections/cf112912-a5c1-11ee-b29b-026c14065f7c/view Screenshot as well in case the URL stops working: ![election results](https://github.com/go-gitea/gitea/assets/42128690/645d67e4-af8b-49bb-b720-87bd288c8798)
Author
Owner

@6543 commented on GitHub (Jan 27, 2024):

@silverwind do you accept it?

@6543 commented on GitHub (Jan 27, 2024): @silverwind do you accept it?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12153