github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 21:10:00 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Community TOC Nominations 2025 #13678

New Issue
Closed
opened 2025-11-02 10:50:01 -06:00 by GiteaMirror · 18 comments
GiteaMirror commented 2025-11-02 10:50:01 -06:00
Owner
Copy Link

Originally created by @jolheiser on GitHub (Nov 5, 2024).

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):

  • @delvh
  • @6543
  • @lafriks
  • @tboerger
Originally created by @jolheiser on GitHub (Nov 5, 2024). 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): - @delvh - @6543 - @lafriks - @tboerger
GiteaMirror added the type/miscellaneous label 2025-11-02 10:50:01 -06:00
GiteaMirror commented 2025-11-02 10:50:02 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Nov 5, 2024):

Nominating incumbents: @jolheiser @delvh @6543

@techknowlogick commented on GitHub (Nov 5, 2024): Nominating incumbents: @jolheiser @delvh @6543
GiteaMirror commented 2025-11-02 10:50:02 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 5, 2024):

I nominate @6543

@lafriks commented on GitHub (Nov 5, 2024): I nominate @6543
GiteaMirror commented 2025-11-02 10:50:02 -06:00
Author
Owner
Copy Link

@justusbunsi commented on GitHub (Nov 5, 2024):

Nominating @jolheiser @delvh @6543 as well

@justusbunsi commented on GitHub (Nov 5, 2024): Nominating @jolheiser @delvh @6543 as well
GiteaMirror commented 2025-11-02 10:50:03 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Nov 5, 2024):

I mean… I accept the nomination.
However, I already know that I'll have equally little time in 2025 as currently in 2024.
If that's fine for everybody, then yes, I accept the nomination.

@delvh commented on GitHub (Nov 5, 2024): I mean… I accept the nomination. However, I already know that I'll have equally little time in 2025 as currently in 2024. If that's fine for everybody, then yes, I accept the nomination.
GiteaMirror commented 2025-11-02 10:50:03 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Nov 5, 2024):

I nominate @delvh @yp05327 @lafriks

@6543 commented on GitHub (Nov 5, 2024): I nominate @delvh @yp05327 @lafriks
GiteaMirror commented 2025-11-02 10:50:03 -06:00
Author
Owner
Copy Link

@wolfogre commented on GitHub (Nov 6, 2024):

Nominating @wxiaoguang (although I know he might refuse again, I believe he deserves it), @yp05327, and @silverwind.

@wolfogre commented on GitHub (Nov 6, 2024): Nominating @wxiaoguang (although I know he might refuse again, I believe he deserves it), @yp05327, and @silverwind.
GiteaMirror commented 2025-11-02 10:50:03 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Nov 6, 2024):

Nominating wxiaoguang (although I know he might refuse again,

Yup, so no need to nominate me

@wxiaoguang commented on GitHub (Nov 6, 2024): > Nominating wxiaoguang (although I know he might refuse again, Yup, so no need to nominate me
GiteaMirror commented 2025-11-02 10:50:03 -06:00
Author
Owner
Copy Link

@puni9869 commented on GitHub (Nov 6, 2024):

I nominate @delvh @yp05327 @lafriks

@puni9869 commented on GitHub (Nov 6, 2024): I nominate @delvh @yp05327 @lafriks
GiteaMirror commented 2025-11-02 10:50:04 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Nov 7, 2024):

I nominate myself, others are already mentioned :)

@tboerger commented on GitHub (Nov 7, 2024): I nominate myself, others are already mentioned :)
GiteaMirror commented 2025-11-02 10:50:04 -06:00
Author
Owner
Copy Link

@pat-s commented on GitHub (Nov 7, 2024):

@yp05327 @tboerger @jolheiser

@pat-s commented on GitHub (Nov 7, 2024): @yp05327 @tboerger @jolheiser
GiteaMirror commented 2025-11-02 10:50:04 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Nov 20, 2024):

@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'm hoping to get voting started ASAP in December! 😁

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.

@jolheiser commented on GitHub (Nov 20, 2024): @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'm hoping to get voting started ASAP in December! 😁 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.
GiteaMirror commented 2025-11-02 10:50:05 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Nov 20, 2024):

I'm not standing for TOC, but I'm happy to continue to contribute :)

@silverwind commented on GitHub (Nov 20, 2024): I'm not standing for TOC, but I'm happy to continue to contribute :)
GiteaMirror commented 2025-11-02 10:50:05 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 21, 2024):

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.

@yp05327 commented on GitHub (Nov 21, 2024): 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.
GiteaMirror commented 2025-11-02 10:50:05 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Dec 1, 2024):

Nominees are locked in, I'll prepare the vote. 🙂

@jolheiser commented on GitHub (Dec 1, 2024): Nominees are locked in, I'll prepare the vote. :slightly_smiling_face:
GiteaMirror commented 2025-11-02 10:50:05 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Dec 1, 2024):

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 ...
... as looking back at my current elected period I did not hat as much time to dedicate to this as I personally had wished

Through I at least could spread the word at a lot of conferences ... through that is not visible in code contributions or reviews :0 :)

@6543 commented on GitHub (Dec 1, 2024): 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 ... ... as looking back at my current elected period I did not hat as much time to dedicate to this as I personally had wished Through I at least could spread the word at a lot of conferences ... through that is not visible in code contributions or reviews :0 :)
GiteaMirror commented 2025-11-02 10:50:06 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Dec 16, 2024):

@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.

  1. If you haven't voted, please do so! (You should have received an email for the vote. If not, please let me know!)
  2. Regarding https://github.com/go-gitea/gitea/pull/32820 I want to make sure everyone has a chance to re-vote if they feel the need to. Helios allows multiple votes, where only the final vote you cast is counted.

Unless something goes awry, hopefully the next ping/notification will be the election results in early January. 🙂

@jolheiser commented on GitHub (Dec 16, 2024): @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. --- 1. If you haven't voted, please do so! (You should have received an email for the vote. If not, please let me know!) 2. Regarding https://github.com/go-gitea/gitea/pull/32820 I want to make sure everyone has a chance to re-vote if they feel the need to. Helios allows multiple votes, where only the final vote you cast is counted. --- Unless something goes awry, hopefully the next ping/notification will be the election results in early January. :slightly_smiling_face:
GiteaMirror commented 2025-11-02 10:50:06 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Jan 1, 2025):

The votes have been tallied! Thank you again to everyone who voted.
https://vote.heliosvoting.org/helios/e/gitea-toc-2025

Screenshot for posterity
Screenshot 2025-01-01 090235

@jolheiser commented on GitHub (Jan 1, 2025): The votes have been tallied! Thank you again to everyone who voted. https://vote.heliosvoting.org/helios/e/gitea-toc-2025 Screenshot for posterity ![Screenshot 2025-01-01 090235](https://github.com/user-attachments/assets/7fa52589-7a20-49cc-97f3-c4d4d2252dd8)
GiteaMirror commented 2025-11-02 10:50:06 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Jan 14, 2025):

thanks for the trust and I hope I can move more code again this year + governance stuff :)

@6543 commented on GitHub (Jan 14, 2025): thanks for the trust and I hope I can move more code again this year + governance stuff :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/miscellaneous
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13678
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?