In T135327, the WMF Technical Collaboration team collected a list of Phabricator bugs and feature requests from the Wikimedia Developer Community. After identifying the most promising requests from the community, these were presented to Phacility (the organization that builds and maintains Phabricator) for sponsored prioritization.
I am very pleased to report that we are already seeing the benefits of this initiative. Several sponsored improvements have landed on https://phabricator.wikimedia.org/ over the past few weeks. For an overview of what's landed recently, read on!
The following tasks are now resolved:
|T33: Phabricator should let you add dependencies both ways (depending and blocking)|
|T165: Provide a way to upload a file in Phabricator if drag'n'drop is not available or not wanted|
|T234: Projects dropdown should offer project descriptions|
|T634: pholio/new/ requires drag and drop|
|T75851: Email notification for "edited the task description" does not contain the actual content changes (diff) nor a link|
|T78078: Videos cannot be viewed without downloading|
|T78824: Phabricator task description diffs inaccurate due to 80-character line wrapping|
Notice three of those have task numbers lower than 2000. Those long-standing tasks date from the first months of WMF's Phabricator evaluation and RFC period. When those tasks were originally filled, Phabricator was just a test install running in WMF Labs. For me, It's especially satisfying to close so many long-standing issues that have effected many of us for more than a year.
Several more issues were identified for sponsorship which are still awaiting a complete solution. Some of these are at least partially fixed and some are still pending. You can find out more details by reading the comments on each task linked below.
|Partially fixed||T76732: Exact matches should always win when suggesting/auto-completing|
|In Progress||T136071: Get Phabricator i18n ready for translatewiki.net|
|Stalled||T96464: Upon edit, a task description which mentions a Phab user (re)adds that Phab user to CC/Subscribers field|
|x||T1035: Consolidate the many tech events calendars in Phabricator's calendar|
Besides the sponsored features and bug fixes, there are several other recent improvements which are worth mentioning.
This very helpful feature displays a graphical representation of a task's Parents and Subtasks.
Initially there was an issue with this feature that made tasks with many relationships unable to load. This was exacerbated by the historical use of "tracking tasks" in the Wikimedia Bugzilla context. Thankfully after a quick patch from @epriestley (the primary author of Phabricator) and lots of help and testing from @Danny_B and @Paladox, @mmodell was able to deploy a fix for the issue a little over 24 hours after it was discovered.
Here's to yet more fruitful collaborations with upstream Phabricator!
Starting Thursday May 12th, 13:00 PDT ( 20:00 GMT ) we will be having the first weekly Code Review office hours on freenode IRC in the #wikimedia-codereview channel.
Thanks to everyone who's been helping to organize this. We would welcome people to submit your patches for review as well as reviewers who can spare a few minutes to provide feedback and hopefully merge some patches!
If you can't make it during the scheduled time period then please feel free to suggest other times that would be better for you. I intend to set up one or two other weekly time slots, at least one of which should be at a time that's more convenient for people in Europe and Asia.
Looking forward to seeing you in #wikimedia-codereview
Not a lot has changed for Wikimedia's instance of Phabricator over the past few months. That's because a lot has been happening behind the scenes, as well as upstream at Phacility. Members of the Release-Engineering-Team and Team-Practices group have been working since December 2015 to integrate various upstream changes, however, nothing was released to our production instance because there were so many important features that were in-progress and not yet fully usable. Additionally, we had to figure out exactly how these features would fit with the specific needs of our project and test a lot of functionality to be sure that we would not break anyone's workflows.
So our Phabricator instance has been relatively unchanged since November of last year. This all changed last Wednesday night (Thursday February 18th, 01:00 UTC) when we unleashed several months of changes into production. If you use phabricator.wikimedia.org regularly then you have probably already noticed some of the more obvious improvements.
A whole lot of hard work went into this release. Thankfully, everyone's hard work seems to have paid off as we only encountered a couple of relatively small issues which were fixed quickly after.
This post is to fill everyone in about what's changed and what you can expect from some of the exciting new functionality that has been added with this release.
It's now possible to customize individual project pages to meet the needs of each type of project or the needs of specific teams.
Projects can now be nested. There are two new types of projects in Phabricator and they could prove to be really useful for organizing all of the things. Sub-projects are just like regular projects, but nested inside of an existing project. Milestones are a special type of sub-project that can be used to represent a sprint or a software release. There are a few somewhat complex rules about how project membership, policies and tasks are affected by sub-projects. There is detailed coverage in the Phabricator Projects Documentation and we have attempted to explain some of the implications here:
Previously this functionality was provided by a custom field and rPHSP phabricator-Sprint
This couldn't have happened without everyone's help <3
Specifically I'd like to thank: