54 maximum length of a concatenated string with unique characters

README.md

@@ -0,0 +1,30 @@
+# 👋 Welcome: This is ⚡`PyRectifiers`⚡Group
+
+🚀 **"Alone we can do so little; together, we can achieve so much."**
+
+## We made this repository to practice what we learn in the `MIT Foundational Track`
+
+``` text
+💡 Our Vision:
+To collaborate, innovate, and deliver impactful solutions.
+This repository serves as our central hub for all documentation,
+project discussions, and code contributions.
+```
+
+### ⭐ Key Objectives
+
+* Contribute meaningful 2 challenges at least, and review peers'  
+code for continuous improvements.
+
+### 📂 Repository Structure
+
+* **`main`**: The primary branch containing stable and reviewed code.
+* **`collaboration/`**: Contain our group's learning goals, constrains, and
+  scheduling our team's meeting.
+* **`notes/`**: Project's and team's notes.
+* **`solutions/`**: Python solutions and corresponding test files for coding challenges.
+
+### ✨ Our Journey
+
+Our team's key insights, learnings, and collaborative decision-making processes:
+Documented all in [`collaboration/`](https://github.com/MIT-Emerging-Talent/ET6-foundations-group-25/tree/main/collaboration)

collaboration/README.md

@@ -1,5 +1,43 @@
-# Collaboration
+# 🐍 We're the PyRectifiers 🛠️  
 
-<!-- group norms summary -->
+## *We're here to rectify your Pythons!*
 
-<!-- group norms list -->
+---
+
+## 📜 Group Norms  
+
+### ⏰ Respecting Each Other’s Time  
+
+- **Meetings** will be scheduled **at least one day a week**.
+- **Additional Meetings** will be scheduled **48-hours** beforehand.  
+- 🗳️ **Meeting times** will be voted on in Slack the day before.  
+
+### 📡 Communication  
+
+- **Maintain communication** on Slack—let’s keep the discussions flowing! 💬  
+- Feel free to **ask for help**; we’re here to support each other! 🙌  
+
+### 🗓️ Meetings  
+
+- **Prepare for meetings** with pre-defined agendas beforehand.  
+- **Use Google Meet** for a smoother meeting experience. 🎥  
+- **Weekly milestones** will help us track progress. 🏁  
+- **Internal milestone** will be Jan. 7 ⏱
+
+### 🏗️ Repository Management  
+
+- Follow **naming conventions** for challenges that reflect their behavior.
+- Preferably, the branches/issues will be named as *"GP25_challenge-name"*  
+- Choose **1 or 2 people** to handle repository updates to ensure consistency.  
+
+### 🔧 Collaboration Tips  
+
+- Stay **active on Slack** to stay in the loop and contribute effectively. 🖇️  
+- Let’s make meetings productive and focused to avoid unnecessary delays.  
+
+---
+
+## 🤝 Together, We’ll Rectify Pythons! 🐍✨  
+
+With great communication, preparation, and teamwork?
+We’ll keep things rectified—just like PyRectifiers should! 🎉

collaboration/communication.md

@@ -1,54 +1,69 @@
-<!--
-    this template is for inspiration, feel free to change it however you like!
+# Communication
 
-    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 you group by another channel
--->
+## Communication Schedule
 
-# Communication
+| Day        | How              | The topic of discussion                       |
+|------------|------------------|-----------------------------------------------|
+| All        | Slack            | Various discussions                           |
+| Sunday     | Zoom/Google Meet | Introducing ourselves; Discussing Group Norms |
+|(22/12/2024)|                  |                                               |
+| Tuesday    | Google Meet      | Discussing the Challenges (with a Demo)       |
+|(24/12/2024)|                  |                                               |
+| Friday     |Google Meet       | Discussing the Collaboration Documents,       |
+|(27/12/2024)|                  | assigning members, discussing the Challenges, |
+|            |                  | and working on the repository                 |
+| Thursday   | Google Meet      | Discussing the work progress                  |
+|(02/01/2025)|                  |                                               |
 
 ______________________________________________________________________
 
-## Communication Schedule
+## Communication Channels
 
-| Day | How | The topic of discussion | | --- | :-: | ----------------------- |
-| | | |
+How often will we get in touch on each channel, and what we will discuss there:
 
-## Communication Channels
+- **Issues**:  
+  - **Frequency**: As needed.  
+  - **Purpose**: To track tasks, assign the responsibilities, and report the bugs.
 
-how often will we get in touch on each channel, and what we will discuss there:
+- **Pull Requests**:  
+  - **Frequency**: Daily.  
+  - **Purpose**: To share the codes and documents, review the contributions,
+    and approve changes.
 
-- **Issues**:
-- **Pull Requests**:
-- **Slack/Discord**:
-- **Video Calls**:
+- **Slack**:  
+  - **Frequency**: Daily.  
+  - **Purpose**: To ask questions and provide answers, and to update the group members
+    on the work and the meetings.
+
+- **Video Calls**:  
+  - **Frequency**: As discussed (often, twice a week).  
+  - **Purpose**: To discuss the collaborative work in detail, and to organize
+  and plan the upcoming steps and future work.
 
 ______________________________________________________________________
 
 ## Availability
 
 ### Availability for calling/messaging
-
-| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |
------- | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: |
-| _name_ | | | | | | | |
+<!-- markdownlint-disable MD013 -->
+| Days                    | Monday  | Tuesday  | Wednesday  | Thursday  | Friday  | Saturday  | Sunday  |
+|-------------------------|:-------:|:--------:|:----------:|:---------:|:-------:|:---------:|:-------:|
+| Amin Abd Elraheem       | 9am-2pm | 9am-2pm  | 9am-2pm    | 9am-2pm   | 9am-2pm | 9am-2pm   | 9am-2pm |
+| Mohamed Saeed           | 9am-3pm | 9am-3pm  | 9am-3pm    | 9am-3pm   | 9am-3pm | 9am-3pm   | 9am-3pm |
+| Name                    | ...     | ...      | ...        | ...       | ...     | ...       | ...     |
 
 ### How many hours everyone has per day
 
-- name: _5h_;
-- name: _6h_;
-- name: _5h_;
-- name: _4h_;
-- name: _3h_;
+- Amin Abd Elraheem: _5hrs_  
+- Mohamed Saeed: _6hrs_  
+- Name: _...hrs_  
 
 ## 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:
+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
-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.  
+2. **30 -> 60 min**: Ask your group for help.  
+3. **60+ min**: Tag your coaches in Slack or GitHub.

collaboration/constraints.md

@@ -1,34 +1,62 @@
-<!-- this template is for inspiration, feel free to change it however you like! -->
 
 # Constraints
 
-Some boundaries around our project.
+---
+
+This file reflects some boundaries and challenges that may face our group and project
 
 ## External
 
-<!--
-  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
-  - ...
--->
+These are constraints coming from the outside and we (as a team)
+have no control over, for example:
+
+- **Project deadlines**
+  - The project must be completed within 3 weeks, with a clear
+  deadline for each deliverable.
+- **Programming Language: Python**
+  - Python will be used to build the project. No other languages
+   or frameworks will be used.
+- **Version Control with GitHub:**
+  - The code related to the project has to be pushed to the GitHub
+   repository And pull requests should be reviewed before merging.
+- **Testing Framework: Unittest**
+  - For testing purposes, the project will use unittest for Python.
+   And no other testing libraries or frameworks will be introduced.
+- **Documentation Standards:**
+  - During the project, all code should have clear and concise
+   documentation (using docstrings).
+- **Team Size:**
+  - A team of 10 members will work on this project.
+  All members will be expected to collaborate.
 
 ## Internal: 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
--->
+These are constraints that come from within our team and we have no
+control over but we can work on mitigating them:
+
+- **Skills level:**
+  - Team members have different levels of experience and
+  familiarity with programming, Git&GitHub.
+
+- **amount of time available to work on the project**
+  - Due to work or life responsibilities, each team member
+ has a different amount of time that he can use to work on this project.
+- **Communication issues**
 
 ## Internal: 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
--->
+These are the types of constraints that we’ve decided on to help scope the project.
+They include:
+
+- coding style & conventions
+- Follow the code review checklist for the project repository
+- The number of hours you want to spend working
+- Agreed to use Slack as the main communication channel
+- Agreed to use Google Meet for meetings
+- We may share the insights or challenges that we faced during problem-solving
+  to help others learn and reduce the potential time that may be wasted on debugging
+- Meeting Frequency and Duration:
+  - Group meetings should be held at least once a week for up to 1 hour. That said,
+  team availability will factor into scheduling and it’s expected that all team
+  members will participate.
+- Agreed on completing any outstanding tasks by **January** the **7th**.

collaboration/learning_goals.md

@@ -1,5 +1,93 @@
 # Learning Goals
 
-## Collective
+Our learning goals are categorized into two main areas: Focuses on Collective
+Goals, that is improving together as a team and Individual Goals helping
+individual areas of growth based on the aspirations of each member. This
+structured approach guarantees both group development and individual development
 
-## Individual
+## Collective Learning Goals
+
+Together we seek to build a collaborative development environment where we
+sharpen our technical and communication skills. Through practice and continuous
+learning, we aim to develop a strong foundation in software development and Python
+programming. Below are our key focus areas as a collective:
+
+1. Collaborative Development Skills
+
+    - Develop effective collaboration practices through GitHub workflows, including:
+        - **Issues**: Creating, tracking, and assigning tasks.
+        - **Pull Requests (PRs)**: Submitting, reviewing, and merging pull
+        requests to ensure code quality.
+        - **Merging**: Understanding different merge strategies and resolving conflicts.
+        - **Projects**: Organizing tasks and milestones using GitHub Projects
+        for visual tracking.
+        - **Branching**: Managing branches effectively to keep the repository
+        clean and organized.
+        - **GitHub CLI**: Managing repositories, pull requests, and issues from
+        the terminal.
+
+2. Effective Communication
+
+    - Enhance communication skills within the team through:
+        - **Slack**: Using Slack for group communication.
+        - **Regular Meetings**: Actively participating in group meetings and
+        discussions to ensure alignment on goals and progress.
+        - **Feedback and Collaboration**: Providing and receiving constructive
+        feedback in both code reviews and team discussions.
+
+3. Unit Testing
+
+    - Learn and integrate unit testing in Python using the `unittest` module.
+
+4. Code Review Process
+
+    - Develop an understanding of an effective code review process, including
+    giving and receiving constructive feedback to improve code quality.
+
+5. Efficient Development Practices
+
+    - Focus on becoming more efficient developers by improving workflows,
+    debugging techniques, and programming skills.
+
+6. Python Programming
+
+    - Strengthen Python programming skills by:
+        - Writing efficient and well-documented Python code.
+
+7. Docstring Documentation
+
+    - Learning the art of writing clear and concise docstrings to document code effectively.
+
+## Individual Learning Goals
+
+### *Alexander Andom*
+
+- *Learn New Data Structures*: Learn and implement new data structures that are
+unfamiliar or challenging.
+- *Improve Debugging Skills*: Develop strategies for debugging code and
+resolving issues more efficiently.
+- *Deepen Knowledge of Testing Frameworks*: Learn to use `unittest` in Python
+to write solid and detailed unit tests.
+
+### *Mohamed Saeed*
+
+- Mastering GitHub
+- To foster my programming skills
+- Improve my debugging skills
+
+### *Amin Abd Elraheem*
+
+- To Understand how to plan and execute projects on GitHub.
+- Transform Ideas into Programs
+
+### *Kefah Albashityalshaer*
+
+- Improve my programming skills in Python, especially in writing unit test programs
+- Mastering Code Review, making PRs, and the other GitHub teams' tasks.
+- Improve my communication with the team.
+
+### *Tamir El-Waleed*
+
+- Improve my testing skills, in addition to mastering basic Git & Github behavior.
+- Create a complete project from scratch, building my portfolio in the process.
+