Review and organize overall project team structure

[ehuss]

This is a bit nebulous, but the overall idea is to:

• Determine the overall shape of the project.
  • Determine who or which teams are actually part of the project.
  • Establish guidelines for determining whether or not to accept a new team in the project.
• Ensure all teams and other governance structures are "attached" to appropriate places in the structure. (This includes working with teams to find appropriate homes, and ensuring such changes are ultimately reflected in the team metadata repository.)

I seem to recall there are some ambiguities, but I don't remember what they were exactly.

See also #32 for specific considerations of the top-level team arrangement.