How to handle rejection, criticism, and burnout in open source
PR rejection recovery, hostile review handling, imposter syndrome in OSS, sustainable contribution pace, setting contribution limits, when to fork vs advocate, recognizing community toxicity
Rejection Is Part of the Process
Every long-term open source contributor has PRs that were rejected, reviews that stung, and periods where they stepped back. The ones who stayed learned to separate feedback from identity.
When a PR Is Rejected
Read the reason fully before reacting. Most rejections contain actionable information. Wait 24 hours before responding to emotional feedback. Ask one clarifying question if the reason is unclear. Do not reopen without addressing the stated reason.
Handling Hostile Reviews
Some reviewers are blunt to the point of rudeness. Separate the technical content from the tone. Extract the technical point -- the null check needs to be before the cast -- and address it. If behavior violates the Code of Conduct, report it to maintainers through the project process.
Sustainable Contribution
Open source contribution is a marathon. Set a pace you can maintain indefinitely. Contributing two hours per week consistently beats two-week sprints followed by months of silence. If you feel guilty about reducing your contribution rate, that is a signal to step back, not push harder.
When to Fork
If a project direction consistently conflicts with your needs and advocacy has not worked, forking is legitimate. The git model was designed for this. Forking is not hostile -- it is how competing ideas resolve themselves over time.