Decide as a team when you will be able to meet, and how you'll stay in touch between meetings. The example in this repository gives some ideas for organizing this file, but it's up to your group to find what works best for you.
This step may seem simple but it's soooo important. HYF projects go by very quickly, often you'll only have one week to plan and build a whole website! Taking a few extra minutes to plan this on Monday (or even Sunday right after class) can save you a day or two of confusion over the week.
Here's a template you can copy-paste into /planning/communication.md.
# Communication
## Group Rules
<!-- any general rules you'd like to set for your group? -->
---
## Communication Schedule
| Day | How | The topic of discussion |
| --- | :-: | ----------------------- |
| | | |
## Communication Channels
how often will we get in touch on each channel, and what we will discuss there:
- **Issues**:
- **Pull Requests**:
- **GitHub Discussions**
- **Slack/Discord**:
- **Video Calls**:
---
## Availability
### Availability for calling/messaging
| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday |
| ------ | :-----: | :-----: | :-------: | :------: | :-----: | :------: | :-----: |
| _name_ | 13 - 20 | 13 - 20 | 13 - 20 | 13 - 20 | 13 - 20 | 13 - 20 | 13 - 20 |
### How many hours everyone has per day
- name: _5h_; extra comments?
- name: _6h_;
- name: _5h_;
- name: _4h_;
- name: _3h_;
## Asking for Help
There's a fine line between confidently learning from your mistakes, and
stubbornly getting no where. Here is a general guide for when to ask for help
based on how long you've been stuck on the same problem:
1. _0 -> 30 min_: Try on your own
2. _30 -> 60 min_: Ask your group for help
3. _60+ min_: Tag your coaches in Slack or GitHub