lpm - Lightweight Project Management

Project Management

Traap's repositories use a lightweight project management system provided by GitHub.

A project board is created with the following columns:

Backlog - Issues that have not been started.
In Progress - Issues that are being worked on.
In Review - Issues that have are part of a pull request or manual review process.
Done - Issues that are done.
Pull Request - Issues that are tagged as a pull request.

lpm uses different done classifications as follows:

duplicate - A reference to one or more duplicate is provided.
invalid - An Issues has been determined to be invalid. A rationale is given.
wontfix - An Issues will not be fixed and a rationale is given.

lpm uses GitHub milestones as a Sprint. Projects uses 5-day sprints. Sprints names use the following naming convention: Sprint vM.N.S, where

As an example, three consecutive Sprints are declared as follows:

lpm uses labels as follows:

bug - is an Issues that did not meet the intent of the Story.
duplicate - is an Issues that duplicates another issue regardless of the Issues label. A rationale is given for duplicate Issues.
enhancement - the Agile Story format

    As a <type of user> I want <some goal> so that <some reason>.

help wanted - is most often used as a secondary tag to ask for help determining the direction an Issues should take.
invalid - is an issue that is invalid. A rationale is given for invalid Issues.
pull request - is used to label a pull request.
question - is most often used as a secondary tag to ask another person a question and to track the answer to closure.
wontfix - this Issues will not be fixed. A rationale is given for Issues that are not fixed.

lpm consist of one or more milestones. Release names use the following naming convention: vM.N.P name, where