On Tue, Oct 7, 2014 at 11:02 AM, Dan Garry <dgarry@wikimedia.org> wrote:

On Tuesday, October 7, 2014, Greg Grossmeier <greg@wikimedia.org> wrote:
The "critical for the foundation" stuff that doesn't fit within any specific team tends to come to MW Core, and that's a problem that was identified by robla and others in the eng. management circle. Proposals on how to fix that more than welcome.

Basically I think it comes down to agreeing as a team on the team's scope, making that scope known in a public venue, then holding people accountable to explaining how their proposed project for the team meets that scope.

MW Core has a scope, see the responsibilities that Chris quoted. It's just that the scope doesn't matter when a C-level comes along and says "Erik (now Damon), we need X by Y, please do it." That request rarely (if ever, I've never seen it) goes to any other team than MW Core. I've never see Editing or Flow or Mobile or Multimedia take on things like an IEG review system. Ever.

There aren't many good solutions to this problem, but there are many bad ones :)

--
Greg Grossmeier
Release Team Manager