Event Dates: November 10 - November 18

• Introduction to Open Source
• Why Participate?
• How to add Labels
• What You’ll Gain
• How to Handle Merge Conflicts
• Our Pledge
• Project List
• Code of Conduct
• Get Involved

IEEE IGDTUW Open Source Week is a week-long event aimed at fostering collaboration and skill-building in open-source. Participants can work on impactful projects, learn version control, and gain real-world experience while contributing to open-source communities. It’s a great opportunity to develop coding skills, connect with mentors, and make meaningful contributions.

Joining IEEE IGDTUW Open Source Week is a fantastic opportunity to:

• 💰 Win Exciting Cash Prizes: Compete for rewarding cash prizes!
• 🎁 Earn IEEE Goodies: Grab exclusive IEEE merchandise.
• 🏅 Get Annual IEEE Membership: Enjoy a year-long membership with IEEE and its benefits.
• 🚀 Enhance Your Skills: Build real-world coding and collaboration skills.
• 🌱 Make a Difference: Contribute to impactful projects with lasting value.
• 🤝 Expand Your Network: Connect with peers, mentors, and industry professionals.
• 🔧 Master Open-Source Tools: Gain hands-on experience with version control and open-source contributions.
• 📈 Boost Your Resume: Showcase your participation in an IEEE-led open-source event.

Don’t miss out on this opportunity to learn, contribute, and win!

Adding labels to issues and pull requests helps us organize and prioritize work efficiently. Follow these steps to add labels to any issue or pull request:

1️⃣ 👩‍💻 On GitHub, navigate to the main page of the repository.

2️⃣ 👀 Under your repository name, click Issues or Pull requests.

3️⃣ 📂 Above the list of issues or pull requests, click Labels.

4️⃣ 👩‍💻 To the right of the search field, click New label.

5️⃣ 💫 Now, you can create ieee-igdtuw label.

• Under "Label name", type a ieee-igdtuw
• Under "Description", type a description to help others understand and use your label.
• To customize the color of your label, edit the hexadecimal number. (#C08BE4)

6️⃣ 📌 To save the new label, click Create label.

7️⃣ 🎊 After following above steps, ieee-igdtuw label will be visible under Labels section.

1️⃣ 👩‍💻 Open the Issue or Pull Request

• Select the specific issue or pull request where you want to add labels.

2️⃣ 🌟 Access the Labels Section

• On the right sidebar of the issue or pull request page, find the Labels section.
• Click on the Labels dropdown to view the list of available labels.

3️⃣ 🎊 Choose a Label

• Scroll through the list and click on the label(s) you want to add.
• You can add multiple labels if necessary.
• Don't forget to add ieee-igdtuw label.

4️⃣ 🏆 Labels are added🎉

• Collaboration Skills: Work with others on shared projects.
• Version Control Mastery: Learn to manage code using Git and GitHub.
• Problem-Solving Abilities: Develop solutions in a supportive environment.
• Hands-On Learning: Gain experience working on impactful projects.

• Engage in real-world projects.
• Receive mentorship from experienced contributors.
• Gain hands-on experience with version control and project management.

1️⃣ Choose a Project: Browse the project list and select one you'd like to contribute to. Access the repository by clicking on its project link.

2️⃣ Fork the Repository: Once on the repository page, click the "Fork" button in the top-right corner to create a copy of the repository in your GitHub account.

3️⃣ Clone Your Fork: Clone your forked repository to your local machine with:

git clone https://github.com/your-username/repository-name.git

Replace your-username with your GitHub username and repository-name with the name of the repository.

4️⃣ Navigate to the Repository Directory:

cd repository-name

5️⃣ Create a Branch: Create a new branch for your feature or bug fix. Use a descriptive name for your branch:

git checkout -b your-feature-branch-name

6️⃣ Make Changes: Make your desired changes. Ensure that your code adheres to our coding standards and passes any tests.

7️⃣ Add Changes: Stage your changes for commit:

git add .

8️⃣ Commit Your Changes: Commit your changes with a clear and concise message:

git commit -m "Brief description of your changes"

9️⃣ Push to GitHub: Push your changes to your forked repository:

 git push origin your-feature-branch-name

🔟 Submit a Pull Request: Navigate to the original repository and submit a pull request from your branch. Provide a clear description of your changes and any relevant details.

Merge conflicts are a common part of collaboration in open source. They occur when multiple people make changes to the same lines of code in a file or when one contributor edits a file that another contributor has deleted. Understanding why they happen helps us approach conflicts with care and respect for others’ contributions.

1. Identify the conflicting files in your branch.
2. Open the files and locate the conflict markers:
   • <<<<<<< marks the beginning of your changes.
   • ======= separates your changes from others' changes.
   • >>>>>>> marks the end of the conflicting code.
3. Decide which changes to keep, either by integrating both sets of changes or choosing one. Then, remove the conflict markers to clean up the file.
4. Save the file, add it to the staging area, and commit your changes.

Note: When resolving a conflict, make sure not to delete other contributors’ code without reviewing it. Try to combine changes where possible to preserve everyone’s contributions.

Contributors should adhere to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

We pledge to:

• Foster a welcoming and inclusive environment for all contributors.
• Support each other in learning and growing as developers.
• Commit to creating a positive impact through our open-source contributions.