Test file for the test_three_sum

.github/ISSUE_TEMPLATE/help_wanted.md

@@ -14,7 +14,7 @@ labels: "help wanted"
   - assign: anyone you would like help from
 -->
 
-## The Code
+# The Code
 
 <!--
   The code you have a question about (it doesn't need to be your code!). This can

.github/ISSUE_TEMPLATE/new_challenge.md

@@ -13,7 +13,8 @@ about: >
 -->
 
 <!-- 
-  Describe the challenge's _behavior_ so someone can start solving it without asking for clarification.
+  Describe the challenge's _behavior_ so someone can start solving it without 
+  asking for clarification.
   Do not describe a _strategy_ or an _implementation_!  
   Others are free to solve the behavior however they like.
 -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -12,9 +12,9 @@ about: A template PR for code review with a checklist
 
 <!-- describe the challenge you will solve -->
 
-## Behavior
+# Behavior
 
-### Files
+## Files
 
 - [ ] The file name describes the function's behavior
 - [ ] There is a module docstring in the function file

LICENSE

@@ -1,4 +1,4 @@
-MIT License
+# MIT License
 
 Copyright (c) 2024 MIT Emerging Talent
 

README.md

@@ -0,0 +1,19 @@
+# Git it Done  
+
+## Overview  
+
+Welcome to the **Git it Done** repository!  
+
+This is a collaborative learning project where our team works together to solve
+problems and learn new skills. Each teammate will:  
+
+- Solve 2 problems.  
+- Help resolve 2 problems contributed by others.  
+
+Our team is made up of people with different levels of experience—some of us are
+complete beginners, while others have a little experience. But one thing we all
+share is a strong eagerness to learn. By the end of this project, we will no longer
+ be complete beginners.  
+
+We are learning collaboratively, growing through our mistakes, and working as a
+team to improve.  .  

collaboration/README.md

@@ -2,4 +2,69 @@
 
 <!-- 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 -->
+
+### 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.
+
+### 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.
+
+### 3. Technical Meetings
+
+- 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.
+
+### 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.
+
+### 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.
+
+### 7. Create a Safe Feedback Culture
+
+- 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.
+
+### 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.
+
+### 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.