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

Apps

Feature

• Account creation MUST
• Campaigns in Commons apps MUST MUST
  • I want to find out what focused themes other people are contributing to, and join them in contributing focused image items. I also want to find out what other people have been uploading into campaigns, so that I can follow them
  • estimation - MED
• More hooks into the app from wikipedia web MUST
  • connect with web team
• Adding categories to uploads MUST (done this week)
• Mobile GettingStarted MUST
  • A new user should be introduced gently to the idea of Commons, reusability, and CC licensing... at least enough to tell them not to upload random selfies or useless photos
  • sage?, guillaume?, maryana?
• Dealing with deleted uploads. MUST MUST
  • If an image that I uploaded is up for deletion, I want to know that so that I can look at it and respond appropriately [deletED or deletABLE?]
    • notifications? -> ties in with talk page commenting?
    • estimation - HIGH
    • guidance for now is to remove image from their my uploads view
      • Needs API work

Plumbing

• Image Info API MUST
  • As an app author or API consumer, I want to be able to fetch relevant information in machine-readable format and be able to *update* it piece-by-piece. (License info, descriptions, authorship/provenance).
    • connect w/ wikidata team, yuri?,
      • wikidata/yuri/max conversation
    • push actual work to next Q?
• Discovery of 'What to photograph' process (similar to our WLM discovery), using Wikidata as backend MUST HIGHLY RECCOMENDED
  • I want to be given suggestions on what to photograph, both in general and for each campaign. (See: WLM suggestions from last year)
  • estimation - HIGH
  • connect with wikidata team, community
  • gudiance for now is to start conversations

NonTech

• Legal discussion about Video / Audio Codecs
• Address Freedom of Panarama
  • possibly in getting started

Outside of Quarter

• Kiosks at Wikimania (People can pop in their SD card from their DSLRs and upload easily) SHOULD

Deferred

• Apps sharing, geotagging, referencing MUST
  • Directly from their camera app or gallery, use the share feature and choose the Commons app to ingest the image. Already exists! -- verified
  • Directly from browsing or other apps with URLs, use the native share feature and Already exists! I can't seem to find this with Share via from native Android browser I think this only works for actual images, not URLs that have images on them Got it, doesn't contribute to core upload metric...maybe ** interesting for adding references, but not interesting for photo uploads, which would break the requirement that photo must be from the specific user
• Curation Micro-apps MUST HIGHLY RECCOMENDED
  • As a commons user I have 20 minutes left and want to clear some of the backlogs (categorization, minor image editing, etc) and want to do it in an easy, clean way with the apps
• Talk page commenting HIGHLY RECOMMEND NOT (Not too useful for commons)
  • Actually I think this is very useful for Commons -- user talk pages are where you get messaging saying "we're gonna delete your image". It would be very nice to see those and be able to reply.
    • defer to later?
    • You also get them on you user talk page, which emails you.
      • true... but then you have to go to the web site to deal with reading it and responding.
        • You can't really respond to it from the app anyway :)
        • Recommend delay until after Flow / Echo

Needs more thought

• Nearby with upload CTA MUST NICE
• As a user if I share or pick an image from my gallery or camera, if the image is geotagged or if the the image is really new and the geolocation sensor is on, I would like to be prompted with nearby articles to which I can upload the image.
  • poor OSM map support in iOS and Android

• Upload a similar photo SHOULD
• Suggest a photo for this page SHOULD
• Article image galleries SHOULD
• Associate images with articles SHOULD
  • choose the Commons app to add the hyperlink as a reference. SHOULD

• Watchlist with upload CTA NICE NICE
• Update outdated images NICE
  • Would need common discussion
• Article of the day widget NICE
• Wiktionary Word prononciation uploading NICE
• GeoTagging NICE
  • IF you have it turned on your phone
  • would have edit the template or do it pre upload

• Non-lead image uploads NOT
• Watchlist reverting NOT
• Editing NOT
• Notification area NOT
• wikipedia:// and wcommons:// protocol handlers NOT
• Upvote/downvote images NOT

• Wikipedia and Wiktionary search widgets Already exists?

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?

• iOS contributions dont catch up to Android
• Not enough design support
• Features we think work don't anymore

http://epicfail.xepher.net/wp-content/uploads/2010/12/epicfail1.jpg

• 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

Q4 planning mtg Retrospective

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?