451 Communication Plan
| Platform | Purpose(s) | Time | Participants |
|---|---|---|---|
| Face to face | (Lab hour) | Tuesday 15:00 - 17:00 | Team members |
| Face to face | (Lecture hour) | Tuesday 13:00 - 14:00 | Team members |
| Zoom | Regular weekly meetings | Thursday 20:00 - 21:00 | Team members |
| GitHub | Organizing project development | Anytime needed | Team members |
| Slack | Formal communication platform | Anytime needed | Team members |
| Casual chit-chatting platform | Anytime needed | Team members |
Session Structure:
- Each week, a different member from the group will take the notes.
- The session will start with discussing the questions and agenda.
- A review of that week’s work will be conducted.
- The action items for the next week will be discussed and written.
Rules for documentation, usage and communication in GitHub:
- All meeting notes, project documents, and important resources will be stored in the GitHub repository.
- Meeting notes (except labs) will be named YYYY-MM-DD_Meeting-Notes.md
- All significant decisions and their rationales will be documented in the meeting notes.
- GitHub Pull Request reviews should be completed within 12-24 business hours.
- All development work for a new feature or bug fix should be done in a separate branch, not directly on the main branch.
- Code will be merged into the main branch only via a Pull Request. At least one other team member must review and approve the PR before merging.
