-
-
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
Voting for new owners between 2019/1/1 ~ 2019/12/31 #5572
Comments
@lunny @JonasFranzDEV @techknowlogick |
Voting for @lunny @lafriks @techknowlogick |
I am voting @lunny , @techknowlogick and @lafriks |
2 similar comments
I am voting @lunny , @techknowlogick and @lafriks And I'll be stepping down, so @lafriks and @tboerger might wanna change their votes ;) |
I'm @techknowlogick, @lafriks, @lunny |
I am voting for @lunny, @lafriks, and @JonasFranzDEV With 19 maintainers voting the current totals are as follows: So the new owners are @lafriks, @lunny, and @techknowlogick. Congrats! On a personal note, I want to thank all of you for the trust you have shared with me and wish you all a happy new year. Also, a thank you to @bkcsoft for serving two terms as an owner! |
Thanks everyone for trust, let's keep up great work :) |
Congratulations to the new owners 🥳 |
Thanks everyone for trust and happy new year! |
With the end of the year being less than 2 weeks away and as the description on our CONTRIBUTING, the Gitea community has an election every year for owners. Only maintainers could be elected, and if somebody don't want to be elected please send comment following this thread. And also, only maintainers could send their votes. Every maintainer could send 3 or less than 3 votes to other maintainers on the following comments and cannot send the votes to themself. The voting is available from now to 2018/12/31.
If you are not a maintainer of gitea, please don't send any comment here and if you do that the comment will be deleted. Speak to us on discord if you have any idea about the community election.
The text was updated successfully, but these errors were encountered: