Coincidentally, I just saw that https://phabricator.wikimedia.org/tag/epic/ reads

Epics are long-themed tasks with many subtasks.

This tag is also used for goals identified in WMF's quarterly planning process, e.g. https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals

See also the thread "'Roadmap' project in Phabricator" started by @Eloquence on the team-practices list.

@Awjrichards my understanding is that this would now fall into the area of responsibility of the Team-Practices group. Is this correct?

As we get closer to wrapping up the goalsetting process from Q4, I'll work with the goal setting process owners to create phab tasks for the goals, and we can see how it goes :)

I am actively working on defining Best Practices (via SPDPP and Phlogiston projects) that both point in this direction.

Removing Team Practices Group for now; a number of TPGers are subscribed and following the conversation closely. If you need something specific from the TPG, we suggest you consider using a template along the lines of the example requests here:

https://www.mediawiki.org/wiki/Team_Practices_Group/How_To_Engage_With_TPG

@Qgil just so you know, removing the TPG tag leaves this task without an associated project. Not sure if this should fall under the product development process stuff, should just be closed, or other - but you are probably better suited to make that call :)

TPG has been experimenting with one phab tag per goal, instead of or in addition to one phab epic task per goal. Example: TPG-FY2016-17-Q1-Roll-Out-Engagement-Survey

Teams are free to use Goal to mark such tasks. Proposing to decline this task (also as nobody seems to feel responsible for T253629).