Getting your first PR merged into a major open-source project is harder than it looks - not because the code is hard, but because nobody explains the unwritten process: how to find an issue worth taking, how maintainers actually triage contributions, and why technically correct PRs still get rejected.

This talk walks through the real mechanics of contributing to large projects, drawn from merged and rejected PRs across Apache Spark, Apache Flink, and Elasticsearch.

I'll cover finding good first issues, writing PRs maintainers actually want to review, navigating JIRA/review workflows, and what to do when a PR gets closed instead of merged - because that happens too, and it's not the end of the story.

Suitable for developers who've never contributed to open source and want a concrete starting point, as well as engineers who've tried and gotten stuck in review purgatory. Includes real examples of merged, closed, and open PRs with what made the difference.