In T177616#3665067, @bd808 wrote:

We have tried for a couple of years now to discourage projects scoped to a Foundation team or department. We have many legacy projects that violate this pseudo-standard:

• analytics
• commtech
• contributors
• design
• editor-engagement
• maps-team
• mobile
• multimedia
• reading-web-staging
• ... probably a few others that didn't jump out at me ...

There are a few reasons for discouraging 'team' aligned projects. One is that teams can and do change while their software projects tend to stick around. Another is that team alignment can restrict or discourage community involvement in the Cloud VPS projects. A third is that it can become very difficult for the Cloud VPS admins to find canonical points of contact for grab bag projects. When we need to determine who to work with to correct issues with VMs in a project its not fun to wait a couple of weeks for people to "ask around" about who may still be using a particular VM.