meta/AGREEMENTS.md
fr33domlover 05dc4604c9 Document decision-making process (#148)
So far, the decision-making guide is a brief very simplified one.

This PR:

- Improves the simplified guide
- Adds a full detailed version of the decision-making process, to help everyone make non-trivial decisions together, and so that even if I disappear, the project has the tools to continue, learn, evolve, flourish
- Tweaks the table in AGREEMENTS.md based on earlier feedback

Clarification: This PR isn't making a new agreement/decision, it's mostly just expanding the decision-making guide, and we can continue to try the guide in Forgejo and see how it goes and improve it as needed. Or even throw it away entirely if it really doesn't work.

It's not a command forcing you to make decisions in a certain way. It's a helpful resources giving you a way to make decisions together. If you know what you're doing and you don't need a guide, that's fine.

# The Request

If you have **limited time to read** the guide:

Can you **skim** through it and see if there's anything that stands out, that **bothers/concerns** you or that you disagree with? And comment if yes. Otherwise, do you trust me and **willing that we try the guide in Forgejo** (despite not thoroughly reading it) and see how it goes, and let it improve via ongoing feedback, and make an official community approval at a later time? (Worst case, if it turns out to be garbage, we can delete it)

If you **don't have time to read** the guide:

Do you trust me and **willing that we try the guide in Forgejo** (despite not reading the very long detailed sections that this PR adds) and see how it goes, and let it improve via ongoing feedback, and make an official community approval at a later time? (Worst case, if it turns out to be garbage, we can delete it)

If you **have time to thoroughly read** the guide:

Can you go through it and review / give feedback? Including *questions* if there's anything there that's unclear or confusing.

If you don't have enough trust in me to answer yes to the questions above, that's fine and please don't hesitate to say so <3 I know it's hard to trust a stranger landing some huge document out of nowhere. We'll figure out a pathway to togetherness. Even if it means simply closing this PR without merging anything.

Co-authored-by: fr33domlover <fr33domlover@riseup.net>
Reviewed-on: https://codeberg.org/forgejo/meta/pulls/148
2023-03-02 15:04:53 +00:00

2.5 KiB

Forgejo Organization Agreements

Agreements are ways of working, practices and methods that help us work together effectively to make Forgejo amazing and achieve its goals.

These are the overall Forgejo Organization agreements; specific teams may have their own agreements about how they work. See <TEAMS.md> for more info.

Decision Making

  • Where to document agreements: When a decision is made, and it includes an agreement about how we do things, the person who initiated the decision records the agreement as follows:
    • If it's within a specific team, it goes into that team's agreements file
    • If it's a change in the roles of team members, update TEAMS.md
    • If it's a conceptual agreement about our purpose and values, it goes into MISSION.md
    • Otherwise, it goes into this file, i.e. AGREEMENTS.md

Responsibility distribution table

Each item has 4 pieces of info:

  1. Domain: Type of decision / domain of responsibility
  2. Who decides / Who is accountable
  3. How? Based on what? Advice, policy, criteria
  4. Duration: How often do we review and re-approve
  5. Review: When's the next time do we review and re-approve
  • Domain: Security

    • Who: Security Team
    • How:
      • Consider impact on Forgejo instances, users and admins
      • Consult with relevant security-knowledgeable people if needed
    • Duration: 1 year
    • Review: 1 Feb 2024
  • Domain: Fediverse account

    • Who: Social Account Team
    • How: -
    • Duration: 1 year
    • Review: 1 Feb 2024
  • Domain: Anything else

    • Who: The community together, with a facilitator about whom there's no controversy (either an Organization member or external person chosen for this), with the option to delegate an urgent decision to a small group to make in behalf of the community
    • How: Using the process described in DECISION-MAKING.md (or any other collaborative inclusive process, as long as all participants are okay with it)
    • Duration: 1 year
    • Review: 1 Feb 2024

Branding: Forgejo name, tagline, logo and mascot

The name of the project is Forgejo, the tagline is Beyond coding. We forge.. See here for details.

Logo

Forgejo Mascot

Logo

Conflict Engagnement

  • When a conflict arises, we contact the well-being team and ask for their support to mediate the conversation