Fixed constraints

README.md

@@ -16,4 +16,4 @@ share is a strong eagerness to learn. By the end of this project, we will no lon
  be complete beginners.  
 
 We are learning collaboratively, growing through our mistakes, and working as a
-team to improve.  .  
+team to improve. 

collaboration/README.md

@@ -1,70 +1,73 @@
 # Collaboration
 
-<!-- group norms summary -->
-
 ## Summary of Norms
 
-Our goal is to create a collaborative environment where everyone feels
- comfortable asking questions and working together. We will start with the basics,
-  progress toward project goals, and remain respectful, helpful, and connected
-   throughout the journey.
-<!-- group norms list -->
+Our goal is to create a collaborative environment where everyone feels  
+comfortable asking questions and working together. We will start with  
+the basics, progress toward project goals, and remain respectful, helpful,  
+and connected throughout the journey.
 
 ### 1. Encourage Open and Respectful Communication
 
-- Ensure all members feel heard and valued in discussions.
-- Prioritize clear and constructive communication, encouraging everyone to share
- their ideas and perspectives without fear of judgment or interruption.
+- Ensure all members feel heard and valued in discussions.  
+- Prioritize clear and constructive communication, encouraging everyone  
+  to share their ideas and perspectives without fear of judgment or  
+  interruption.
 
 ### 2. Balance Discussion and Debate
 
-- Promote productive collaboration through thoughtful discourse.
-- Use discussions to generate ideas and debates to critically evaluate them while
- maintaining respect and focusing on project goals.
+- Promote productive collaboration through thoughtful discourse.  
+- Use discussions to generate ideas and debates to critically evaluate  
+  them while maintaining respect and focusing on project goals.
 
 ### 3. Technical Meetings
 
-- Use **Slack** for technical discussions and project updates.
+- Use **Slack** for technical discussions and project updates.  
+
 - Use **WhatsApp** for urgent matters and quick clarifications.
 
 ### 4. Reminders for Code Review
 
-- To ensure timely code reviews, feel free to send a friendly reminder on Slack
- or WhatsApp when necessary.
-- Encourage team members to notify the requester once the code review is completed.
+- To ensure timely code reviews, feel free to send a friendly reminder  
+  on Slack or WhatsApp when necessary.  
+- Encourage team members to notify the requester once the code review  
+  is completed.
 
 ### 5. Handling Delays and Meeting Attendance
 
-- Meetings will start as scheduled to respect everyone's time.
-- If unable to attend, members should share their situation in advance and catch
- up via recordings.
+- Meetings will start as scheduled to respect everyone's time.  
+- If unable to attend, members should share their situation in advance  
+  and catch up via recordings.
 
 ### 6. Maintain a Positive Team Environment
 
-- Avoid rude or mean behavior.
-- If any interaction causes discomfort, address it respectfully to resolve the
- issue and foster understanding.
+- Avoid rude or mean behavior.  
+- If any interaction causes discomfort, address it respectfully to resolve  
+  the issue and foster understanding.
 
 ### 7. Create a Safe Feedback Culture
 
-- Encourage constructive feedback to improve team performance.
+- Encourage constructive feedback to improve team performance.  
+
 - Focus on solutions rather than blame when giving or receiving feedback.
 
 ### 8. Clear Handoffs When Required
 
-- If there are delays in completing tasks, inform the team promptly to prevent
-further delays.
-- Minimize dependency issues by clearly communicating expectations and timelines
- when tasks require input or dependencies from another member.
+- If there are delays in completing tasks, inform the team promptly to  
+  prevent further delays.  
+- Minimize dependency issues by clearly communicating expectations and  
+  timelines when tasks require input or dependencies from another member.
 
 ### 9. Respect for Different Work Styles
 
-- Foster individuality while ensuring progress.
-- Respect that everyone has a unique working style, provided deliverables are
- submitted on time and meet agreed standards.
+- Foster individuality while ensuring progress.  
+- Respect that everyone has a unique working style, provided deliverables  
+  are submitted on time and meet agreed standards.
 
 ### 10. Responsiveness and Accountability
 
-- While everyone has different schedules, acknowledging messages on Slack or
-WhatsApp—even with a brief reply—helps keep the team informed and connected.
-- This ensures smooth collaboration and demonstrates respect for everyone’s efforts.
+- While everyone has different schedules, acknowledging messages on  
+  Slack or WhatsApp—even with a brief reply—helps keep the team  
+  informed and connected.  
+- This ensures smooth collaboration and demonstrates respect for  
+  everyone’s efforts.

