On Tue, Jun 30, 2015 at 1:25 AM, Pine W wiki.pine@gmail.com wrote:
Hi Quim,
A scope expansion for your team makes sense to me. I have two questions.
- Does your team currently have the capacity for this scope expansion,
with only existing staff, while continuing to support the existing Community Engineering mission?
The Engineering Community team can do less of what has been doing if we collaborate better with other colleagues: Community Liaisons, Team Practices, Release Engineering, product owners, lead developers, the upcoming Community Tech team, WMDE's young TCB-Team... https://phabricator.wikimedia.org/T101116
And of course we can do less if we collaborate better with the developer community (example: GSoC / Outreachy / Google Code-in are running better every year, a main factor being the increasing quantity and quality of volunteer involvement).
Then some tasks can take the change without much impact in total amount of work. For instance, organizing a developer summit in San Francisco including a track for web APIs targeted to developers from the SF Bay Area.
So yes, we believe we have capacity to start this move and make some progress. How much, how quick, and how well will depend on several factors. We will do our best showing results with the resources we have, and only then requesting more resourcing via alignment of goals with other teams or growing our own capacity.
2. Will the team continue to have goals related to code review?
More than ever, check the following quarters in our roadmap. https://phabricator.wikimedia.org/T101099
Without a proper code review process, this team is likely to fail in one of its measurements of success: Number of volunteer and third party developers contributing to our open source projects, and volume of their merged code contributions.