Commit Graph

7 Commits

Author SHA1 Message Date
3233e33e27 chore: update maintainers list - add ChristopherHX (#937)
All checks were successful
changelog / changelog (push) Successful in 8s
check-and-test / check-and-test (push) Successful in 43s
As discussed in #931 Reviewed-on: #937 Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> Reviewed-by: Markus Pesch <volker.raschek@noreply.gitea.com> Co-authored-by: ChristopherHX <christopher.homberger@web.de> Co-committed-by: ChristopherHX <christopher.homberger@web.de>
2025-08-21 08:50:09 +00:00
d9e181df93 chore: update maintainers list - volker.raschek (#933)
All checks were successful
changelog / changelog (push) Successful in 9s
check-and-test / check-and-test (push) Successful in 46s
Reviewed-on: #933 Reviewed-by: delvh <dev.lh@web.de> Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: Markus Pesch <markus.pesch@cryptic.systems> Co-committed-by: Markus Pesch <markus.pesch@cryptic.systems>
2025-08-20 16:32:23 +00:00
603f8e68a7 chore: update maintainers list - rossigee (#932)
All checks were successful
changelog / changelog (push) Successful in 9s
check-and-test / check-and-test (push) Successful in 41s
Co-authored-by: Ross Golder <ross@golder.org> Co-committed-by: Ross Golder <ross@golder.org>
2025-08-20 11:19:17 +00:00
9206b34af3 docs: remove pat-s from maintainers (#918)
All checks were successful
changelog / changelog (push) Successful in 9s
check-and-test / check-and-test (push) Successful in 45s
generate-chart / generate-chart-publish (push) Successful in 1m8s
generate-chart / release-gitea (push) Successful in 10s
#916 After many years of maintaining this chart alongside @justusbunsi, I am also stepping down as a maintainer. In the following, I want to inform users about the reasons. I am on an independent journey since ~ 1 year, which brought many new challenges and responsibilities. Since then I have created many devops-related assets (charts, Ansible role, images) which I am now curating as part of my professional work. Besides, I have also continued with all my FOSS-related efforts. This has summed up to ~ 20-30 projects for which I am either in a primary or secondary maintainer role. While I have a lot of fun in this, I need to ensure to not go beyond my limits and focus on the ones which I also use in my daily dev & professional life. Gitea isn't among these anymore since some time, which brings me to the second part of why I am stepping down: After thinking about it for a long time and being torn between worlds, I've decided to go with Forgejo instead of Gitea for most instances I am running/maintaining. Since then, I have used the Gitea helm chart to deploy these. This has worked out great and without issues and will likely continue to do so for the foreseeable future. However, it lately started to feel "wrong", i.e. to continue using the Gitea chart for Forgejo deployments, especially after both projects have substantially diverged some time ago already and a Forgejo Helm Chart exists since some time. Also, I had the feeling of not being able to "commit" to one of the projects fully, being involved in both. After launching [CodeFloe](https://codefloe.com) a few weeks ago, a public Forgejo instance, I came to the conclusion to step down as a maintainer and focus on the software that I use daily. And as I like be fully transparent: I don't wanna hold back on the fact that I was also missing the community spirit from "the old days" quite a bit lately, both in the Discord server and the discussions in the chart. The ratio of low-quality requests in the Chart increased a lot over the last ~ 1.5 years, while at the same time the average response times of Gitea core member increased to weeks. I hope the Gitea community can turn this around again and create a welcoming place to which its fun to contribute to in one's spare time. I enjoyed it for the most part and want to thank everyone who supported me during this time, for the general trust in Chart-related decisions, and the opportunity to personally improve on Helm chart management in general. Reviewed-on: #918 Co-authored-by: pat-s <patrick.schratz@gmail.com> Co-committed-by: pat-s <patrick.schratz@gmail.com>
2025-08-04 19:06:39 +00:00
203a282e93 docs: step down as maintainer (#917)
All checks were successful
changelog / changelog (push) Successful in 9s
check-and-test / check-and-test (push) Successful in 44s
This is a direct follow-up to #916. Over the past months I took an unofficial break. During this time I realized that I don't have the necessary energy and spare time to maintain the Helm Chart long-term - in a way I would like to. Before that break I had ups where I was hyper-focused on the chart, and downs where everything was too much after work. I never found a sweat spot between both. This is not good for me. It is therefore with a heavy heart that I am stepping down as a maintainer. Signed-off-by: justusbunsi <sk.bunsenbrenner@gmail.com> Reviewed-on: #917 Co-authored-by: justusbunsi <sk.bunsenbrenner@gmail.com> Co-committed-by: justusbunsi <sk.bunsenbrenner@gmail.com>
2025-08-04 18:33:25 +00:00
da2d169d65 chore: refine CODEOWNERS to skip request triggers for CI yaml changes
Some checks failed
changelog / changelog (push) Has been cancelled
check-and-test / check-and-test (push) Has been cancelled
2025-05-10 15:55:55 +02:00
42937062d9 Add codeowners file (#642)
All checks were successful
check-and-test / check-and-test (push) Successful in 35s
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Reviewed-on: gitea/helm-chart#642 Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.com> Co-authored-by: pat-s <patrick.schratz@gmail.com> Co-committed-by: pat-s <patrick.schratz@gmail.com>
2024-04-18 07:23:34 +00:00