... | ... | @@ -14,12 +14,22 @@ Branches |
|
|
|
|
|
Issues
|
|
|
|
|
|
* Every ticket should be labelled bug, task, feature, feature request or document
|
|
|
* When you start working on a ticket, assign it to yourself
|
|
|
* Label your ticket 'in progress' while you're working on it, then 'in code review' while it's being reviewed
|
|
|
* When your branch is merged, label the ticket 'fixed' and close it
|
|
|
* As a rule of thumb, if a ticket takes longer than a day, break it into smaller tickets (mention the parent in the description)
|
|
|
* Every ticket should be labelled 'bug', 'task', 'feature', 'feature request' or 'document'
|
|
|
* Bugs are mistakes that affect the user, e.g. potential crashes
|
|
|
* Tasks are work items that don't directly affect the user, e.g. refactoring or research
|
|
|
* Features are work items that directly affect the user
|
|
|
* Feature requests are features that someone has asked for -- we might or might not implement them, but they're worth documenting
|
|
|
* Documents are work items that produce writing rather than software
|
|
|
* When you start working on a ticket, assign it to yourself
|
|
|
* Label your ticket in progress while you're working on it, then in code review while it's being reviewed
|
|
|
* When your branch is merged, label the ticket fixed and close it |
|
|
* Documents are work items that produce text rather than software
|
|
|
|
|
|
Meetings
|
|
|
|
|
|
* At the start of each week, please let the team know roughly what hours you'll be working via the standup channel
|
|
|
* At the start or end of each day (whichever's closer to 10am UTC), please post an update to the standup channel saying:
|
|
|
* What you worked on yesterday/today
|
|
|
* What you'll be working on today/tomorrow
|
|
|
* Any blockers
|
|
|
* If you're online at 10am UTC, please post your update at that time so we can have an interactive meeting |