[AGREEMENT] dachary application to release team #2

New Issue

Closed

opened 2023-03-02 02:53:02 +00:00 by dachary · 2 comments

dachary commented

2023-03-02 02:53:02 +00:00

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.

Pledge

I pledge to publish Forgejo releases by following and improving the release process

I pledge to rebase Forgejo by following and improving the documented workflow

I pledge to only use my access to the social account for the purpose of announcing the release.

If there is an agreement for me to be a member of the team, I pledge to apply again a year later.

Background

I authored and maintained the release process, the rebase workflow and the soft-fork-tools.

I took care of all the rebase from the beginning of Forgejo as documented in the recurring issue and publishing all releasees up to v1.18.3.

In the past few weeks I began automating the tools and transferring my knowledge to other Forgejo contributors. That allowed @crystal to successfully publish v1.18.3-2 and @earl-warren to successfully rebase Forgejo 25 February 2023.

I created the initial scripted configuration based on @gapodo scripts took care of the upgrades on both https://forgejo-ci.codeberg.org and https://ci.dachary.org when bug fixes or diagnostics were necessary.

### 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/meta/src/branch/readme/DECISION-MAKING.md). ### Pledge I pledge to publish Forgejo releases by following and improving the [release process](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING/RELEASE.md) I pledge to rebase Forgejo by following and improving the documented [workflow](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING/WORKFLOW.md) I pledge to only use my access to the social account for the purpose of announcing the release. If there is an agreement for me to be a member of the team, I pledge to apply again a year later. ### Background I authored and maintained the [release process](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING/RELEASE.md), the rebase [workflow](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING/WORKFLOW.md) and [the soft-fork-tools](https://codeberg.org/forgejo-contrib/soft-fork-tools). I took care of all the rebase from the beginning of Forgejo [as documented in the recurring issue](https://codeberg.org/forgejo/forgejo/issues/51) and publishing all releasees up to v1.18.3. In the past few weeks I began automating the tools and transferring my knowledge to other Forgejo contributors. That allowed @crystal to successfully publish [v1.18.3-2](https://codeberg.org/forgejo/forgejo/issues/368) and @earl-warren to successfully [rebase Forgejo 25 February 2023](https://codeberg.org/forgejo/forgejo/milestone/3550). I created the initial [scripted configuration](https://codeberg.org/Codeberg-Infrastructure/scripted-configuration/src/branch/main/hosts/forgejo-ci) based on @gapodo scripts took care of the upgrades on both https://forgejo-ci.codeberg.org and https://ci.dachary.org when bug fixes or diagnostics were necessary.

👍 5

dachary added the

[Decision] Gathering advice

label 2023-03-02 02:53:02 +00:00

dachary commented

2023-03-02 02:56:11 +00:00

Poster

For the record I previously withdraw the same application because I was overwhelmed by a number of unfounded accusations. I trust this new Forgejo space is safe and apply again.

For the record I previously [withdraw the same application](https://codeberg.org/forgejo/meta/issues/176) because I was overwhelmed by a number of unfounded accusations. I trust this new Forgejo space is safe and apply again.

👎 1

dachary added

Election

and removed

[Decision] Gathering advice

labels 2023-03-02 03:05:24 +00:00

dachary changed title from ~~[AGREEMENT] dachary application to the release team~~ to [AGREEMENT] dachary application to release team

2023-03-05 09:47:24 +00:00

dachary commented

2023-03-08 14:24:00 +00:00

Poster

Added a pledge to only use social account for announcing releases in the context of my involvement in the release team (same as forgejo-contrib/governance#3 (comment))

I pledge to only use my access to the social account for the purpose of announcing the release.

Added a pledge to only use social account for announcing releases in the context of my involvement in the release team (same as https://codeberg.org/forgejo-contrib/governance/issues/3#issuecomment-827988) > I pledge to only use my access to the social account for the purpose of announcing the release.

👎 1 👀 1