Our fork of 
Flutter is called Flock. We describe Flock as "Flutter+". In other words, we do not want, or intend, to fork the Flutter community. Flock will remain constantly up to date with Flutter. Flock will add important bug fixes, and popular community features, which the Flutter team either can't, or won't implement.
By forking Flutter, we get to decide what gets merged. We won't lower the quality bar, but by controlling merge decisions, we do gain the following opportunities:
Recruit a much larger PR review team than the Flutter team. This means faster review times.
Recruit PR reviewers who are ready to facilitate contributions, instead of merely tolerating them. This means support for a wider contributor audience.
Optimize policies. E.g., don't blindly demand design docs and conference calls when they won't substantially add to the effectiveness of the task at hand.
Use contribution successes to socially promote more contributions.
We're all Flutter users - leverage team and company relationships to identify market priority.
As Flock ships important bug fixes and features, the Flutter team can then choose to add those to Flutter, on their schedule. The community will no longer be limited by the Flutter team's availability, nor will the community need to beg the Flutter team to please accept a change. The Flutter team can use Flock's solutions, or not, but all Flock users will have access to them, eliminating your company and team's urgency and desperation.
