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

[AGREEMENT] crystal membership renewal to release team #357

Closed
opened 2025年12月19日 03:30:49 +01:00 by crystal · 0 comments

Membership

I propose to remain part of the release team.

  1. If you agree, please simply add a 👍 to this issue.
  2. If you disagree or have concerns, please write them in a comment below and I will do my best to address them.

This membership request follows the Forgejo decision making process (accepted after 2 weeks, unless concerns are raised).

Pledge

I pledge to act in accordance with the code of conduct, and all other rules and processes agreed via the Forgejo decision making process.

If there is an agreement for me to be a member of the team, I will consider renewing my membership a year later.

Background

I have been a member of the release team (albeit inactive) since the beginning. The release team thankfully does now have plenty of additional members, but I intend to help out with filling the void that will surely be left by @earl-warren's 2026 sabbatical, whose admirable dedication to the project has been carrying it thusfar.

Previous membership requests

  • March 2023: #5
  • Feb 2024: #80
  • Jan 2025: #212
### Membership I propose to remain part of the release team. 1. If you agree, please simply add a 👍 to this issue. 2. If you disagree or have concerns, please write them in a comment below and I will do my best to address them. This membership request follows the Forgejo [decision making process](https://codeberg.org/forgejo-contrib/governance/src/branch/main/DECISION-MAKING.md) (accepted after 2 weeks, unless concerns are raised). ### Pledge I pledge to act in accordance with the [code of conduct](https://codeberg.org/forgejo/code-of-conduct/), and all other rules and processes agreed via the Forgejo [decision making process](https://codeberg.org/forgejo-contrib/governance/src/branch/main/DECISION-MAKING.md). If there is an agreement for me to be a member of the team, I will consider renewing my membership a year later. ### Background I have been a member of the release team (albeit inactive) since the beginning. The release team thankfully does now have plenty of additional members, but I intend to help out with filling the void that will surely be left by @earl-warren's [2026 sabbatical](https://codeberg.org/forgejo/discussions/issues/191), whose admirable dedication to the project has been carrying it thusfar. ### Previous membership requests - March 2023: #5 - Feb 2024: #80 - Jan 2025: #212
viceice added the due date 2026年01月02日 2025年12月19日 08:35:16 +01:00
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".

2026年01月02日

Reference
forgejo/governance#357
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?