English Spanish
We use the git repository to record status documents. An https://pagure.io/fedora-pgm/pgm_team/blob/main/f/example.md[example file] is in the root of the repo.
We use the following tags (or "labels"):
The top of the markdown file should contain basic information about the project (e.g. main contact, links to resources, etc.)
The repository intentionally does not have any roadmap milestones defined. We will need to use it for a while and see what naturally arises for us.
The repository intentionally does not have any priorities defined. We will need to use it for a while and see what naturally arises for us.
The repository intentionally does not have any boards set up. We will need to use it for a while and see what naturally arises for us.
The primary repository for the team is the https://pagure.io/fedora-pgm/pgm_team[pgm_team repo]. This document describes how we use it.
The following guidelines apply:
The example file is a _guideline_. You do not need to strictly match it. Add or remove information as you see fit. It is not machine-parsed, so as long as the meaning is clear to the rest of the team, variations in style and content are okay.
Tags
**support request**.
We use this to tag requests from other teams in Fedora.
Status files
**spins keepalive**.
This tag is for issues related to the semi-annual keepalive process for Spins and Labs.
**schedule**.
This tag is for issues related to the https://fedorapeople.org/groups/schedule/[Fedora Project Schedule].
Roadmap
Remember that these files are so that others can step in to help you if needed. Try to document what you'd want to know if you were coming into the project.
Put the latest updates at the top of the update section (so updates should appear newest to oldest)
Priorities
Previous work should be moved into the `past/` directory.
PgM Team repository