meta/TEAMS.md
2023-03-23 10:14:04 +00:00

5.6 KiB

Forgejo teams

A team is a group of people who work together on a specific area to further Forgejo.

Some of the teams are trusted with access to exclusive resources that require credentials. To participate in such a team someone can open a pull request to add their name and their membership will be decided by the Forgejo community (see the decision making document for more information).

Secrets keeper

Purpose: See the documentation.

Accountability:

  • Keep the Forgejo credentials (social accounts, release keys, etc.) in a safe place.

Team members:

Admins

Purpose: The team has administrative access to all repositories except those with Forgejo credentials.

Accountability:

  • Grant access to team members depending on what they need.

Team members:

Accessibility

Purpose: Work on improving Forgejo accessibility.

Team members:

Devops

Purpose: The team cares for the resources that Forgejo depends on (CI, static web site hosting). The team has administrative access to all repositories involved in the CI/CD pipelines (code, releases, website, etc.).

Accountability:

  • Fix problems that prevent the resources that Forgejo depends on from running.

Team members:

Contributors

Purpose: Improve Forgejo. The team has write access to all repositories but no access to Forgejo credentials.

Team members:

Chatrooms / matrix

Purpose: manage the Matrix chatrooms

Accountability:

  • Address technical problems that prevent people/bots from participating

Team members:

Releases

Purpose: See the documentation. The team is trusted with the primary GPG key used to sign Forgejo releases.

Accountability:

  • Publish Forgejo releases.

Team members:

Security

Purpose: See the documentation.

Accountability:

  • Handle security vulnerabilities.

Team members:

Social account

Purpose: See the documentation

Accountability: reply to questions and publish news.

Team members:

Well-being

Purpose: See the documentation.

Accountability:

  • Defuse tensions before they escalate

Team members:

Moderation

Purpose: See the documentation.

Accountability:

  • Enforce the Code of Conduct

Team members:

  • (none)

Decision-making

Purpose: The Forgejo team effectively and successfully makes collaborative decisions that tend to and integrates the variety of needs and concerns that arise

Accountabilities:

  • Be a point of contact for challenges that arise during attempts to make decisions
  • Look for further external support when needed

Resources maintained:

  • <DECISION-MAKING.md> and the other agreement files it links to

Team members:

Github organisation owners

FreeBSD

Purpose: to provide advice when needed about FreeBSD builds and the FreeBSD ports tree.

Accountabilities:

Be a point of contact for all FreeBSD & Forgejo related matters

Resources maintained:

https://codeberg.org/forgejo-contrib/freebsd

Team members: