Meetings & Communication Protocol
Effective communication is the backbone of the Inky project. We utilize a mix of full-team synchronizations and ad-hoc sub-team meetings to maintain momentum during our 1–2 week sprints.
Meeting Cadence
We categorize our meetings into two primary types based on attendance and scope:
1. Full Team Sync (Sprint Meetings)
- Frequency: Every 1 to 2 weeks (aligned with Sprint cycles).
- Platform: Discord (Internal) or Microsoft Teams (Official Epitech Reviews).
- Purpose:
- Refine Objectives: Adjust project direction based on recent findings.
- Monitor Progress: Review the status of current issues.
- Assign Tasks: Distribute work for the upcoming sprint.
2. Sub-Team Syncs
- Frequency: Ad-hoc / As needed.
- Platform: Discord.
- Purpose: Dedicated to specific developers working on shared components to resolve technical blockers or pair-program.
Meeting Logs & Archives
Transparency is key. All major decisions and sprint updates discussed in full team meetings are documented on our internal blog.
View Meeting Archives: You can access the history of our meeting minutes and sprint summaries here: Meeting Logs (Blog)
What to Log
For every Full Team Sync, the following must be recorded in the blog post:
- Date & Attendees.
- Agenda Items.
- Decisions Made.
- Tasks Assigned (Links to GitHub Issues).
Communication Channels
| Platform | Usage Context |
|---|---|
| Discord | Day-to-day communication, internal voice chat, and sub-team collaboration. |
| Microsoft Teams | Official meetings with Epitech mentors and formal reviews. |
| GitHub Issues | Task-specific discussions and technical clarifications. |
Meeting template
---
slug: meeting-YYYY-MM-DD
title: Meeting Notes - [Date]
authors: [author-name]
tags: [meeting]
date: YYYY-MM-DD
---
# Meeting Notes: [Date]
**Location:** [Discord / Microsoft Teams]
**Type:** [Sprint Planning / Progress Review / Epitech Mentor Meeting]
## 1. Progress review
### Decisions Made
## 2. New Objectives
## 3. Open Discussion / Notes