collaboration/communication.md

@@ -1,135 +1,42 @@
-<!--
-    This template is for inspiration. Feel free to change it however you like!
 
-    Careful! Be sure to protect your privacy when filling out this document.
-    Everything you write here will be public, so share only what you are
-    comfortable sharing online. You can share the rest in confidence with your
-    group by another channel.
--->
+# Communication Channels
 
-# Communication Plan
+How often will we get in touch on each channel, and what we will discuss there:
 
-## Communication Schedule
-
-This is the schedule for each week, and it will be updated weekly.
-
-| Day       | How  | The topic of discussion                    |
-|-----------|:----:|-------------------------------------------|
-| Monday    | Zoom |                                           |
-| Tuesday   | Zoom |                                           |
-| Wednesday | Zoom | GitHub Issues and Pull Request Discussion |
-| Thursday  | Zoom |                                           |
-| Friday    | Zoom |                                           |
-| Saturday  | Zoom |                                           |
-| Sunday    | Zoom |                                           |
+- **Issues**: Adding availability to the schedule.
+- **Pull Requests**: Reviewing each other's code and giving feedback.
+- **Slack/Discord**: Email, Slack, and WhatsApp.
+- **Video Calls**: Zoom and Google Meet.
 
 ---
 
-## Communication Channels
 
 All technical discussions will be conducted on Slack. General discussions will
 use WhatsApp.
 
-- **Issues**: Adding availability to the schedule  
-- **Pull Requests**: Reviewing each other's code and giving feedback  
-- **Slack/Discord**: Email, Slack, and WhatsApp  
-- **Video Calls**: Zoom and Google Meet  
-
----
-
-## Availability
-
 ### Availability for Calling/Messaging
-<!-- Ignored the max line length cause it it looks good in this way -->
-| Day        | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday|
-|------------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:|
-| **Madiha** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-
-| **Fatima** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-
-| **Shahroz**| ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-
-### Hours Available Per Day
-
-- **Fatima**: _5h_  
-- **Madiha**: _5h_  
-- **M Shahroz**: _4h_  
-- **Member 2**: _4h_  
-- **Member 3**: _3h_  
-
----
-
-## Meeting Agendas and Records
-
-### Previous Meetings
 
-#### Meeting 1
+| Day    | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday|
+|--------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------|
+| **Madiha** |   ✓   |    ✓  |     ✓   |    ✓     |    ✓   |    ✓     |    ✓|
+| **Shahroz**|   ✓|    ✓    |     ✓    |    ✓     |        |    ✓     |    ✓ |
 
-- **Date:** 20-12-2024  
-- **Discussion Topics:**  
-  - Introduction  
-  - Team Norms  
-  - Strategies for tackling the project  
-- **Decisions Made:**  
-  - Decided on 7 team norms.  
-  - Study Google Documents.  
+### How Many Hours Everyone Has Per Day
 
-#### Meeting 2
-
-- **Date:** 21-12-2024  
-- **Discussion Topics:**  
-  - Finalizing group norms  
-  - Team name  
-- **Decisions Made:**  
-  - Finalized 10 norms.  
-  - Decided on the team name: "Git it Done."  
-  - First commit made on GitHub.  
-
-#### Meeting 3
-
-- **Date:** 22-12-2024  
-- **Discussion Topics:**  
-  - Discussion on assigned Google Docs  
-  - Guiding new team members  
-- **Decisions Made:**  
-  - Official work to start tomorrow.  
-
-#### Meeting 4
-
-- **Date:** 23-12-2024  
-- **Discussion Topics:**  
-  - Pull requests  
-  - Branches  
-- **Decisions Made:**  
-  - Tasks assigned to each team member.  
-  - Explore more about pull requests and branches.  
-  - Explore issues on GitHub.  
-
----
-
-### Upcoming Meetings
-
-#### Meeting 5
-
-- **Date:** 25-12-2024  
-- **Discussion Topics:**  
-  - [Point 1]  
-  - [Point 2]  
-- **Decisions Made:**  
-  - [Decision 1]  
-  - [Decision 2]  
- **Action Items:**  
-  - [Action 1]  
-  - [Action 2]  
-
----
+- **Shahroz**: 4h.
+- **[Name]**: 6h.
+- **Madiha**: 5h.
+- **[Name]**: 4h.
+- **[Name]**: 3h.
 
 ## Asking for Help
 
