docs: remove pat-s from maintainers #918

pat-s · 2025-08-04T18:57:37Z

pat-s commented

2025-08-04 18:57:37 +00:00

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

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

pat-s added 1 commit 2025-08-04 18:57:37 +00:00

add

commitlint / check-and-test (pull_request) Successful in 7s

Details

check-and-test / check-and-test (pull_request) Successful in 45s

Details

89f31e4fda

justusbunsi merged commit 9206b34af3 into main

2025-08-04 19:06:40 +00:00

justusbunsi deleted branch chore/remove-as-maintainer

2025-08-04 19:06:41 +00:00

justusbunsi referenced this issue from a commit

2025-08-04 19:06:42 +00:00

docs: remove pat-s from maintainers (#918)

~~giteabot referenced this pull request 2025-08-04 19:07:56 +00:00~~

Changelog for upcoming version #809

lunny commented

2025-08-04 22:45:48 +00:00

Thank you so much for all the years of hard work, dedication, and high standards you’ve brought to maintaining the Gitea Helm chart. Your contributions have been deeply appreciated — not just by me, but by the broader Gitea community, especially those running Gitea in Kubernetes environments. You’ve helped shape an important part of our ecosystem.

It’s of course a real pity to see you step down, but I fully understand your reasons. It’s admirable that you’re being intentional with your time and energy, and I respect your decision to focus on the tools you actively use in your daily life. Maintaining open source projects is rarely easy, and balancing this with professional and personal responsibilities is always a challenge.

I also want to acknowledge your honesty and transparency — both about the technical reasons and about the community atmosphere. As Gitea continues to grow, we know there’s always room to improve, and I genuinely appreciate the feedback. Your message is a helpful reminder for us to continue fostering an open, respectful, and supportive environment for all contributors.

Even though our paths may now diverge in terms of project focus, I want to thank you again for everything you’ve done — not just the code, but the thoughtful maintenance, discussions, and the collaborative spirit you brought to the project. We’ll miss having you on board, and I wish you all the best with CodeFloe and your other endeavors.

You’re always welcome back any time.

Thank you so much for all the years of hard work, dedication, and high standards you’ve brought to maintaining the Gitea Helm chart. Your contributions have been deeply appreciated — not just by me, but by the broader Gitea community, especially those running Gitea in Kubernetes environments. You’ve helped shape an important part of our ecosystem. It’s of course a real pity to see you step down, but I fully understand your reasons. It’s admirable that you’re being intentional with your time and energy, and I respect your decision to focus on the tools you actively use in your daily life. Maintaining open source projects is rarely easy, and balancing this with professional and personal responsibilities is always a challenge. I also want to acknowledge your honesty and transparency — both about the technical reasons and about the community atmosphere. As Gitea continues to grow, we know there’s always room to improve, and I genuinely appreciate the feedback. Your message is a helpful reminder for us to continue fostering an open, respectful, and supportive environment for all contributors. Even though our paths may now diverge in terms of project focus, I want to thank you again for everything you’ve done — not just the code, but the thoughtful maintenance, discussions, and the collaborative spirit you brought to the project. We’ll miss having you on board, and I wish you all the best with CodeFloe and your other endeavors. You’re always welcome back any time.

👍 1

lunny referenced this issue from a commit

2025-08-05 00:03:22 +00:00

Step down as maintainer (pat-s) (#35213)

pat-s commented

2025-08-05 10:14:51 +00:00

Thanks for the kind words, @lunny!

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: gitea/helm-gitea#918