From 231aad635dbd4f92393012c231044eeab8b21485 Mon Sep 17 00:00:00 2001 From: fatima-malik99 <7223fatimamalik@gmail.com> Date: Wed, 25 Dec 2024 12:07:56 +0500 Subject: [PATCH 1/8] updated meeting agendas --- collaboration/communication.md | 117 ++++++++++++++++++++++++++------- 1 file changed, 94 insertions(+), 23 deletions(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index 02c0a184..b4ded30b 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -7,41 +7,112 @@ you can share the rest in confidence with you group by another channel --> -# Communication - -______________________________________________________________________ +# Communication Plan ## Communication Schedule +This is the schedule for each week, it'll be changed every week. + +| Day | How | The topic of discussion | +|-----------|:----:|-------------------------| +|Monday |Zoom | | +|Tuesday |Zoom | | +|Wednesday |Zoom |GitHub Issues and Pull requests + Discuss and choose problems. | +|Thursday |Zoom | | +|Friday |Zoom | | +|Saturday |Zoom | | +|Sunday |Zoom | | -| Day | How | The topic of discussion | | --- | :-: | ----------------------- | -| | | | +--- ## Communication Channels -how often will we get in touch on each channel, and what we will discuss there: +All the technical disussions will be done on slack. But for general discussions we will use Whtsapp -- **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 +- **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 - -| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | | ------- | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: | -**Madiha**| Monday ✓| Tuesday ✓| Wednesday ✓| Thursday ✓| Friday ✓| Saturday ✓| Sunday ✓| | - -### How many hours everyone has per day +### Availability for Calling/Messaging + +| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | +|----------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| +| **Madiha** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| **Fatima** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | + +### How Many Hours Everyone Has Per Day + +- Fatima: _5h_ +- Name: _6h_ +- Madiha: _5h_ +- Name: _4h_ +- Name: _3h_ + +--- + +## Meeting Agendas and Records + +### Previous Meetings + +#### Meeting 1 +- **Date:** 20-12-2024 +- **Discussion Topics:** + - Introduction + - Team Norms + - Strategies for tackeling project + +- **Decisions Made:** + - Decided 7 team norms. + - Study google documents. + +#### Meeting 2 +- **Date:** 21-12-2024 +- **Discussion Topics:** + - Finalising group norms. + - Team name +- **Decisions Made:** + - Finalised 10 norms + - Git it Done- team name decided + - First commit made on github + +#### Meeting 3 +- **Date:** 22-12-2024 +- **Discussion Topics:** + - Discussion on assigned Google docs + - Guiding new members of team +- **Decisions Made:** + - Official work will be started from 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] -- name: _5h_; -- name: _6h_; -- Madiha: _5h_; -- name: _4h_; -- name: _3h_; ## Asking for Help From 5f63132072add5da6d4973d12d04f617b701837f Mon Sep 17 00:00:00 2001 From: fatima-malik99 <7223fatimamalik@gmail.com> Date: Wed, 25 Dec 2024 12:25:00 +0500 Subject: [PATCH 2/8] Fix markdown linter errors --- collaboration/communication.md | 108 ++++++++++++++++++--------------- 1 file changed, 59 insertions(+), 49 deletions(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index b4ded30b..cd644f5c 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -1,32 +1,33 @@ # Communication Plan ## Communication Schedule -This is the schedule for each week, it'll be changed every week. - -| Day | How | The topic of discussion | -|-----------|:----:|-------------------------| -|Monday |Zoom | | -|Tuesday |Zoom | | -|Wednesday |Zoom |GitHub Issues and Pull requests + Discuss and choose problems. | -|Thursday |Zoom | | -|Friday |Zoom | | -|Saturday |Zoom | | -|Sunday |Zoom | | + +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 Requests + Discuss and choose problems | +| Thursday | Zoom | | +| Friday | Zoom | | +| Saturday | Zoom | | +| Sunday | Zoom | | --- ## Communication Channels -All the technical disussions will be done on slack. But for general discussions we will use Whtsapp +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 @@ -39,18 +40,18 @@ All the technical disussions will be done on slack. But for general discussions ### Availability for Calling/Messaging -| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | -|----------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| -| **Madiha** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| **Fatima** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | +|-----------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| +| **Madiha** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| **Fatima** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -### How Many Hours Everyone Has Per Day +### Hours Available Per Day - Fatima: _5h_ -- Name: _6h_ - Madiha: _5h_ -- Name: _4h_ -- Name: _3h_ +- Member 1: _6h_ +- Member 2: _4h_ +- Member 3: _3h_ --- @@ -59,67 +60,76 @@ All the technical disussions will be done on slack. But for general discussions ### Previous Meetings #### Meeting 1 + - **Date:** 20-12-2024 - **Discussion Topics:** - - Introduction - - Team Norms - - Strategies for tackeling project + - Introduction + - Team Norms + - Strategies for tackling the project - **Decisions Made:** - - Decided 7 team norms. - - Study google documents. + - Decided on 7 team norms. + - Study Google Documents. #### Meeting 2 + - **Date:** 21-12-2024 - **Discussion Topics:** - - Finalising group norms. + - Finalizing group norms - Team name + - **Decisions Made:** - - Finalised 10 norms - - Git it Done- team name decided - - First commit made on github + - 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 members of team + - Discussion on assigned Google Docs + - Guiding new team members + - **Decisions Made:** - - Official work will be started from tomorrow. + - Official work to start tomorrow. #### Meeting 4 + - **Date:** 23-12-2024 - **Discussion Topics:** - - Pull requests - - Branches + - Pull requests + - Branches + - **Decisions Made:** - - Tasks assigned to each team member. - - Explore more about pull requests and branches - - Explore issues on github. + - 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 + +- **Date:** 25-12-2024 - **Discussion Topics:** - [Point 1] - [Point 2] + - **Decisions Made:** - [Decision 1] - [Decision 2] + - **Action Items:** - [Action 1] - [Action 2] +--- ## 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 -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 From d4e85ff15e34c29d7f221be9ebda5f28f61c98ca Mon Sep 17 00:00:00 2001 From: Muhammad Shahroz <114472614+Shahroz657@users.noreply.github.com> Date: Fri, 27 Dec 2024 02:33:03 +0500 Subject: [PATCH 3/8] Update communication.md --- collaboration/communication.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index cd644f5c..002ec949 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -44,12 +44,13 @@ All technical discussions will be conducted on Slack. General discussions will u |-----------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| | **Madiha** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | **Fatima** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | +| **Shahroz** | ✓ | ✓ | ✓ | ✓ | | | ✓ | ### Hours Available Per Day - Fatima: _5h_ - Madiha: _5h_ -- Member 1: _6h_ +- M Shahroz: _4h_ - Member 2: _4h_ - Member 3: _3h_ From c1692692db35792dbd4f422a654a9b3a3b317fc4 Mon Sep 17 00:00:00 2001 From: Madiha Malikzada Date: Sat, 28 Dec 2024 02:20:45 +0530 Subject: [PATCH 4/8] Fix CI errors by addressing linting and formatting issues --- collaboration/communication.md | 55 ++++++++++----------- collaboration/constraints.md | 89 +++++++++++++++++++++------------- 2 files changed, 82 insertions(+), 62 deletions(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index 002ec949..f03f5fea 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -2,9 +2,9 @@ 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. + 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 Plan @@ -13,21 +13,22 @@ 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 Requests + Discuss and choose problems | -| Thursday | Zoom | | -| Friday | Zoom | | -| Saturday | Zoom | | -| Sunday | Zoom | | +| 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 | | --- ## Communication Channels -All technical discussions will be conducted on Slack. General discussions will use WhatsApp. +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 @@ -40,19 +41,19 @@ All technical discussions will be conducted on Slack. General discussions will u ### Availability for Calling/Messaging -| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | -|-----------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| +| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | +|------------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| | **Madiha** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | **Fatima** | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | -| **Shahroz** | ✓ | ✓ | ✓ | ✓ | | | ✓ | +| **Shahroz**| ✓ | ✓ | ✓ | ✓ | | | ✓ | ### Hours Available Per Day -- Fatima: _5h_ -- Madiha: _5h_ -- M Shahroz: _4h_ -- Member 2: _4h_ -- Member 3: _3h_ +- **Fatima**: _5h_ +- **Madiha**: _5h_ +- **M Shahroz**: _4h_ +- **Member 2**: _4h_ +- **Member 3**: _3h_ --- @@ -67,7 +68,6 @@ All technical discussions will be conducted on Slack. General discussions will u - Introduction - Team Norms - Strategies for tackling the project - - **Decisions Made:** - Decided on 7 team norms. - Study Google Documents. @@ -78,7 +78,6 @@ All technical discussions will be conducted on Slack. General discussions will u - **Discussion Topics:** - Finalizing group norms - Team name - - **Decisions Made:** - Finalized 10 norms. - Decided on the team name: "Git it Done." @@ -90,7 +89,6 @@ All technical discussions will be conducted on Slack. General discussions will u - **Discussion Topics:** - Discussion on assigned Google Docs - Guiding new team members - - **Decisions Made:** - Official work to start tomorrow. @@ -100,7 +98,6 @@ All technical discussions will be conducted on Slack. General discussions will u - **Discussion Topics:** - Pull requests - Branches - - **Decisions Made:** - Tasks assigned to each team member. - Explore more about pull requests and branches. @@ -116,11 +113,9 @@ All technical discussions will be conducted on Slack. General discussions will u - **Discussion Topics:** - [Point 1] - [Point 2] - - **Decisions Made:** - [Decision 1] - [Decision 2] - - **Action Items:** - [Action 1] - [Action 2] @@ -129,8 +124,10 @@ All technical discussions will be conducted on Slack. General discussions will u ## 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 +3. _60+ min_: Tag your coaches in Slack or GitHub diff --git a/collaboration/constraints.md b/collaboration/constraints.md index a6c02893..065e7b4a 100644 --- a/collaboration/constraints.md +++ b/collaboration/constraints.md @@ -2,72 +2,95 @@ # 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 **These factors outside our control influence how we work on this project.** + - **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, documentation, and clear variable name). -- **Deadlines:** - - Projects must be finished at 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. + - 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, + 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. +- **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. ## Internal Constraints: Involuntary -**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, and documentation. - - Some members may require more time or support to complete tasks. + +**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, + and documentation. + - Some members may require more time or support to complete tasks. + - **Availability:** - - Team members may have different schedules and commitments, limiting synchronous collaboration opportunities. -- Technical Skills: - - Limited familiarity with tools like Git, GitHub workflows, or unit testing frameworks. + - Team members may have different schedules and commitments, limiting + synchronous collaboration opportunities. +- **Technical Skills:** + - Limited familiarity with tools like Git, GitHub workflows, or unit testing + frameworks. ## Internal Constraints: Voluntary -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. + - 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: - Problem description. - Approach and thought process. - Test cases used. + - **Communication Protocols:** - Use GitHub Issues to discuss problems and tasks. - At least one other member must review pull requests before merging. - Constructive feedback is required for all reviews. + - **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. + - 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. From 52e0b896c6dd5078ace54503889757018c4a7486 Mon Sep 17 00:00:00 2001 From: Muhammad Shahroz Date: Sat, 28 Dec 2024 04:56:48 +0500 Subject: [PATCH 5/8] Fixed mardown formatting issues --- collaboration/README.md | 48 +++++++++++++++++++++++++++++------------ 1 file changed, 34 insertions(+), 14 deletions(-) diff --git a/collaboration/README.md b/collaboration/README.md index 6abd0d6e..09a13cce 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -3,48 +3,68 @@ ## 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. + +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. +- 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. +- 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. + +- 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. +- 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. + +- 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. +- 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. From 11e3cb360532072f66583b5963e3dd3d17ff6663 Mon Sep 17 00:00:00 2001 From: Muhammad Shahroz Date: Sat, 28 Dec 2024 05:12:39 +0500 Subject: [PATCH 6/8] Upadated with markdown errors fixed --- .github/ISSUE_TEMPLATE/help_wanted.md | 2 +- .github/ISSUE_TEMPLATE/new_challenge.md | 3 ++- .github/PULL_REQUEST_TEMPLATE.md | 4 ++-- LICENSE | 2 +- README.md | 13 ++++++++++--- collaboration/communication.md | 6 ++++-- collaboration/guide/0_repository_setup.md | 3 ++- solutions/abcd.py | 2 -- 8 files changed, 22 insertions(+), 13 deletions(-) delete mode 100644 solutions/abcd.py diff --git a/.github/ISSUE_TEMPLATE/help_wanted.md b/.github/ISSUE_TEMPLATE/help_wanted.md index 2ee010f2..134efead 100644 --- a/.github/ISSUE_TEMPLATE/help_wanted.md +++ b/.github/ISSUE_TEMPLATE/help_wanted.md @@ -14,7 +14,7 @@ labels: "help wanted" - assign: anyone you would like help from --> -## The Code +# The Code diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 330a04cb..7d9ab3be 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -12,9 +12,9 @@ about: A template PR for code review with a checklist -## Behavior +# Behavior -### Files +## Files - [ ] The file name describes the function's behavior - [ ] There is a module docstring in the function file diff --git a/LICENSE b/LICENSE index 6e628e40..d04b0351 100644 --- a/LICENSE +++ b/LICENSE @@ -1,4 +1,4 @@ -MIT License +# MIT License Copyright (c) 2024 MIT Emerging Talent diff --git a/README.md b/README.md index 3807226f..7be07991 100644 --- a/README.md +++ b/README.md @@ -1,12 +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: +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. +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. . +We are learning collaboratively, growing through our mistakes, and working as a +team to improve. . diff --git a/collaboration/communication.md b/collaboration/communication.md index 60ab49de..e98c57a9 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -33,9 +33,11 @@ ______________________________________________________________________ | Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | | ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: | -**Madiha**| Monday ✓| Tuesday ✓| Wednesday ✓| Thursday ✓| Friday ✓| Saturday ✓| Sunday ✓| | +**Madiha**| Monday ✓| Tuesday ✓| Wednesday ✓| Thursday ✓ +| Friday ✓| Saturday ✓| Sunday ✓| | -**Shahroz**| Monday ✓| Tuesday ✓| Wednesday ✓| Thursday ✓| Sunday ✓| | +**Shahroz**| Monday ✓| Tuesday ✓| Wednesday ✓| Thursday ✓| +Sunday ✓| | ### How many hours everyone has per day diff --git a/collaboration/guide/0_repository_setup.md b/collaboration/guide/0_repository_setup.md index 4044fe97..4b968900 100644 --- a/collaboration/guide/0_repository_setup.md +++ b/collaboration/guide/0_repository_setup.md @@ -14,7 +14,8 @@ repository and configure it for collaboration: - Change your [repository description](https://stackoverflow.com/questions/7757751/how-do-you-change-a-repository-description-on-github) - Add or remove topics from your repository - - Update your main README with your group name and an initial overview of your project. (You can change this as much as you want.) + - Update your main README with your group name and an initial overview of your + project. (You can change this as much as you want.) - Under settings in your repository select: - _Issues_ - _Discussions_ diff --git a/solutions/abcd.py b/solutions/abcd.py deleted file mode 100644 index 739dfd80..00000000 --- a/solutions/abcd.py +++ /dev/null @@ -1,2 +0,0 @@ -# this is an example file -print("example") From c723797a478c961846d4318f9da9c3bc55fbf01e Mon Sep 17 00:00:00 2001 From: Muhammad Shahroz Date: Sat, 28 Dec 2024 05:21:07 +0500 Subject: [PATCH 7/8] Add placeholder test --- solutions/tests/test_placeholder.py | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 solutions/tests/test_placeholder.py diff --git a/solutions/tests/test_placeholder.py b/solutions/tests/test_placeholder.py new file mode 100644 index 00000000..7dca2c23 --- /dev/null +++ b/solutions/tests/test_placeholder.py @@ -0,0 +1,8 @@ +import unittest + +class PlaceholderTest(unittest.TestCase): + def test_placeholder(self): + self.assertTrue(True) + +if __name__ == "__main__": + unittest.main() From d86da5369d7dacc93cecdcd6e13e88c4701453b0 Mon Sep 17 00:00:00 2001 From: Muhammad Shahroz Date: Sat, 28 Dec 2024 05:33:15 +0500 Subject: [PATCH 8/8] Fixed formatting erorrs --- solutions/tests/test_placeholder.py | 8 -------- 1 file changed, 8 deletions(-) delete mode 100644 solutions/tests/test_placeholder.py diff --git a/solutions/tests/test_placeholder.py b/solutions/tests/test_placeholder.py deleted file mode 100644 index 7dca2c23..00000000 --- a/solutions/tests/test_placeholder.py +++ /dev/null @@ -1,8 +0,0 @@ -import unittest - -class PlaceholderTest(unittest.TestCase): - def test_placeholder(self): - self.assertTrue(True) - -if __name__ == "__main__": - unittest.main()