Application
I propose to be accountable for the Forgejo release and become part of the the release team.
- If you agree, please simply add a 👍 to this issue.
- If you disagree or have reservations, please write them down here, in a comment.
This application follows the Forgejo decision making process.
This is a follow-up to my previous successful application to the release team in 2023 in #5
Pledge
I pledge to publish Forgejo releases by following and improving the release process
If an agreement is reached for me to become a member of the release team, I pledge to re-apply to retain this position on the team after approximately one year.
Background
Chaotic events in my own life caused me to be unable to work on Forgejo as frequently as I wished to over the course of the past year, and thus the release team's responsibilities have largely fallen on other members of the team, namely @earl-warren, without whom Forgejo simply would not have been possible throughout the last year.
With the upcoming hard fork, the release team will no longer have the responsibility of rebasing on a weekly basis, but that doesn't necessarily mean their responsibilities will be reduced. After the hard fork, Forgejo's community will be fully responsible for building and maintaining the software moving forward, including analyzing and cherry picking improvements from Gitea's codebase as it continues to evolve.
In 2024, I intend to spend a lot more time working on Forgejo. I am proactively opening this issue ahead of the March 2024 deadline and doubling down on my commitment to improving Forgejo in the next year. I will work with the release team to ensure the completeness of the release notes and major release blog posts, and making sure Forgejo's releases are representative of the reliable quality software our community has come to expect.
### Application
I propose to be accountable for the Forgejo release and become part of the [the release team](https://codeberg.org/forgejo/meta/src/branch/readme/TEAMS.md#releases).
1. If you agree, please simply add a 👍 to this issue.
2. If you disagree or have reservations, please write them down here, in a comment.
This application follows the Forgejo [decision making process](https://codeberg.org/forgejo/governance/src/branch/main/DECISION-MAKING.md).
This is a follow-up to my previous successful application to the release team in 2023 in #5
### Pledge
I pledge to publish Forgejo releases by following and improving the [release process](https://forgejo.org/docs/latest/developer/release/)
If an agreement is reached for me to become a member of the release team, I pledge to re-apply to retain this position on the team after approximately one year.
### Background
Chaotic events in my own life caused me to be unable to work on Forgejo as frequently as I wished to over the course of the past year, and thus the release team's responsibilities have largely fallen on other members of the team, namely @earl-warren, without whom Forgejo simply would not have been possible throughout the last year.
With the upcoming [hard fork](https://codeberg.org/forgejo/governance/issues/58), the release team will no longer have the responsibility of rebasing on a weekly basis, but that doesn't necessarily mean their responsibilities will be reduced. After the hard fork, Forgejo's community will be fully responsible for building and maintaining the software moving forward, including analyzing and cherry picking improvements from Gitea's codebase as it continues to evolve.
In 2024, I intend to spend a lot more time working on Forgejo. I am proactively opening this issue ahead of the March 2024 deadline and doubling down on my commitment to improving Forgejo in the next year. I will work with the release team to ensure the completeness of the release notes and major release blog posts, and making sure Forgejo's releases are representative of the reliable quality software our community has come to expect.