Flutter Inner source
Examples, advice and documentation from the Flutter inner source & GitHub community
Winning Together with Inner source
Inner source products within the Flutter group
can
be used by any internal team, and are open to contribution from any of our ~5000
engineers
in any division or location. We use inner source to leverage the scale of our business
by
improving our products at a speed and quality that our competitors can't match.
For
example we inner source the same betting platform across many divisions & teams
with
each actioning their own priorities within it.
Read more
about how inner source
works...
Our inner source portfolio is contained in the Flutter-Global GitHub organisation.
GitHub
recommends a flat single-org repository structure like this for inner source to
simplify
access control and consistent team management. At our scale with thousands of inner
source
repositories extra structure and conventions are required so we group repositories by
"capability" and provide automated tooling to work on these repository
groups.
Read more about our GitHub conventions and
automation...