Archived
15
23
Fork
You've already forked meta
6

Becoming a legitimate member of Forgejo teams #173

Merged
earl-warren merged 1 commit from :wip-teams into readme 2023年02月27日 16:05:54 +01:00

Now that a decision making process is in place, as pledged at the
begining of Forgejo, I step down from all teams I belong to. I will
apply to become a member of the team in a way that meets the agreement
of the Forgejo community. This is an important step towards a
democratic governance and I'm happy this is happening.

I am not stepping down from the security team because:

  • It is critical to keep the Forgejo user safe
  • I have already applied to become a member
Now that a decision making process is in place, as pledged at the begining of Forgejo, I step down from all teams I belong to. I will apply to become a member of the team in a way that meets the agreement of the Forgejo community. This is an important step towards a democratic governance and I'm happy this is happening. I am not stepping down from the security team because: * It is critical to keep the Forgejo user safe * I have already applied to become a member
Now that a decision making process is in place, as pledged at the
begining of Forgejo, I step down from all teams I belong to. I will
apply to become a member of the team in a way that meets the agreement
of the Forgejo community. This is an important step towards a
democratic governance and I'm happy this is happening.
I am not stepping down from the security team because:
* It is critical to keep the Forgejo user safe
* I have already applied to become a member
First-time contributor
Copy link

The security team is at the end of the process to become legitimate #174

I'll merge this which may require a rebase

The security team is at the end of the process to become legitimate https://codeberg.org/forgejo/meta/pulls/174 I'll merge this which may require a rebase
First-time contributor
Copy link

It is an interesting case: this could be merged without approval because it is a personal decision from a Forgejo community member.

It is an interesting case: this could be merged without approval because it is a personal decision from a Forgejo community member.
Commenting is not possible because the repository is archived.
No reviewers
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] 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
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
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
2 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/meta!173
Reference in a new issue
forgejo/meta
No description provided.
Delete branch ":wip-teams"

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?