(In the context of T94165: Engineering Community quarterly review January - March 2015, WMF is changing its quarterly review process, and this is a goal task created basically after the fact in order to accommodate to the new process.)
The following text is extracted from the last quarterly review, and eventually fine tuned:
Expected impact: Fluent development process across teams and with volunteers
Success measures:
- ☑ Overall participation keeps growing (active users, projects). -- see e.g. https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081421.html and https://www.mediawiki.org/wiki/Community_metrics#Reports
- ☑ WMF Engineering processes use Phabricator for cross-team coordination. -- cf. Blocked-on-* projects
- ☑ WMF teams still using Trello have identified actionable blockers. -- reported by individual Trello users; also cf. T825: Goal: The majority of WMF developer teams and sprints have moved to Phabricator
- ☑ The Wikimedia Phabricator team maintains the project, dealing with upstream bugs and high priority tasks.
- ☒ Our instance is upgraded regularly following a deployment plan that includes continuous integration of local patches. -- not fully resolved yet but on the way, being discussed and worked on in dedicated T85123: Create a continuous integration plan for Wikimedia Phabricator patches
- ☑ Plan agreed on local patches and relationship with upstream. -- Documented in mw:Phabricator/Code#Wikimedia Phabricator bug workflow