What should I work on?
This page attempts to be a one-stop shop for figuring out what the most important thing to work on is, so that team members (contributors) can determine the more effective way to improve Flutter.
- Build breakage. Check the dashboard.
- P0 issues (e.g. serious regressions).
- Mentoring promising new contributors.
- Code review of open PRs.
-
P1 issues, including:
- Flaky tests.
- Performance regressions. Check the dashboard for new unreported regressions and see GitHub for the list of reported performance regressions.
- Other regressions.
- Reducing technical debt. (For example, increasing our test coverage by writing new tests, or fixing TODOs.)
-
P2 issues, which correspond to the remaining areas of our roadmap, such as:
- Bugs marked as annoyances.
- Bugs labeled as issues of quality.
- Bugs with the crash label.
- Issues sorted by thumbs-up. Focus on bugs in existing code and avoid adding new code.
- Everything else. Consider this advice when prioritizing bugs.
Bugs in other bug systems should be tracked with bugs in GitHub. OKRs should be reflected in the items listed above. For example, OKRs should reflect what the roadmap covers, expected customer blockers, and so forth. Work that is unique to a particular quarter would be represented by a filed bug with a milestone and assignee.
During triage, bugs should be prioritized according to the P0-P3 labels so as to fit the order described above.
Sometimes, items in the list above escalate. For example, a bug might get filed as a P2 issue, then be recognized as a critical regression and upgraded to P0.
See also:
- Issue Hygiene, in particular the section on prioritization.
- Home of the Wiki
- Roadmap
- API Reference (stable)
- API Reference (main)
- Glossary
- Contributor Guide
- Chat on Discord
- Design documents
- Code of Conduct
- Issue triage reports (latest)
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Popular issues
- Running and writing tests
- Release process
- Flutter Framework Gardener Rotation
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems and Retrospectives
- Hotfix Documentation Best Practices
- In case of emergency
- Landing Changes With Autosubmit
- Setting up the Framework development environment
- The Framework architecture
- API Docs code block generation
- Running examples
- Using the Dart analyzer
- The flutter run variants
- Test coverage for package:flutter
- Writing a golden-file test for package:flutter
- Managing template image assets
- Setting up the Engine development environment
- Compiling the engine
- Debugging the engine
- Using Sanitizers with the Flutter Engine
- Testing the engine
- The Engine architecture
- Flutter's modes
- Crashes
- more...
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Contributing to Plugins and Packages
- Understanding Packages tests
- Plugin Tests
- Releasing a Plugin or Package
- more...