Public work on shared projects.
WHAT IT PROVIDES
Public evidence of your work Experience of real codebases Exposure to review Occasionally, connections
WHAT IT DOES NOT PROVIDE
A direct route to employment.
WHY THAT NEEDS SAYING
Contribution is frequently oversold as a job strategy.
WHAT TO START WITH
Something you actually use.
WHY
You understand the problem and care about the outcome.
WHAT FIRST CONTRIBUTIONS TYPICALLY ARE
Documentation improvements Small bug fixes Tests
WHY DOCUMENTATION IS A GOOD START
It is needed, welcomed, and it teaches the codebase.
HOW TO FIND SOMETHING
Issues marked for newcomers Problems you encountered yourself
WHAT TO DO BEFORE CONTRIBUTING
Read the contribution guidelines Look at recent accepted changes Comment on the issue before starting
WHY COMMENT FIRST
It avoids duplicated work and rejected approaches.
WHAT TO EXPECT
Review that may be blunt Changes requested Occasionally, no response at all
WHAT TO DO ABOUT NO RESPONSE
Move on; maintainers are volunteers.
WHAT TO AVOID
Trivial changes made only for the record Large unrequested rewrites
WHAT TO VALUE
The review, which is free instruction.
