Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experment #6

Closed
Closed
Changes from 9 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# 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. .
45 changes: 45 additions & 0 deletions collaboration/README.md
Original file line number Diff line number Diff line change
@@ -2,4 +2,49 @@

<!-- group norms summary -->

## Summary of Norms

Check failure on line 5 in collaboration/README.md

GitHub Actions / md_formatting

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## 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

Check failure on line 9 in collaboration/README.md

GitHub Actions / md_formatting

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### 1. Encourage Open and Respectful Communication"]
- Ensure all members feel heard and valued in discussions.

Check failure on line 10 in collaboration/README.md

GitHub Actions / md_formatting

Lists should be surrounded by blank lines [Context: "- Ensure all members feel hear..."]
- Prioritize clear and constructive communication, encouraging everyone to share their ideas and perspectives without fear of judgment or interruption.

### 2. Balance Discussion and Debate

Check failure on line 13 in collaboration/README.md

GitHub Actions / md_formatting

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### 2. Balance Discussion and Debate"]
- Promote productive collaboration through thoughtful discourse.

Check failure on line 14 in collaboration/README.md

GitHub Actions / md_formatting

Lists should be surrounded by blank lines [Context: "- Promote productive collabora..."]
- Use discussions to generate ideas and debates to critically evaluate them while maintaining respect and focusing on project goals.

### 3. Technical Meetings

Check failure on line 17 in collaboration/README.md

GitHub Actions / md_formatting

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### 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.


1 change: 1 addition & 0 deletions solutions/abcd.py
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
print("example")