Skip to content

Issue Review & Approval process

Jump to bottom
Michael O'Connor edited this page Mar 17, 2021 · 1 revision

Why we review & approval Issues

To ensure all work on the project match the overall project vison and planning has been done to considerate changes in the code. Some tickets may introduce a breaking change and will need to be reviewed and passed on to teams that are affected by the breaking change. This serves to save time and make sure issues are productive and meaningful.

Issue Criteria:

  1. The issue must be related to approved design relating to the Yumble project.
  2. The issue must follow the Issue Schema.

Issue Approval Process:

  1. Someone other than the creator ensures that all Issue Criteria has been met.
  2. Leave A comment informing the creator whether the criteria has been met.
  3. If it has not been met then proper feedback will be given to the creator in the comments.
  4. If the criteria has been meet the reviewer will leave a positive comment and move the issue into the "TO DO" column on the project board.

Yumble Wiki

  1. Yumble Code of Conduct
  2. Yumble Contribution Guide

Setting up the project

  1. Setup your Mongo Atlas
  2. Local MongoDB guide

Team Processes

GitHub Help

  1. GitHub Basics
  2. Fork & Pull workflow

Issue Creation, Review & Approval

  1. Issue Review & Approval process
  2. Project Labels
  3. Issue schema
  4. Bug Report Template

Pull Requests

  1. Pull Request Reviews

Testing

  1. Testing

Technical Documentation

  1. Yumble Architecture
  2. API Contracts
  3. API template
  4. Socket Architecture
  5. Working with Google Maps JavaScript API

Group documentation

  1. Project Contributors
  2. Table of Contributions
  3. Meeting Minutes
  4. Mistakes made
  5. Group 4 Contributions

Clone this wiki locally