-There's a fine line between confidently learning from your mistakes and
-stubbornly getting nowhere. Here is a general guide for when to ask for help
-based on how long you've been stuck on the same problem:
+There's a fine line between confidently learning from your mistakes
+and stubbornly
+getting nowhere. 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
+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.

collaboration/constraints.md

@@ -1,18 +1,16 @@
-<!-- This template is for inspiration, feel free to change it however you like! -->
-
 # Constraints
 
-This section outlines the boundaries and considerations for our project to ensure
-smooth collaboration, efficient learning, and effective task completion.
+This section outlines the boundaries and considerations for our project
+to ensure smooth collaboration, efficient learning, and effective task completion.
 
 ## External Constraints
 
 <!--
   Constraints coming from the outside that your team has no control over:
-  - Project deadlines
-  - Number of unit tests required to pass a code review
-  - Technologies (sometimes a client will tell you what to use)
-  - Power or connectivity
+  - project deadlines
+  - number of unit tests required to pass a code review
+  - technologies (sometimes a client will tell you what to use)
+  - power or connectivity
   - ...
 -->
 
@@ -21,29 +19,30 @@
 - **Platform Requirements:**
   - Problems must be selected from the workshop's exercises, CodeWars, LeetCode,
     or similar coding platforms.
-  - Solutions must comply with the workshop's requirements (e.g., unittest,
+
+  - Solutions must comply with the workshop's requirements (e.g., unit tests,
     documentation, and clear variable names).
 
 - **Deadlines:**
-  - Projects must be completed within the timeline set by the MIT Emerging Talent
-    program.
-  - Each member must solve and review problems within the agreed-upon time frames.
+  - Projects must be completed according to the timeline set by the MIT Emerging
+    Talent program.
+  - Each member must solve and review problems within the agreed-upon timeframes.
 
 - **Tools and Resources:**
   - GitHub must be used for version control, communication, and documentation.
-  - The team must rely on publicly available resources (e.g., online tutorials
-    and documentation) to enhance learning.
+  - The team must rely on publicly available resources (e.g., online tutorials and
+    documentation) to enhance learning.
+
 
 ## Internal Constraints: Involuntary
 
 <!--
   Constraints that come from within your team, and you have no control over:
-  - Each of your individual skill levels
-  - Amount of time available to work on the project
+  - each of your individual skill levels
+  - amount of time available to work on the project
 -->
 
-**These are limitations or challenges within the team that we need to navigate
-effectively.**
+**These are limitations or challenges within the team that we need to navigate effectively.**
 
 - **Experience Levels:**
   - Team members have varying levels of experience in programming, unit testing,
@@ -61,22 +60,23 @@
 ## Internal Constraints: Voluntary
 
 <!--
-  Constraints that your team decided on to help scope the project. They may 
-  include:
-  - Coding style & conventions
-  - Agree on a code review checklist for the project repository
-  - The number of hours you want to spend working
-  - Only using the colors black and white
+  Constraints that your team decided on to help scope the project.
+  They may include:
+  - coding style & conventions
+  - agreeing on a code review checklist for the project repository
+  - the number of hours you want to spend working
+  - only using the colors black and white
 -->
 
-**These are self-imposed rules or boundaries designed to improve collaboration and
-learning outcomes.**
+**These are self-imposed rules or boundaries designed to improve collaboration
+and learning outcomes.**
 
 - **Unit Testing:**
-  - All submitted solutions must include unit tests to verify correctness and
-    edge cases.
-  - Use Python’s unittest module (or equivalent) for testing.
+  - All submitted solutions must include unit tests to verify correctness and edge
+    cases.
+  - Use Python’s `unittest` module (or equivalent) for testing.
+
 
 - **Documentation Standards:**
   - All code must include meaningful comments explaining the logic.
   - Problem solutions must include documentation with:
@@ -92,5 +92,6 @@
 - **Collaborative Learning:**
   - Each member must share insights or challenges they faced during problem-solving
     to help others learn.
-  - Regular check-ins (via GitHub comments or virtual meetings) to ensure
-    alignment.
+
+  - Regular check-ins (via GitHub comments or virtual meetings) to ensure alignment.
+