Open Source Beginner’s Guide for GSSoC Contributors

---

Author: Resham Saipranathi
GitHub: github.com/reshamsai150
LinkedIn: linkedin.com/in/saipranathi-resham-5a7921315

---

✨ Welcome to GirlScript Summer of Code (GSSoC)!

If you're new to open source, GSSoC is the perfect place to begin. This guide walks you through everything — from discovering issues to making your first pull request (PR).

---

📅 When Should You Start?

Timing is key! Here’s how to stay ahead:

• Before GSSoC starts:
  Follow interesting repositories, read their README.md, and understand the contribution guidelines.

• Once the program begins:
  Join project communication channels (Discord/Slack), stay active, and look for beginner-friendly issues labeled like:

  • good first issue

  • documentation

  • level1

---

🔧 Setting Up Your Local Environment

Here’s a quick setup checklist:

1. Create a GitHub account (if you don't already have one).

2. Fork the project repository.

3. Clone your fork locally:

    git clone <your-forked-repo-url>
    cd <repo-folder>
   

4. Set the upstream remote:

    git remote add upstream <original-repo-url>
   

5. Keep your fork updated:

    git fetch upstream
    git merge upstream/main
   

---

⚖️ Choosing the Right Issue

1. Head to the “Issues” tab of the repository.

2. Look for GSSoC-labeled issues:

   • level1: Easy

   • level2: Medium

   • level3: Hard

3. Comment to claim:
   "I’d like to work on this issue. Please assign it to me."

✅ Wait for the maintainers to assign the issue before working on it!

---

🚀 Start Working on the Issue

1. Create a new branch:

    git checkout -b issue-#<number>
   

2. Implement your fix or feature.

3. Test your changes locally.

4. Add screenshots or screen recordings if it's a UI-related task.

5. Stage and commit your changes:

    git add .
    git commit -m "Fixes: #<issue-number> - Short description"
   

6. Push your branch:

    git push origin issue-#<number>
   

---

🔗 Open Your First Pull Request (PR)

1. Go to your forked repository on GitHub.

2. Click “Compare & pull request.”

3. Write a clear title and description:

   • Mention the issue using Fixes #<issue-number>

   • Explain the changes you made

   • Attach relevant screenshots (if applicable)

4. Submit the PR and request reviewers (if required).

5. Wait for feedback or approval — and be open to making changes.

---

💰 Understanding the GSSoC Points System

Here’s how points are awarded:

🎯 Tip: Always check if your PR has the right labels — it directly affects your points!

---

🏆 What You Get from GSSoC

Besides learning, you’ll gain:

• 💻 Hands-on experience with real-world projects

• 📃 Certificate of participation

• 🎁 Swags & goodies (for top contributors)

• 🧑‍🤝‍🧑 Networking with mentors, devs, and community

• ✨ Recognition in the open-source world!

---

🔹 Pro Tips to Stand Out

• Always ask before working on an issue.

• Keep your fork updated to avoid merge conflicts.

• Follow code formatting and project guidelines.

• Add helpful visuals and clear explanations in your PR.

• Respond politely to feedback and revise code if asked.

• Be consistent and engage in the community channels.

---

📍 Stay Connected

Want to connect or collaborate?

• GitHub: github.com/reshamsai150

• LinkedIn: linkedin.com/in/saipranathi-resham-5a7921315

---

✨ Final Note

You don’t need to be an expert to begin. You just need to begin.
Each PR, each line of code, and each contribution helps you grow as a developer.

Good luck with your GSSoC journey! Happy contributing! 💖

---

Written with love to help beginners take their first confident step into open-source.

---