Contributor Resources
Level up your open-source journey. Explore our curated guides packed with real-life examples from successful past contributors.
Resources to level up
How to write proposals
Mentorship ApplicationLearn how to formulate and present winning project proposals for GSoC, Outreachy, LFX, and ESoC.
Key Takeaways
- •Focus heavily on the technical implementation breakdown, not just marketing speak.
- •Include realistic, week-by-week timelines with clear deliverable milestones.
- •Show evidence of preliminary research (e.g. referencing specific functions or files).
Finding Good First Issues
DiscoveryStruggling to find where to start? Use our curated paths to discover beginner issues.
Key Takeaways
- •Use advanced GitHub search filters to narrow down issues.
- •Look for repositories that actively merge community PRs.
- •Don't just claim an issue; state exactly how you plan to fix it.
All resources
Git Guide
Version ControlMaster the git workflows, branches, commits, forks, and rebase conventions used in open source.
Key Takeaways
- •Never commit directly to the `main` branch of your fork.
- •Write descriptive commit messages explaining the 'why', not just the 'what'.
- •Learn how to squash commits to keep the project history clean.
GitHub Guide
Developer PlatformFind your way around repositories, issues, discussions, projects, and pull requests.
Key Takeaways
- •Always fork the repository and clone your fork locally.
- •Keep your fork synced with the upstream repository.
- •Use GitHub Draft PRs if you want early feedback on incomplete code.
Resume Tips
Career SupportOptimize your resume to highlight open-source contributions and grab reviewer attention.
Key Takeaways
- •Quantify your impact (e.g., 'Merged 5 PRs', 'Decreased load time by 10%').
- •Link directly to your merged PRs or GitHub profile.
- •List open source under 'Experience', not just 'Hobbies'.
Interview Tips
Career SupportNail behavioral screening and technical walkthrough interviews for premium fellowships.
Key Takeaways
- •Prepare to walk through code you have previously written.
- •Admit when you don't know something, but explain how you would find out.
- •Ask the interviewers thoughtful questions about the community.