Readers/Web/Team/Etherpad/Q4 Planning 2012-2013

Agenda
3/26 Mobile web and apps Q4 Planning
 * Goals/hopes/concerns (15mins) 1015-1030
 * Current state analysis (15 mins) 1030-1100
 * Break (5 mins) 1100-1105
 * Wishlist/product visioning (30 mins) 1105-1145
 * https://www.mediawiki.org/wiki/Mobile/2013_strategy_planning
 * Lunch (30 mins) 1145-1215
 * User stories (55 mins) 1215-1300 (separate groups)
 * Estimation (15 mins) 1300-1315 (separate groups)
 * Discussion and Prioritization (30 mins) 1315-1345 (everyone together)
 * Quick retrospective (15 mins) 1345-1400

Wishlist
For more details, see https://www.mediawiki.org/wiki/Mobile/2013_strategy_planning

Web

 * Nearby w/upload CTA M
 * Non lead image uploads (add image to section, gallery, etc.) M
 * Uploads view enhancements (dealing w/deleted images, etc.) M
 * Upload a similar photo (to one that's already in an article) M
 * Editing M
 * lighweight in scope (no VisualEditor)
 * section-level editing
 * how are people editing now?!
 * More login/signup hooks - M
 * Any contributory feature should have the login/signup hooks
 * Not necessarily a feature in itself, but should be guiding how we add new contributory features
 * Mobile file page improvement M
 * edit meta info on file page
 * add categories
 * added user info (eg from watchlist view)
 * Associate image w/article or Commons category S
 * Add article links to images (without inserting image into article)
 * See images that link to an article
 * Watchlist w/upload CTA S
 * Notifications - "You have new messages" S for minimum implementation, C for Echo stuff
 * Link to your own talk page
 * Coordination with Echo
 * Geotag images & match to nearby articles C
 * Find existing images from CTA
 * Find existing images nearby for a specific article
 * Geotagging existing images that don't have geotags
 * Adding categories to images C
 * Mobile GettingStarted (displayed after login as interstitial page) C
 * Depends on having more stuff for users to DO
 * Watchlist reverting C
 * Would require some sort of warning mechanism (warning to author of reverted change)
 * Could lead to edit interface rather than flat-out reversion
 * Mobile TWINKLE, yay!
 * Talk page commenting C
 * Requires exposure of talk page (Jon has patchset awaiting merge for alpha)
 * Viewing talk pages
 * Commenting on talk pages
 * Backlog-clearing work queues C
 * Stuff-to-do link in nav, like add categories, diambiguate links, add photos to articles, fix spelling
 * Integrate with existing Category:Wikipedia backlog ?
 * Semi-related to GettingStarted
 * Better/simpler user profile pages C
 * User pages (to deal with selfie photos! :-)) C
 * See other people's uploads from dashboard C
 * Article image galleries W
 * Update outdated images W
 * Upvote/downvote images W

delete this shit nosy peole

Web/mobile synchronization

 * Notifications
 * Communication
 * Nearby... maybe, eg OSM at the mapping layer

What does success for Q4 look like?
Graphs of edits/photo uploads (contributions in general) that look like this (log scale): ______
 * We have enough mobile uploaders to get at least *some* brickbats(https://en.wiktionary.org/wiki/brickbat) from the commons folks


 * http://i0.kym-cdn.com/photos/images/newsfeed/000/011/296/success_baby.jpg?1251168454
 * Percentage of mobile uploads that are *not* deleted is high
 * We have awesome tools that people use to upload photos on their mobile phones and such
 * 1,000 mobile uploaders :)
 * We meet our mobile uploaders goal before the end of the quarter and move on to other fun contributory stuff
 * We see more desktop power users paying attention to, using, and getting excited about mobile features
 * We begin to see repeated engagement on mobile web, not just one-time contributors
 * We infulence how people think about uploads on the desktop
 * Features moving from mobile to desktop
 * People moaning on wikitech about how crappy the desktop site is comparatively
 * We improve mobile cache hit rate to be close to that of desktop squids
 * Ops loves us!
 * We let current power users curate content (at least have some control over changes to articles)
 * Happy Stephen Walling
 * We hire another SUPER AWESOME software developer to help reduce the JS backlog

What does failure for Q4 look like?
http://epicfail.xepher.net/wp-content/uploads/2010/12/epicfail1.jpg
 * iOS contributions dont catch up to Android
 * Not enough design support
 * Features we think work don't anymore
 * Not enough awesomeness!!!1
 * Using only numbers to tell success from failure is a failure
 * Out of control mobile spam
 * Declining long time editors
 * We continue to get hamstrung by stuff like CentralAuth
 * People working long/unsustainable hours
 * We get a thousand selfies
 * http://medlibes.com/uploads/torches-and-pitchforks.jpg (village pump)
 * Meetings about meetings
 * Commons users completely hate us, mobile team needs armed escorts for Wikimania (same as Jon's ^)
 * Never figure out code review backlog
 * Uploading sucks and nobody uses it
 * Apps and Web step on each others toes (ouch!)
 * We still need mobile varnish cache flushes
 * Ops hates us <-- so we've already failed?
 * People stop using mobile phones (blame Apple) and start using Google Glass we can just fork into the Google Glasses team
 * We introduce more bugs than features ;) (and spend too much time fixing them)
 * Too rigid code review

What worked?

 * web team is really into product discussions :)+
 * Timing works fine+
 * AV was very unglitchy
 * got some issues sorted out & prioritized so we don't feel like there's a billion things we could do :)
 * didn't feel like half the day went by
 * very focused discussion on just q4
 * breaks +1
 * having all three teams together (partner+web apps)
 * free lunch \o/
 * good facilitation by arthur thanks! +1!
 * feels actionable

What didn't?

 * Had to add new items to failures post review
 * could have used more time digging into features+
 * R66 A/V setup
 * Watching people eat lunch while not eating lunch :P(note to self: get yuvi lunch next time)
 * Varnish 500 errors during demo
 * Bit tired pre deployment ++
 * Would have been interested to be involved in app team discussions (team fragmentation) (+1)
 * We shouldn't need to do demos ++
 * Personal responsibility to eat our own dog food
 * Use more regular show cases
 * 4 friggin hours+
 * Possibly break into multiple, shorter meetings? Most folks prefer one day.
 * Some folks think might feel longer
 * What about focus meeting time, then group hacking, then reconvene?