Created Project management (markdown)

Project-management.md

@@ -0,0 +1,32 @@
+_This is a stub page and will be expanded on_
+
+For this project we are in a relatively unique situation where we have a live product but we are also aiming to "ship" feature-complete at a future date to allow migration away from `osu-stable` (the old osu! client). For this reason, for the time being we have a primary focus on completing remaining tasks required to "go live".
+
+## Labels
+
+Labels track rough areas of concern or types of issues. Labels are defined as `<category>:<identifier>`. At most, one `identifier` should be chosen per `category` per issue.
+
+Current categories:
+
+- `area` The area in the game that this issue relates to
+- `type` The type of an issue, if it can be defined into a common type
+
+We also have special labels for other use cases
+
+- `blocked` An issue which is blocked on another task or external fix.
+- `bounty` An issue which has a monetary bounty attached.
+- `good first issue` A good place to start contributing to this project without going too deep.
+- `low priority` A task which the core team will not address in the next 6 months. External contributors are welcome to attempt these tasks.
+- `proposal` An issue which has not yet reached consensus as to whether it will be implemented.
+
+## Projects
+
+Projects track large areas of the game which are required for live. These can be considered "epic" issues. We don't directly use the "kanban" views and generally these are used for tracking purposes at a high level.
+
+## Milestones
+
+Milestones track core team tasks in a chronological fashion. We respect a few rules when dealing with milestones:
+
+- Add new tasks that should be completed ASAP only to milestones *after* the current month
+- Don't move tasks forward from past milestones
+- Exception: If the current month is completed early, tasks may be moved forward from future milestones