By participating in this project, you agree to abide by the our Code of Conduct which reflects the Contributor Covenant.
- Fork the project
- Make your changes
- Submit a PR. A good PR would be muchly appreciated
- Wait on us to get back to you. We shouldn't be long, 3 working days at most, but sometimes work and life could slow this down
Some things that will help the PR get through
- Reference a
userstory, or abug. - Again, a good PR goes a long way
- Leverage our internal process for clarity and organisation where you can.
Labels define most of our process within GitHub
### Userstory
Who are you, and how might we help?
A new piece of functionality that we have no baseline for, and would like to
start testing, often against a userstory.
A change made to an existing part of the product to try raise the baseline KPIs.
A change made to ensure a feature is maintaining the baseline KPIs.
Requires someone with this speciality to take a look before we continue. Could be used in conjunction with assignee.
The type of research that was performed
Literally, doing it this quarter (potentially use milestones?).
Used to raise transparency about the work that is going on, but not necessarily completely ready for review.
The issue was closed with no resolution, as we have explicitly decided there shouldn't be one.
We use projects to give us another slice of our data, and track what state the bits of work are in using traditional, and GitHub automated, Kanban.
