challenge/count characters

.github/workflows/ci-checks.yml

@@ -4,19 +4,19 @@ on: [push, pull_request, workflow_dispatch]
 
 jobs:
   ls_linting:
-      runs-on: ubuntu-latest
-      steps:  
-        - uses: actions/checkout@v4
-        - uses: ls-lint/action@v2.2.3
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ls-lint/action@v2.2.3
 
   md_formatting:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v4
-    - uses: nosborn/github-action-markdown-cli@v3.3.0
-      with:
-        files: .
-        config_file: .markdownlint.yml
+      - uses: actions/checkout@v4
+      - uses: nosborn/github-action-markdown-cli@v3.3.0
+        with:
+          files: .
+          config_file: .markdownlint.yml
 
   py_formatting:
     runs-on: ubuntu-latest
@@ -44,11 +44,11 @@ jobs:
         if: always()
       - name: install pylint
         run: |
-          python -  m pip install --upgrade pip
+          python -m pip install --upgrade pip
           pip install pylint
         shell: bash
       - name: Python - Check Linting - pylint
-        run: "pylint solutions tests  || echo '::warning title=Pylint Error(s)::Discuss solutions and trade-offs in code review.'"
+        run: "pylint solutions tests || echo '::warning title=Pylint Error(s)::Discuss solutions and trade-offs in code review.'"
         shell: bash
 
   py_tests:
@@ -59,22 +59,12 @@ jobs:
       - name: python version
         run: python --version
         shell: bash
-      
+
       - name: Check for test files
         id: check_tests
         run: |
-          test_files=$(find ./solutions/tests -type f -name "test_*.py")
-          if [ -n "$test_files" ]; then
-            echo "Found test files:"
-            echo "$test_files"
-            echo "has_tests=true" >> $GITHUB_OUTPUT
-          else
-            echo "No test files found matching pattern ./solutions/tests/test_*.py"
-            echo "has_tests=false" >> $GITHUB_OUTPUT
-          fi
-        shell: bash
-
+
       - name: Python - Run Tests
         if: steps.check_tests.outputs.has_tests == 'true'
-        run: python -m unittest
+        run: echo "PYTHONPATH=$GITHUB_WORKSPACE" >> $GITHUB_ENV
         shell: bash

.markdownlint.yml

@@ -1,3 +1,9 @@
 ignore:
   - venv
   - .github
+
+
+MD013:
+  line_length: 180
+  ignore_urls: true
+

.vscode/settings.json

@@ -119,8 +119,6 @@
     "editor.defaultFormatter": "charliermarsh.ruff",
     "editor.formatOnSave": true,
     "editor.codeActionsOnSave": {
-      "source.fixAll.ruff": "explicit",
-      "source.organizeImports.ruff": "explicit"
     }
   }
 }

README.md

@@ -0,0 +1,48 @@
+# Collab Coders
+
+> Welcome to the **Collab Coders** repository! 🚀  
+We are a team of passionate Junior developers From MET.
+> dedicated to building impactful solutions through collaboration and innovation.
+
+---
+
+## 🌟 About Us
+
+> At **Collab Coders**, we believe in the power of teamwork:
+
+- to tackle complex challenges and create meaningful projects.
+- This repository serves as a hub for our collaborative efforts.
+- where ideas turn into reality.
+
+---
+
+## 📂 Repository Structure
+
+Here’s how the repository is organized:
+
+- `main`: The primary branch containing stable and reviewed code.
+- `feature-branches`: Each team member has their own branch
+- for working on features or tasks.
+- Branches are named after it is functionality for clarity
+- (e.g., `challenges/factorial-function`, `challenges/sort-list`).
+
+---
+
+## 🛠️ Technologies Used
+
+> Our team use stack of tools and technologies
+> based on the program specifications and requirements:
+
+- **Languages**: Python, Markdown  
+- **Frameworks**: N/A
+- **Tools**: Github,Git, VS Code  
+- **Communication_channels**: Slack, Google Meet, Zoom, Whatsapp  
+
+---
+
+## 🌱 How to Contribute
+
+1. Clone the repository:  
+
+   ```bash
+   git clone <repository_url>

collaboration/README.md

@@ -2,4 +2,156 @@
 
 <!-- group norms summary -->
 
+## Group norms for ET6-Foundation-group-09's project
+
+**These group norms will serve as the guidelines and directives, everyone is expected to comply with,
+yet no repercussions will follow if they are disregarded.**
+
+## Communication
+
+### Primary communication channel
+
+Slack
+
+WhatsAPP
+
+GitHub
+
+Zoom Meeting
+
+Google meet
+
+#### Response Time
+
+Everyone is expected to response to the messages on all the communication channels within 24 hours.
+
+#### Language of communication
+
+The official language of communication is English, and we strongly recommend using clear, concise language, avoid using jargon.
+
+#### Official Meeting platforms
+
+Zoom Meeting
+
+Google Meet
+
+The group meeting will be conducted on the official platforms at least once in the week which can be adjusted based on group demands.
+
+The  time will be discussed and agreed by all the participants on slack and WhatsAPP.
+
+All the meetings are expected to last for one hour.
+
+The recording will be made available after the meeting and uploaded to the group channels, it will be helpful to the participants who missed the meeting.
+
+All the participants who missed the meeting are advised to watch the recording before sharing their opinions.
+
+## Group Organization
+
+**The team organization will ensure effective communication among the group members, making informed decisions
+and ensuring that everyone is working on the same goal.**
+
+### Organizational Structure
+
+### Project lead
+
+### Responsibilities
+
+Oversees the project, ensuring timely completion and making sure no member is left behind.
+
+The project lead has no absolute authority over the group members.
+
+Coordinates the resolution of key issues and pull requests
+
+### Head of the project Communication
+
+### Key Responsibilities
+
+Discussion management on Github and WhatsAPP
+
+Schedule and control the group meeting
+
+### Deputy Head of the project Communication
+
+Assist the Head of communication in implementing communication plan
+
+Provides supports to group members, helping in resolving issues and answering questions.
+
+### Technical lead
+
+Assist in code review and conflict resolution
+
+### Collaboration Norms
+
+### collaboration Tools
+
+Github
+
+Git
+
+Visual Code Studio (VS Code)
+
+### Task Assignment
+
+Each team member will assign him/her self to the task using Github issues
+
+Everyone is expected to work individually and push it to the branch upon completion
+
+### Code Review
+
+Team members will review and provide feedback on each others's code within 48 hours
+
+we anticipate everyone bear in mind that we are reviewing codes not individuals.
+
+### Branching and Merging
+
+we will use feature branches and pull request to manage different version of codes
+
+## Conflict Resolution
+
+### Open Communication
+
+All the members are expected to communicate their concerns and challenges
+
+### Constructive Feedback
+
+We encourage the culture of constructive feedback and respectful criticism
+
+Remember we are reviewing codes not people
+
+### Conflict resolution process
+
+All sorts of conflict and misunderstanding shall be resolved through open discussion and mutual understanding
+
+## Respect and Inclusion
+
+### Equality
+
+All the group members have equal rights and their opinion must be respected.
+
+We equal participation from all the group members.
+
+### Respectful Communication
+
+Group members are expected to communicate respectful and professionally by avoiding offensive language.
+
+### Decision Making
+
+All the team members will have their voices in decision making.
+
+### Diversity
+
+We endeavor to create an inclusive environment that fosters diversity.
+
 <!-- group norms list -->
+
+## Groups Norms List
+
+Communication Norms
+
+Organization norms
+
+Collaboration Norms
+
+Conflict Resolution Norms
+
+Respect and Inclusion Norms

collaboration/communication.md

@@ -7,41 +7,44 @@
         you can share the rest in confidence with you group by another channel
 -->
 
-# Communication
+# Communication 📬
 
 ______________________________________________________________________
 
 ## Communication Schedule
 
-| Day | How | The topic of discussion | | --- | :-: | ----------------------- |
+| Day & Time | How | The topic of discussion |
+| --- | :-: | ----------------------- |
+|Every Friday, 9 EST| Google Meet| Activity Updates|
 | | | |
 
 ## 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**:
+- **Issues**: To track team progress, update as needed, and assign tasks where needed
+- **Pull Requests**: Reviewed within 48 hours for feedback, approving the change and merging it to the main branch
+
+- **Slack**: For daily task updates and resolving small problems from team members
+- **Video Calls**: Zoom/Google meet preferably for general group meetings and weekly updates
 
 ______________________________________________________________________
 
 ## Availability
 
-### Availability for calling/messaging
-
-| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |
------- | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: |
-| _name_ | | | | | | | |
-
-### How many hours everyone has per day
-
-- name: _5h_;
-- name: _6h_;
-- name: _5h_;
-- name: _4h_;
-- name: _3h_;
+### Availability for calling/messaging(+how many hours each day in EST)
+
+| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday |
+|:------ | :----: | :-----: | :-------: | :------: | :----: | :------: | ----: |
+|  Hiba | 9-12     |  9-12       |    9-12    |    9-12     |   9-12    |     9-12   |   9-12   |
+| Jeffery |   9-12    |    9-12     |    9-12    |     9-12   |   9-12   |    9-12    |   9-12  |
+| Kelvin |         |          |          |            |          |          |                   |
+| Mahdia |     9-12  |     9-12   |     10-12   |    10-12    |    9-12   |   9-12   |   10-12  |
+| Martha |   9-12      |   9-12       |   9-12       |   9-12      | 9-12     | 9-12    | 9-12  |
+| Osei |   10-13      |11-15          | 9-12         |  9-12        | 9-15    |  13-15   |  9-15|
+| Rina |         |   7-15       |          |    7-15      | 7-15       |  9-15     |  9-15      |
+| Terry |    9-11     | 9-11         |  9-11        |    6-9      | 9-11       |  9-12  | 9-11  |
+| Yool |    9-12     | 9-12         | 10-13    |   8-12    |  9-12      |  10-13  | 10-13       |
 
 ## Asking for Help