Hi all,
Vibha, Monte, Luis and I met to discuss the blockers for the iOS release. As a group we identified the following things that need to happen before the release:
1. Making the information in the footer link to the article history. [Legal blocker, Brion working on this right now] 2. Add a Terms of Use link into the App Store description upon release. [Legal blocker, Dan to do this] 3. Refine the More menu. i.e. product and design to decide what should be in there, and what the prose should be [Dan and Vibha to work on this, top priority card in for next sprint] - Add links to privacy policy and terms of use [Legal blocker] 4. Auditing internationalisation. Try to switch to other languages. [Dan to test] 5. ToC refinements [Monte, in current sprint] 6. Remove the "tap to hide chrome" behaviour [Monte, in current sprint]
Some of these, namely {1, 5, 6}, are being handled in the current sprint. Some, namely {2}, are handled at release. However, {3, 4} can't be handled in the current sprint.
Given the quarterly planning this week, and the four day week, we're delaying the release, instead placing {3,4} as top priority issues for the next sprint, and targeting 14th July instead.
Let me know if you have any questions.
Thanks, Dan
Also, it bears repeating that "release" is actually code for "submission". Apple takes around six days [1] to review the submissions right now, and then assuming it passes the review we'll need a few days after that to sync everything up with communications, so the *actual* release date is likely to be at least a week after the 14th.
Dan
[1]: http://appreviewtimes.com/
On 30 June 2014 14:10, Dan Garry dgarry@wikimedia.org wrote:
Hi all,
Vibha, Monte, Luis and I met to discuss the blockers for the iOS release. As a group we identified the following things that need to happen before the release:
- Making the information in the footer link to the article history.
[Legal blocker, Brion working on this right now] 2. Add a Terms of Use link into the App Store description upon release. [Legal blocker, Dan to do this] 3. Refine the More menu. i.e. product and design to decide what should be in there, and what the prose should be [Dan and Vibha to work on this, top priority card in for next sprint]
- Add links to privacy policy and terms of use [Legal blocker] 4. Auditing internationalisation. Try to switch to other languages.
[Dan to test] 5. ToC refinements [Monte, in current sprint] 6. Remove the "tap to hide chrome" behaviour [Monte, in current sprint]
Some of these, namely {1, 5, 6}, are being handled in the current sprint. Some, namely {2}, are handled at release. However, {3, 4} can't be handled in the current sprint.
Given the quarterly planning this week, and the four day week, we're delaying the release, instead placing {3,4} as top priority issues for the next sprint, and targeting 14th July instead.
Let me know if you have any questions.
Thanks, Dan
-- Dan Garry Associate Product Manager for Platform and Mobile Apps Wikimedia Foundation
On Mon, Jun 30, 2014 at 2:10 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi all,
Vibha, Monte, Luis and I met to discuss the blockers for the iOS release. As a group we identified the following things that need to happen before the release:
- Making the information in the footer link to the article history.
[Legal blocker, Brion working on this right now]
Do we also need to make sure that the full history can be scrolled through? Currently only the last N revisions (I forget how many) are fetched; we can either make it fetch more items when you scroll down, or we can add a link at the bottom to the web site as a quick hack.
-- brion
Can you make it bump you out to the Mobile Web interface like Android does? It's a bit jarring, but it vastly reduces the complexity of the problem for now.
Dan
On 30 June 2014 15:52, Brion Vibber bvibber@wikimedia.org wrote:
On Mon, Jun 30, 2014 at 2:10 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi all,
Vibha, Monte, Luis and I met to discuss the blockers for the iOS release. As a group we identified the following things that need to happen before the release:
- Making the information in the footer link to the article history.
[Legal blocker, Brion working on this right now]
Do we also need to make sure that the full history can be scrolled through? Currently only the last N revisions (I forget how many) are fetched; we can either make it fetch more items when you scroll down, or we can add a link at the bottom to the web site as a quick hack.
-- brion
Yes that should be pretty easy as a workaround for now.
-- brion
On Mon, Jun 30, 2014 at 3:59 PM, Dan Garry dgarry@wikimedia.org wrote:
Can you make it bump you out to the Mobile Web interface like Android does? It's a bit jarring, but it vastly reduces the complexity of the problem for now.
Dan
On 30 June 2014 15:52, Brion Vibber bvibber@wikimedia.org wrote:
On Mon, Jun 30, 2014 at 2:10 PM, Dan Garry dgarry@wikimedia.org wrote:
Hi all,
Vibha, Monte, Luis and I met to discuss the blockers for the iOS release. As a group we identified the following things that need to happen before the release:
- Making the information in the footer link to the article history.
[Legal blocker, Brion working on this right now]
Do we also need to make sure that the full history can be scrolled through? Currently only the last N revisions (I forget how many) are fetched; we can either make it fetch more items when you scroll down, or we can add a link at the bottom to the web site as a quick hack.
-- brion
-- Dan Garry Associate Product Manager for Platform and Mobile Apps Wikimedia Foundation
On 6/30/14, 2:10 PM, Dan Garry wrote:
Hi all,
Vibha, Monte, Luis and I met to discuss the blockers for the iOS release. As a group we identified the following things that need to happen before the release:
- Making the information in the footer link to the article history. [Legal blocker, Brion working on this right now]
Bug 66908. Yay!
- Refine the More menu. i.e. product and design to decide what should be in there, and what the prose should be [Dan and Vibha to work on this, top priority card in for next sprint]
What exactly is the "More menu"? Is that the entire "W" menu, or the hidden "..." submenu? Either way, I think this covered by bug 65824, which definitely needs more discussion after getting sidetracked about colors.
- ToC refinements [Monte, in current sprint]
Does this include bug 64336: Table of contents drawer should animate from right instead of left?
I think there are a few more bugs that should be considered as blockers though: * Bug 66902: infobox looks cut-off - being worked on! * Bug 64391: Credits screen needs improvement - needs design input maybe? I cc'd a few designers on it a few days ago. * Bug 66884: "last modified" timestamp offsets by timezone instead of showing actual time since edit
I've been loving the app while beta testing it and can't wait to see it go live :)
-- Legoktm