The [[ https://meta.wikimedia.org/wiki/Technical_Collaboration | WMF Technical Collaboration team ]] has some FY2015-16 budget available for Phabricator improvements. Let's agree on a sorted list of Phabricator improvements that could be proposed to Phacility Inc (Phabricator maintainers) for their prioritization, and then let's fund those that can be agreed with upstream and fit our budget.
Basic rules of this //game//:
* Technical Collaboration funds, and therefore the features proposed need to have clear benefit for volunteers.
* Proposals need to be presented in the form of existing or new tasks blocking this one. Discussions specific to those improvements go to the tasks themselves. Here we discuss prioritization between tasks and other general topics.
* We will not argue with upstream about the convenience of certain improvements. If a proposal fits their roadmap, good. If not, that will be the end of the discussion within the scope of this task.
* This budget needs to be spent within this fiscal year (end of June), and counting back steps this means that we need to make quick decisions. In case of getting stuck in long debates, the TC team will make the last call, say by the end of May.
== Improvements confirmed ==
* {T165}
== Candidates ==
The list of candidates is closed now. We are drafting its prioritization in our discussion with the Phabricator maintainers. If you want to suggest changes in this list (additions / removals) or changes in priorities, please post them in a new comment.
* {T33}
* {T45}
* {T634}
* {T1016}
* {T1035}
* {T1375}
* {T75851}
* {T76732}
* {T78078}
* {T78236}
* {T78824}
* {T78830}
* {T91289}
== Lack consensus ==
If you want to discuss proposals in this list, please do it in their own tasks.
* {T234} (no consensus in discussion, no clear mapping with a task upstream)
* {T624} (current status of the task unclear, relevance of what is missing unclear)
* {T800}
* {T883} (unclear plan upstream; duplicated and related tasks seems to be addressed similarly)
* {T1378}
* {T76993}
* {T96464}
* {T127641}
== Unclear status upstream==
* {T96} (a [[ https://secure.phabricator.com/T4207 | local patch ]] exists)
* {T109}
* {T110} (upstream says it is [[ https://secure.phabricator.com/T8362 | fixed ]])
* {T127}
* {T225}
* {T77708} (wontfixed upstream)
* {T78257} (related task is closed resolved upstream)
* {T85305} (upstream has no plans to do this)
* {T85440} (upstream warned that footer in workboards and Conphrence would be a lot more involved)
* {T86464} (lengthy discussion in related task upstream; there seems to be a way to fix this locally)
* {T91648} (closed resolved upstream)
* {T98337} (not a problem according to upstream)
* {T98570} (upstream has an explanation for current behavior, related task is closed resolved)
* {T127903} (not reported upstream; likely to be a discussion on design decisions)
* {T134398} (under discussion upstream)
== Processing ==
You can help triaging these, moving under Candidates those which show a strong use case and consensus.
* {T75854} (marked fixed, but Phabricator search is still awful. It would be great to be able to reenable the Elasticsearch backend.)
* {T76825} (the related task upstream is not a 1:1 map of this request; it needs assessment)
* {T84844} (need current testing and assessment, looks trivial?)
* {T86463} (missing report upstream)
* {T86849} (it is unclear -- at least to Quim -- what needs to be done upstream, what locally)
* {T94675} (missing report upstream)
* {T97751} (missing report upstream)
* {T98334} (missing report upstream, not an essential feature)
* {T100400} (there is no 1:1 mapping with upstream tasks, it needs review)
* {T100943} (missing report upstream, it is a trivial change)
* {T115742} (missing report upstream, looks like a too narrow use case)
* {T127908} (too narrow use case, has alternative solution)
* {T135728} (missing report upstream)
* {T135729} (missing report upstream)
* {T135732} (missing report upstream)