FlutterOpen SourcePakistan
How a Pakistani Engineer Got 6 PRs Merged Into Flutter's Official Framework
A Karachi engineer's 90-day path into the Flutter framework: triage, the test-first bar, review etiquette, and how to repeat it.
Read on
Read on On Site →Key takeaways
- Start with `good first issue` triage, not feature PRs. Earn the review etiquette first.
- Every PR needs a test. Fix-only diffs are rejected almost on sight.
- Tight, obvious diffs win. Reviewers reward clarity over cleverness.
- Plan three months, not three days. Sustainability beats burst contributions.
Frequently asked questions
How long does Flutter PR merging take?
Median 2-4 weeks once review starts. First response usually lands in 3-7 days. Plan for at least one round of revisions even on small fixes.
Do I need to be a Google employee?
No. External contributors get the same review path. Six of these PRs were merged from outside Google.
What is the hardest part?
Writing the test that proves the fix without breaking adjacent paths. The Flutter team will not take a fix without a test that fails before and passes after.
Where do I find good-first-issues?
github.com/flutter/flutter/labels/good%20first%20issue is the live list. Many are stale; pick ones with recent triage labels.