forgejo/governance
40
34
Fork
You've already forked governance
35

[AGREEMENT] dachary application to release team #2

Closed
opened 2023年03月02日 03:53:02 +01:00 by Ghost · 2 comments

Application

I propose to be accountable for the Forgejo release and become part of the the release team.

  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.

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.

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.
Ghost changed title from (削除) [AGREEMENT] dachary application to the release team (削除ここまで) to [AGREEMENT] dachary application to release team 2023年03月05日 10:47:24 +01:00

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.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Collecting stakeholders
We're in a decision-making process, figuring out the relevant stakeholders and bringing them into the process
[Decision] Documenting and implementing
We finished a decision-making process, now documenting and/or implementing the decision
[Decision] Gathering advice
We're in a decision-making process, waiting for people to add their feedback
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
[Decision] Phrasing shared motive
We're in a decision-making process, phrasing the shared question/problem/issue we want to tackle
Membership
Process of appointing a person as a team member.
Moderation
Moderation actions in Forgejo spaces
Money
Accounting, day to day management of money
Scheduled chores
Tasks that need to be done at a scheduled date in the future (paying the bills, renewing certificates, etc.)
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/governance#2
Reference in a new issue
forgejo/governance
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?