Add info on how we track status
This commit is contained in:
parent
fce18741f1
commit
93468d6fb0
1 changed files with 25 additions and 4 deletions
|
|
@ -3,7 +3,28 @@
|
|||
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
|
||||
== 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 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.
|
||||
* The top of the markdown file should contain basic information about the project (e.g. main contact, links to resources, etc)
|
||||
* Put the latest updates at the top of the update section (so updates should appear newest to oldest)
|
||||
* Add updates as frequently as appropriate, but generally at least once a month.
|
||||
For most projects, once every one or two weeks is probably better.
|
||||
* Include links to specific issues, etc that are blocking the work or that are major unresolved decisions.
|
||||
|
||||
TIP: 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.
|
||||
|
||||
== Pagure setup
|
||||
|
||||
=== Tags
|
||||
|
||||
We use the following tags (or "labels"):
|
||||
|
||||
|
|
@ -20,17 +41,17 @@ This tag is for issues related to the semi-annual keepalive process for Spins an
|
|||
Is there another tag you think we should use?
|
||||
Propose it!
|
||||
|
||||
== Priorities
|
||||
=== Priorities
|
||||
|
||||
The respository intentionally does not have any priorities defined.
|
||||
We will need to use it for a while and see what naturally arises for us.
|
||||
|
||||
== Boards
|
||||
=== Boards
|
||||
|
||||
The respository intentionally does not have any boards set up.
|
||||
We will need to use it for a while and see what naturally arises for us.
|
||||
|
||||
== Roadmap
|
||||
=== Roadmap
|
||||
|
||||
The respository intentionally does not have any roadmap milestones defined.
|
||||
We will need to use it for a while and see what naturally arises for us.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue