|
PgM Team repository
|
|
|
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.
|
|
|
Tags
|
|
|
We use the following tags (or "labels"):
|
|
|
**documentation**.
This is used for issues related to documentation.
Generally that means things we document in the PgM Team (or other program management) documentation.
|
|
|
**support request**.
We use this to tag requests from other teams in Fedora.
|
|
|
**schedule**.
This tag is for issues related to the https://fedorapeople.org/groups/schedule/[Fedora Project Schedule].
|
|
|
**spins keepalive**.
This tag is for issues related to the semi-annual keepalive process for Spins and Labs.
|
|
|
Is there another tag you think we should use? Propose it!
|
|
|
Priorities
|
|
|
Boards
|
|
|
Roadmap
|
|
|
Status files
|
|
|
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.
|
|
|
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.
|
|
|
The following guidelines apply:
|
|
|
Active work should be in a markdown file in the `current/` directory.
|
|
|
Previous work should be moved into the `past/` directory.
|
|
|
If you have additional supporting information with no better place to store it, create a directory with the same name as the markdown file.
|
|
|
Put the latest updates at the top of the update section (so updates should appear newest to oldest)
|
|
