<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 9, 2015 at 5:50 PM, Kevin Smith <span dir="ltr"><<a href="mailto:ksmith@wikimedia.org" target="_blank">ksmith@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"><div>I'm curious how you ended up choosing a Task (rather than a Project)</div></div></blockquote><div><br></div><div>ECT's natural rhythm is monthly, and we already create a project for every month. This quarterly task is basically the only artifact we have aiming to cover that quarter. Anyway, not a big deal and we'll see how this evolve.<br></div><div> </div><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"><div>, and why that task only lists the sub-goals (rather than blocking on them). <br></div></div></blockquote><div><br></div><div>Ah, I like this question. It felt a bit silly having a task with a description that basically consists of a list of tasks, and then having such tasks listed again as "Blocked by". A purely cosmetic reason. Again, we'll see.</div><div> </div><div><br></div><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"><div>That might relate to this documented guideline:<br></div><div><br>"Creating <i>new</i> tracking tasks (tasks that "automatically" get
resolved when all its dependency tasks are resolved) in Phabricator is
discouraged. It is recommended to <a href="https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects" title="Phabricator/Creating and renaming projects" target="_blank">create a project</a> instead." [1] <br></div></div></blockquote><div><br></div><div>Mno. This task has a clear end (the end of the quarter), while the usual tracking tasks that became infamous in Bugzilla times are usually neverending goals à la "fix teh docs". </div><div><br></div><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 would be interested in hearing the history behind that policy so I can understand the rationale. <br><br>[1] <a href="https://www.mediawiki.org/wiki/Phabricator/Project_management/Tracking_tasks" target="_blank">https://www.mediawiki.org/wiki/Phabricator/Project_management/Tracking_tasks</a></div></blockquote><div><br></div><div><a href="https://phabricator.wikimedia.org/T75703">https://phabricator.wikimedia.org/T75703</a> -- and if you want more, I would recommend you to sit next to Andre Klapper and a couple of beers. :)<br></div><div> </div><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"><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, Apr 9, 2015 at 2:07 AM, Quim Gil <span dir="ltr"><<a href="mailto:qgil@wikimedia.org" target="_blank">qgil@wikimedia.org</a>></span> wrote:<br></div></div><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><div class="h5"><div dir="ltr">In the past, the "Wikimedia Engineering/2014-15 Goals" wiki page and the quarterly reviews were the main venues to communicate and discuss future plans.<div><br></div><div>Now quarterly reviews are strictly about the past quarter, and only the top goal of each team is documented in the wiki page. This is probably good enough to have a clear top level view of the critical WMF activities. Still, this leaves out a lot of planning and work.</div><div><br></div><div>There is also the #Roadmap project in Phabricator, although this is restricted mostly to user/developer facing software changes, which again doesn't reflect all the work teams do.</div><div><br></div><div>What ECT is doing now is:<br></div><div><br></div><div>* document the single top goal in <a href="https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals" target="_blank">https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals</a> as instructed</div><div>* document our other quarterly goals in a Phabricator task blocked by the related epics, i.e. <a href="https://phabricator.wikimedia.org/T93770" target="_blank">https://phabricator.wikimedia.org/T93770</a></div><div>* If any epic deserves to be on #Roadmap or #Notice, then we associate these tags accordingly.</div><div><div><br></div><div>Is this a good approach?</div><span><font color="#888888"><div><br></div>-- <br><div>Quim Gil<br>Engineering Community Manager @ Wikimedia Foundation<br><a href="http://www.mediawiki.org/wiki/User:Qgil" target="_blank">http://www.mediawiki.org/wiki/User:Qgil</a></div>
</font></span></div></div>
<br></div></div>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Quim Gil<br>Engineering Community Manager @ Wikimedia Foundation<br><a href="http://www.mediawiki.org/wiki/User:Qgil" target="_blank">http://www.mediawiki.org/wiki/User:Qgil</a></div>
</div></div>