From 85af9219701c6996420a052c8f2582f840c00c87 Mon Sep 17 00:00:00 2001
From: Abel Mesfin Teka <tekaabel04@gmail.com>
Date: Wed, 8 Jan 2025 20:22:00 +0300
Subject: [PATCH 1/3] Robel notes included

---
 notes/First meeting note.md | 111 ++++++++++++++++++++++++++++++++++++
 1 file changed, 111 insertions(+)
 create mode 100644 notes/First meeting note.md

diff --git a/notes/First meeting note.md b/notes/First meeting note.md
new file mode 100644
index 000000000..926452201
--- /dev/null
+++ b/notes/First meeting note.md	
@@ -0,0 +1,111 @@
+# Group Task: Writing and Reviewing Explanations
+
+## Meeting Overview
+
+During our meeting, we were tasked with reviewing and practicing documentation writing. To ensure an organized approach, we followed a structured process. Here's how we proceeded
+
+---
+
+## Writing Explanations
+
+1. **Select a Topic:**
+   - Choose a topic from the list below.
+   - Mark your selected topic with `[ ]` in the checkbox next to it.
+2. **Claim Your Topic:**
+   - Create a comment on your topic's line.
+   - Write your name at the top of the comment so everyone knows who is working on which explanation.
+3. **Write the Explanation:**
+   - Include the following details in your comment:
+     - **What is it?**
+     - **How is it used?**
+     - **What collaboration challenges does it address?**
+4. **Indicate Completion:**
+   - When your explanation is complete, update the checkbox to `[O]` to signal it's ready for review.
+5. **Repeat the Process:**
+   - If all topics marked `[O]` are under review, select a new topic and write another explanation.
+
+---
+
+## Reviewing Explanations
+
+1. **Select an Explanation to Review:**
+   - Find a topic marked `[O]` for review.
+2. **Claim the Review Task:**
+   - Update the checkbox to `[...O]` and add a comment with your name, indicating you are reviewing this explanation.
+3. **Perform the Review:**
+   - Check the explanation for:
+     - Accuracy and clarity.
+     - Correct spelling and grammar (use [Grammar Check](https://www.grammarcheck.net/editor/)).
+   - Discuss any questions or improvements with the author in the comment.
+4. **Finalize and Document:**
+   - Once the explanation is ready, copy-paste it into the main document ("Things Explained") under a Level 2 heading.
+   - Mark the checkbox with `[X]` to indicate completion.
+
+---
+
+## Proofreading the Document
+
+1. **Collaborative Proofreading:**
+   - Once all explanations are added to the main document, proofread it as a group.
+2. **Discussion:**
+   - Reflect on the writing process and ensure:
+     - Every topic from the list is included in the document.
+     - Each explanation makes sense to the entire group.
+
+---
+
+## Stand-Up Questions
+
+Be prepared to answer the following questions during the main group call:
+
+- What went well?
+- What went less well?
+- What did you learn as a group?
+
+---
+
+## Challenges in Collaborative Writing
+
+- Shared Understanding
+- Communication
+- Task Division
+- Task Tracking
+- Proofreading
+- Reassembling
+- Merge Conflicts
+- Backtracking
+
+---
+
+## Topics to Explain
+
+For each item, write a short explanation covering:
+
+- **What it is.**
+- **How it’s used.**
+- **Which collaboration challenges it helps address.**
+
+### Topic List
+
+- [X] Project Methodologies (Agile, Scrum, …)
+- [X] Command Line Interface / Terminal
+- [X] Git
+- [X] GitHub
+- [X] GitHub Repository
+- [O] GitHub Issues
+- [O] Project Boards
+- [X] Pull Requests
+- [ ] Continuous Integration (CI)
+- [O] Code Review
+
+---
+
+## Things Explained
+
+(Insert completed explanations here.)
+
+---
+
+## How We Completed the Task
+
+To complete the task effectively, we divided the topics among group members and prepared the explanations accordingly. Each member followed the above steps to write, review, and finalize the explanations.

From 6121731c26710e508aa8e8492a7ec2779dce168f Mon Sep 17 00:00:00 2001
From: Abel Mesfin Teka <tekaabel04@gmail.com>
Date: Wed, 8 Jan 2025 20:27:18 +0300
Subject: [PATCH 2/3] is linting fixed

---
 notes/{First meeting note.md => frst_meeting_note.md} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename notes/{First meeting note.md => frst_meeting_note.md} (100%)

diff --git a/notes/First meeting note.md b/notes/frst_meeting_note.md
similarity index 100%
rename from notes/First meeting note.md
rename to notes/frst_meeting_note.md

From d984e3a58c6be8a7771082d98718aa48dd4ff233 Mon Sep 17 00:00:00 2001
From: Abel Mesfin Teka <tekaabel04@gmail.com>
Date: Thu, 9 Jan 2025 14:39:43 +0300
Subject: [PATCH 3/3] update 1

---
 notes/frst_meeting_note.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/notes/frst_meeting_note.md b/notes/frst_meeting_note.md
index 926452201..487d6adf7 100644
--- a/notes/frst_meeting_note.md
+++ b/notes/frst_meeting_note.md
@@ -92,11 +92,11 @@ For each item, write a short explanation covering:
 - [X] Git
 - [X] GitHub
 - [X] GitHub Repository
-- [O] GitHub Issues
-- [O] Project Boards
+- [X] GitHub Issues
+- [X] Project Boards
 - [X] Pull Requests
 - [ ] Continuous Integration (CI)
-- [O] Code Review
+- [X] Code Review
 
 ---