On Mon, Oct 6, 2014 at 10:02 PM, Bryan Davis <bd808(a)wikimedia.org> wrote:
This seems out of date to me. I think that the newly formed Release
Engineering team is responsible for the first and third bullet points.
That leaves "meeting the evolving needs of the website" and "develop
and document a clear set of APIs" still on our plate. Neither of these
seems like something that can be used to exclude much work from
consideration. This can be seen as a good thing when the team is
presenting their ideas outwardly, but it seems like a double edged
sword for incoming work requests. It also feels like something is
missing here. I really don't see any mention of our team's role in
code review and stewardship of quality for MediaWiki and
responsibility for security and performance considerations.
Also slightly out of date, but this is the document that I always
think of when I think about what it is we do on Core. Possibly more
descriptive than prescriptive:
"MediaWiki Core -- This group is responsible for stability, security,
performance and architectural cleanliness of the system. This ends up
translating into a lot of code review, along with infrastructure
projects like disk-backed object cache, heterogeneous deployment,
continuous integration, and over the course of the next year, a
migration to HipHop. While not a prerequisite, everyone on this team
started off as a volunteer developer. The whole engineering
organization has some level of responsibility for our code review
process, but this group has more of a primary responsibility for it
than most groups." -
https://blog.wikimedia.org/2011/08/17/what-is-platform-engineering/