Archived
15
23
Fork
You've already forked meta
6

[AGREEMENT] Disolving and re-creating the moderation team #145

Open
opened 2023年01月31日 22:02:45 +01:00 by Ghost · 0 comments

Applications

  • (add yourself)

Rationale

The moderation team was created at the very begining of the Forgejo project and has not been approved by the Forgejo community. This needs to change given how important it became. Now that there exists an embryo of decision making, I propose it is done as follows.

  • A discussion happens in this issue regarding how the moderation team is to be appointed
  • Forgejo community members apply to be part of the future moderation team (following the examples set by the existing applications in other teams (see 1 and 2) or whatever they think more appropriate).
  • The larger Forgejo community is actively asked for feedback when there is at least two applicants (the assignee of this issue are accountable to make that happen)
  • When at least two members meet the approval of the community, the existing moderation team is disolved and hand over their duties to the newly formed team.

When created, the moderation team is expected to define its own procedures, base on the existing seminal work or however they see fit.

Does that sound like a sensible way to create a legitimate moderation team?

### Applications * (add yourself) ### Rationale The moderation team was created at the very begining of the Forgejo project and has not been approved by the Forgejo community. This needs to change given how important it became. Now that there exists an [embryo of decision making](https://codeberg.org/forgejo/meta/src/branch/readme/DECISION-MAKING.md), I propose it is done as follows. * A **discussion** happens in this issue regarding how the moderation team is to be appointed * Forgejo community members **apply** to be part of the future moderation team (following the examples set by the existing applications in other teams (see [1](https://codeberg.org/forgejo/meta/issues/142) and [2](https://codeberg.org/forgejo/meta/issues/141)) or whatever they think more appropriate). * The larger Forgejo community is **actively asked for feedback** when there is at least two applicants (the assignee of this issue are accountable to make that happen) * When at least two members meet the approval of the community, the existing moderation team is disolved and hand over their duties to the newly formed team. When created, the moderation team is expected to define its own procedures, base on the [existing seminal work](https://codeberg.org/forgejo/meta/issues/138) or however they see fit. Does that sound like a sensible way to create a legitimate moderation team?
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
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] 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
1 participant
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#145
Reference in a new issue
forgejo/meta
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?