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