<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 19 February 2015 at 23:47, Erik Moeller <span dir="ltr"><<a href="mailto:erik@wikimedia.org" target="_blank">erik@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I propose a "Roadmap" project in Phabricator. Tasks in this project would be typically epics with rough anticipated calendar-level delivery dates and clear, understandable task descriptions.<div><br></div><div>Tasks would be arranged on a Phabricator workboard like so:</div><div><br></div><div>January 2015: Features</div><div>January 2015: Platform</div><div>January 2015: Apps</div><div>February 2015: Features</div><div>February 2015: Platform</div><div>February 2015: Apps</div><div>etc.</div><div><br><div>This could ultimately replace some of the detail in the on-wiki goals pages, and ensure we have a single calendar type view into expected deliverables. We could iteratively move our work into this new format if it works.</div><div><br></div><div>If we play our cards right, we can reduce duplication and bring the roadmap and goalsetting "closer to the metal" so to speak.</div><div><br></div><div>Thoughts? If we try this, any guinea pigs? Or feel free to point me to a much more sophisticated version of this idea :)</div></div></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I'm willing to try this, to replace the existing on-wiki VisualEditor roadmap <a href="https://www.mediawiki.org/wiki/VisualEditor/Roadmap">https://www.mediawiki.org/wiki/VisualEditor/Roadmap</a>.</div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">It has some advantages:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><ul><li>As a Wikimedia user, I now have a single view of all changes which could impact me.</li><li>As a Wikimedia user, I now don't have to have a mental model of what tasks are which teams' responsibilities.</li><li>As a product manager, I now can more trivially free-lance on bigger-picture issues which touch lots of teams' responsibilities and none without duplicating others' work.<br></li></ul></div></div><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">It has some downsides from a user perspective, though:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><ul><li>As a user who cares about a specific outcome in VisualEditor, I no longer have detailed "blocked because of Xyz" explanations around the outcome in which I'm interested.</li><li>As a Wikimedia user who cares about editing tools, I no longer have somewhere to keep track of bigger planned changes to editing things, and have to pick them out of other changes to e.g. Apps or Search which I don't care about.<br></li><li>As a non-Wikimedia MediaWiki sysadmin who wants to upgrade VisualEditor-MediaWiki locally, I no longer get a view<br></li><li>As a non-MediaWiki developer who uses VisualEditor, I no longer can see planned long-term changes in one place and it's more difficult for me to find somewhere to lobby for changes.</li></ul></div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Also, the VisualEditor roadmap explicitly doesn't use dates, as it cover speculative ideas of several person-decades worth of work that may never happen. I'm not sure where we'd put things like that, even if (per Gilles) we show a board based on quarters.</div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Finally, ideally the apps/features/platform changes would be vertically separated in a grid rather than repeating quarterly columns, but I know that Phabricator doesn't support that (yet). Worth trying out, though.</div><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">J.</div></div></div>-- <br><div class="gmail_signature"><div dir="ltr">James D. Forrester<br>Product Manager, Editing<br>Wikimedia Foundation, Inc.<br><br><a href="mailto:jforrester@wikimedia.org" target="_blank">jforrester@wikimedia.org</a> | @jdforrester</div></div>
</div></div>