Issue Workflow

Currently the Force Feedback Programming (FFP) extension is still under "controlled development". As the owners of the project we - Robin and Ralf - would like to decide which issues to focus on next. Not all issues are created equal ;-)

That's why we're asking you, dear contributer, to follow our plan. Please focus your effort on what we think should be done next. Here's how it's working right now:

1. Anybody who wants to raise an issue just adds it to the issue list.
2. The Product Owner (PO) for FFP - currently Ralf - reviews new issues, consolidates them if necessary, categorizes them (using a label, e.g. bug, idea) and assigns them to the milestone Feedback.
3. Periodically the PO reviews feedback to decide what to include in the backlog. Not before an issue is assigned to the milestone Backlog it`s bound to be implemented. Sometime at least ;-) Only backlog items have been accepted as valuable changes to FFP.
4. Not all backlog items are up for implementation, though. Only the top priority issues should be considered by you. They have been assigned to the milestone Ready for progress. If you'd like to get your hands dirty on one of those issues, please tell the PO by leaving a comment in the issue. He'll respond to you and move the issue to the In progress milestone.
5. After you resolved the issue and submitted your PR please assign the issue to the milestone Approve yourself! The PO will then know you deem your work ready for an acceptance check.

Consider the milestones as columns on a Kanban board:

Feedback | Backlog | Ready for progress | In progress | Approve

Issues should be flowing across this board from left to right.