Using the SCRUM Board
To keep things organised and avoid stepping on each other's toes, we are relying on the GitHub Project SCRUM Board. The Project SCRUM Board is the way we communicate, the tool we use to have a bigger picture of what is happening, and the way you will keep records of your work into the BHoM.
.
Each card that you see there corresponds to an issue raised in one of the repos. From the moment it is created to the time when that issue has been completely resolved, the corresponding card will go through the different columns of this board.
To create a card in any column, click on the + symbol at the top left of the column and write a name for the issue/card. The name should be RepoName - Description or ProjectName - Description depending on whether the issue needs changes in the entire repo or in a specific Visual studio project. If you don't know which one it is, just use the repository name. Once the card is created, click on the 3 dots at the top right and select Convert to issue. You can then click on the card name to open the issue and complete the form like you would normally do.
Not that cards might be created from outside of this board. They are then available in the Add Card section on the top right of the page (just above the board).
The ideas and future development column is where we store issues/discussion cards that are valuable, and so should not removed or archived, but they are not necessarily immediately applicable to the current development focus and thus they don’t belong in the backlog.
The backlog is the curated list of issues identified as usefully contributing to the current development focus, and any of which may be selected as Priority...
Once an issue has been assigned to a person as part of his/her tasks for the week, the card is moved to the priority column. If the card/issue was not assigned to anyone at that time, it will then be assigned to that person. You can see who has been assigned the issue by looking at the avatar at the bottom right of the card.
A card is moved to that column when a person starts working on it. Normally, only one card per person should be in that column at a time.
Cards in that column are also locking the repository or the project it targets. This means that nobody is allowed to start editing code in that repository while a card is in the In Progress or For Review column. This also means that you can only move a card in that column if there is not already a card locking the same repository. Coordinate with the card's owner if this is the case.
Once the issue is resolved and a Pull Request has been created, the card is move to the For Review Column waiting for people to review and approve the Pull request.
Once the pull request has been merged into the master branch and the issue closed, the card is moved the the Completed column where it will be discussed in the next planning call. Notice that, once an issue is closed, the logo at the top left of the card has turn red. The Completed column is the only one that should have cards in that state.