Everything you need to know to make meaningful open source contributions and grow as a builder during GSSoC 2026.
Last updated: March 2026
Contents
GSSoC exists to connect you with real projects, real maintainers, and real communities. Open source is not a resume checkbox — it is collaboration, communication, and craft. Your contributions must solve genuine problems, be maintainable by others, and leave the codebase better than you found it.
The program rewards quality over quantity. A single, well-reasoned pull request that solves a real issue carries far more weight than a series of superficial changes.
Respect maintainers' time. Read the documentation before asking questions. Follow contribution guidelines before opening a pull request. Communicate proactively when you encounter blockers.
AI-generated code submitted without understanding will result in disqualification. Reviewers are trained to identify it.
AI as a Learning Tool
You may use AI tools (GitHub Copilot, ChatGPT, etc.) to understand concepts, debug errors, or generate boilerplate. You must fully understand and be able to explain every line you submit.
Cite AI Assistance
If an AI tool substantially contributed to a solution, acknowledge it in your pull request description. Transparency is respected; concealment is grounds for disqualification.
No Unreviewed AI Submissions
Copy-pasting AI output without review, testing, or meaningful adaptation is prohibited.
No AI in Conversations
Do not use AI to generate issue comments, responses to maintainer feedback, or any form of project communication. All communication must be authentic.
Work on Registered Projects Only
Only contribute to repositories listed on the GSSoC 2026 Projects page. Contributions to unregistered repositories do not count toward the leaderboard.
Claim Issues Before Starting
Comment on an issue to express interest and wait for assignment before submitting a pull request. Unsolicited pull requests on unclaimed issues may be closed without review.
Write Clear Pull Request Descriptions
Every pull request must describe: what changed, why it changed, how to test it, and any known trade-offs. UI changes require screenshots or screen recordings.
Test Before Submitting
All code must be locally tested before submission. Include or update test cases where the project has a test suite.
No Trivial Changes
Whitespace fixes, comment typo corrections, and README cosmetic changes are not counted. Accumulating rejected pull requests affects your standing in the program.
Respond to Reviews Promptly
Maintainers volunteer their time to review your work. Respond to review comments within 48 hours or the pull request may be closed.
Your leaderboard score is calculated automatically based on:
Scores update automatically as your contributions are merged. The breakdown of every point you earn is visible on your public profile and the leaderboard.
You will be disqualified and your contributions removed from the leaderboard if you: