On 13 March 2015 at 18:59, Pine W <wiki.pine(a)gmail.com> wrote:
Yes, thank you. I trust you to adjust accordingly if the project finishes
early or encounters surprise roadblocks. At some point I would be
interested in seeing the task breakdown (are those on Phabricator
somewhere?).
Not yet, because we're still not decided on that yet. We avoid putting
cards that are not actionable in our backlog as a point of process. Once
we've done our quarterly planning process, we'll put those cards in the
backlog in Phab.
By the way, lest this email chain come across as
micromanagement of
Mobile Apps, I do appreciate that you and your team have a good track
record of producing software that people like, and I really appreciate your
transparency via the email updates that you write frequently.
Thank you. :-)
What was giving me sticker shock was the cost of
producing this particular
functionality, hence my questions.
A good part of this is because we were (very rightly) encouraged to keep
our proposals short.
Actually there's a lot of cool stuff I'd like to do as part of this, like
building out and scaling up Magnus's AutoDesc API to give users an
automatically generated starting point, which will definitely take
substantial engineering time to get it to a stage where it can be deployed
to a production server. That substantially increases the engineering
resources required. And that also needs to be designed, thus the design
resources required.
I don't just want to make it an editable text box. We can do better than
that! :-)
What I'm going to do, in order to help with our quarterly planning process,
is put together a slide deck that gives an overview of how I think this is
going to play out. Then it'll become clearer why I made the resource asks
that I did, I think. I'll share that deck on here when I have it.
Thanks!
Dan
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation