update to communication.md

collaboration/README.md

@@ -1,11 +1,11 @@
 # Collaboration
 
-## Group “ET6-foundations-group-10”
+## Group “ZeroThroughTen”
 
-The group is focused on professional communication in developing the _**''“ET6-foundations-group-10”**_ project to implement the _Foundations Track_ syllabus of the [_MIT Emerging Talent_](https://emergingtalent.mit.edu/) program.
+TThe group is focused on professional communication in developing the _**''“ZeroThroughTen”**_ project to implement the _Foundations Track_ syllabus of the [_MIT Emerging Talent_](https://emergingtalent.mit.edu/) program.
 
 ### Norms of the group
 
-1. We try to communicate on a professional level on issues related to the project  “ET6-foundations-group-10” development and implementation of the Foundations Track syllabus of the MIT Emerging Talent program. We do not touch on issues of personal characteristics, religious beliefs, political views, or level of competence.
-2. We communicate asynchronously using Slack and GitHub tools, so our communication needs to be documented and other group members can view the subject of the communication, the discussion itself, and the results of the communication.
+1. We try to communicate on a professional level on the issues related to the project development and implementation according to the Foundations Track syllabus of the MIT Emerging Talent program. We do not touch on issues of personal characteristics, religious beliefs, political views, or level of competence.
+2. We communicate asynchronously using Slack and GitHub tools, so our communication needs to be documented to allow other group members to view the subject of the communication, the discussion itself, and the results of the communication.
 3. All group meetings are scheduled in advance so that other group members can organize their time. All group communication is documented. Personal communication can take place online.

collaboration/communication.md

@@ -9,46 +9,74 @@
 
 # Communication
 
-______________________________________________________________________
+---
 
 ## Communication Schedule
 
-| Day | How | The topic of discussion | | --- | :-: | ----------------------- |
-| | | |
+| **Day**       | **How**                        | **Topic of Discussion**             |
+|---------------|--------------------------------|-------------------------------------|
+| Flexible      | Slack (Daily)                 | Quick updates, general communication |
+| Twice a week  | Google Meet                   | Progress updates, task discussions, and important decisions |
+
+---
 
 ## Communication Channels
 
-how often will we get in touch on each channel, and what we will discuss there:
+### Frequency and topics for each channel
+
+- **Slack**:  
+  - **Purpose**: Daily communication, task updates, and sharing quick announcements.
+  - **Frequency**: Regularly active for asynchronous communication.
+
+- **Google Meet**:  
+  - **Purpose**: Discuss progress, blockers, and important milestones.
+  - **Frequency**: Twice per week or as needed based on the project phase.
 
-- **Issues**:
-- **Pull Requests**:
-- **Slack/Discord**:
-- **Video Calls**:
+- **GitHub Issues**:  
+  - **Purpose**: Track tasks, report bugs, and plan milestones.
+  - **Frequency**: Active for task management.
 
-______________________________________________________________________
+- **GitHub Pull Requests**:  
+  - **Purpose**: Code reviews and collaboration.
+  - **Frequency**: Notified via Slack when a review is needed.
+
+---
 
 ## Availability
 
-### Availability for calling/messaging
+### Team's General Availability
+
+The team works asynchronously due to different time zones and schedules. To facilitate effective communication:
+
+- Meeting times are determined by a poll or decided during prior meetings.
+- Members are encouraged to stay active on Slack to ensure timely updates.
+- Meetings are recorded when possible, and summaries are shared for those unable to attend.
 
-| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |
------- | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: |
-| _name_ | | | | | | | |
+### Response Time
 
-### How many hours everyone has per day
+- **Messages**: Responses on Slack are expected within **12 hours**.
+- **Code Reviews**: Pull requests are reviewed within **24 hours** whenever possible.
 
-- name: _5h_;
-- 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:
+Here’s a general guide for when to ask for help if you’re stuck:
+
+1. **0 -> 30 minutes**: Try solving the problem independently using available resources.
+2. **30 -> 60 minutes**: Reach out to the group via Slack for input or support.
+3. **60+ minutes**: If still unresolved, tag a coach or mentor on Slack or GitHub.
+
+### Key Note
+
+Don’t hesitate to ask for help when needed. Collaboration is about supporting each other to achieve the project goals.
+
+---
+
+## Meeting Agendas
+
+Meeting agendas will be created before each scheduled meeting:
 
-1. _0 -> 30 min_: Try on your own
-1. _30 -> 60 min_: Ask your group for help
-1. _60+ min_: Tag your coaches in Slack or GitHub
+- Agendas are drafted using GitHub Issues, where members can add discussion points.
+- Meeting minutes and action items are recorded and shared in the issue comments or via Slack.
+- All agenda points are addressed before closing the meeting issue.