Add files via upload-Pyramid

README.md

@@ -0,0 +1,36 @@
+# Push and Pray
+
+Welcome to the repository of **Push and Pray**, standing for Group 19 in the MIT
+Emerging Talent Program.
+
+![alt text](unit-tests.jpg)
+
+## Meet The Team 🌟
+
+- Ahmed Khalifa: A second-rate meme lord, but a first-class code reviewer.
+  No detail escapes his eye, and no cricket
+  goes unacknowledged when he drops a punchline. 🔎
+
+- Dadi Ishimwe: Or Daddy, the Rwandan that can do basically anything
+  (many people told him to change his name). 🎯
+
+- Mahmoud Alnouri: THE supreme Data Analyst, master of spreadsheets and
+  high priest of tables, at your service. 📈
+
+- Mohammad R. Al Salloum: Coding is his first language. Says “I bend electrons”,
+  sounds so cool (probably bending him back now). ⚡
+
+- Mukuna Kabeya (aka Paul): One name is cool, two names are legendary -
+  Mukuna/Paul choose what you want. 🕶️
+
+- Raed Eleyan: THE Expert, He thinks he's just a bro, but he's actually a pro.
+  That's why his name means 'pioneer' in Arabic. 🏆
+
+- Rama Arafeh: THE keen biologist who never uses GUI, but she would steal your DNA
+  sample and plant it at a crime scene without you noticing. 🧬
+
+- Tamara Saqer: A first-rate meme queen, her creativity is out of this world.
+  If she earned a dollar for every meme she created,
+  she would be a multimillionaire. 💰
+
+## Let's design something extraordinary together. 😎

collaboration/README.md

@@ -1,5 +1,78 @@
 # Collaboration
 
 <!-- group norms summary -->
+Our goal is to create a family-like, friendly, and collaborative work environment.
+We value open and honest communication without fear of judgment and ensure everyone
+ can finish their thoughts without interruption. We treat everyone with kindness
+  and respect, offering help proactively when needed. We encourage collaboration
+  by sharing knowledge, skills, and resources,
+   and focus on solutions rather than blame when challenges arise.
+   We prioritize transparency,
+    empathy, and accountability to build a culture of trust.
+    We encourage open
+     discussions to understand diverse
+      perspectives and use structured debates for effective decision-making.
+     We commit to clear, respectful,
+      and timely communication,
+       ensuring the chosen platform suits the purpose and context.
+      Meetings will have clear agendas,
+       start and end on time, and respect everyone’s contributions and availability.
+        We provide constructive,
+        specific, and respectful feedback, focusing on mutual growth and improvement.
+         We create a collaborative atmosphere
+          where every member feels valued, heard, and empowered to contribute.
 
 <!-- group norms list -->
+Our goal is to create a family-like, friendly, and collaborative work environment.
+
+---
+
+## **Communication Norms**
+
+- Encourage open and honest communication without fear of judgment.
+- Avoid interrupting others during meetings; let everyone finish their thoughts.
+- Trust: We prioritize transparency,
+   empathy, and accountability to build a culture of trust.
+
+- Balanced Discussions:
+  We encourage open discussions
+   to understand diverse perspectives and use structured debates for effective decision-making.
+
+- Effective Communication: We commit to clear, respectful, and timely communication,
+  ensuring the chosen
+  platform suits the purpose and context.
+
+- Respect Time: Meetings will have clear agendas,
+   start and end on time, and respect everyone’s contributions and availability.
+
+- Constructive Feedback: We provide constructive,
+   specific, and respectful feedback, focusing on mutual growth and improvement.
+
+- Inclusivity: We create a collaborative
+   an atmosphere where every member feels valued, heard, and empowered to contribute.
+
+---
+
+## **Respect and Support**
+
+- Treat everyone with kindness and respect
+- Offer help proactively when someone is struggling with a task.
+- Recognize and appreciate the contributions and ideas shared by others.
+
+---
+
+## **Collaboration and Accountability**
+
+- Encourage collaboration by sharing knowledge, skills, and resources.
+- Focus on solutions, not blame, when challenges arise.
+- Take responsibility for your assignments and ensure commitments are met on time.
+
+---
+
+## **Positive Environment**
+
+- Express gratitude by regularly appreciating the contributions of your teammates.
+- Make memes to add humor and foster a light-hearted, enjoyable atmosphere
+in the team.
+- Show that every team member's voice matters.
+- Recognize team achievements publicly.

collaboration/communication.md

@@ -9,46 +9,67 @@
 
 # Communication
 
-______________________________________________________________________
-
 ## Communication Schedule
 
-| Day | How | The topic of discussion | | --- | :-: | ----------------------- |
-| | | |
+| Day       | How                 | The Topic of Discussion     |
+|-----------|---------------------|-----------------------------|
+| Monday    | Google Meet/Slack   | Goal Setting               |
+| Tuesday   | Google Meet/Slack   | Code Review                |
+| Wednesday | Google Meet/Slack   | Code Review and Help       |
+| Thursday  | Google Meet/Slack   | Progress Update            |
+| Friday    | Google Meet/Slack   | Code Review and Help       |
+| Saturday  | Google Meet/Slack   | Code Review and Help       |
+| Sunday    | Google Meet/Slack   | Progress Update            |
 
 ## Communication Channels
 
-how often will we get in touch on each channel, and what we will discuss there:
-
-- **Issues**:
-- **Pull Requests**:
-- **Slack/Discord**:
-- **Video Calls**:
+We will always be in touch to discuss various things:
 
-______________________________________________________________________
+- **Issues**: For bugs, progress checking, and other related tasks.
+- **Pull Requests**: For code reviews and Markdown file updates.
+- **Slack**: For daily updates, notifications, and reporting any code
+  errors or help needed.
+- **Video Calls**: For group discussions, progress updates, tutoring, and meetings.
+- **WhatsApp**: For informal hangouts and check-ins and sending reminders.
 
 ## Availability
 
-### Availability for calling/messaging
+### Availability for Calling
+
+| Member   | Monday | Tuesday | Wednesday | Thursday | Friday  | Saturday | Sunday|
+|----------|------------|------------|------------|------------|------------|------------|------------|
+| Dadi     | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm|
+| Rama     | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm |  - |
+| Ahmed    | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm|
+| Mohammad | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm|
+| Tamara   | 5 - 6pm | 5 - 6pm | 5 - 6pm | 5 - 6pm | 5 - 6pm | 5 - 6pm | 5 - 6pm|
+| Raed     | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm|
+| Mahmoud | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm|
+| Mukuna | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm | 5 - 8pm|
+
+### How Many Hours Everyone Has Per Day on Average
 
-| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |
------- | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: |
-| _name_ | | | | | | | |
+- **Dadi**: 4 hours
+- **Rama**: 4 hours
+- **Ahmed**: 4 hours
+- **Mohammad**: 3 hours
+- **Tamara**: 1 hour
+- **Raed**: 2 hours
+- **Mahmoud**: 3 hours
+- **Mukuna**: 3 hours
 
-### How many hours everyone has per day
+---
 
-- name: _5h_;
-- name: _6h_;
-- name: _5h_;
-- name: _4h_;
-- name: _3h_;
+This README is structured to ensure a clear understanding of our communication
+strategy and availability. Time frames are flexible as they can be adjusted
+over Slack or WhatsApp.
 
 ## 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
-1. _30 -> 60 min_: Ask your group for help
-1. _60+ min_: Tag your coaches in Slack or GitHub
+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