governance/TEAMS.md

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).

Accessibility

Purpose: Work on improving Forgejo accessibility.

Team members:

• https://codeberg.org/Ryuno-Ki March 2023 Agreement

Devops

Purpose: The team cares of all the technical resources that Forgejo depends on (hardware, CI, static web site hosting, social media etc.). It helps all other teams to use those resources by installing, upgrading or migrating them when needed. If a resource becomes unavailable, it will help restore it in a functional state.

Accountability:

• Fix problems that prevent the resources that Forgejo depends on from running.
• Keep the credentials to access the resources in a safe place and share them with the teams that need them.

Team members:

• https://codeberg.org/crystal April 2023 Agreement
• https://codeberg.org/earl-warren April 2023 Agreement
• https://codeberg.org/dachary April 2023 Agreement

Contributors

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

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:

• https://codeberg.org/crystal March 2023 Agreement
• https://codeberg.org/earl-warren March 2023 Agreement
• https://codeberg.org/dachary March 2023 Agreement

Security

Purpose: See the documentation.

Accountability:

• Handle security vulnerabilities.

Team members:

• https://codeberg.org/Gusted February 2023 Agreement
• https://codeberg.org/dachary February 2023 Agreement
• https://codeberg.org/fnetX February 2023 Agreement

Social account

Purpose: See the documentation

Accountability: reply to questions and publish news.

Team members:

• ???

Moderation

Purpose: See the documentation.

Accountability:

• Take action when a behavior in a Forgejo space goes against the Code of Conduct or the law.
• Follow the moderation process and publish auditable reports based on facts and logic.

Team members:

• https://codeberg.org/earl-warren May 2023 Agreement

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:

• fr33domlover (Matrix; Fediverse; Email; fr33domlover on Libera Chat)

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:

• ???