Mobile web/Etherpad/Q1 Planning 2013-2014

Mobile web and apps 2013-2014 Q1 Planning (21 June 2013, 10am-2pm PDT)

Agenda

 * Goals/hopes/concerns
 * Goal: Gain clarity around overall expectations and desires of department
 * Wishlist/product visioning
 * Goal: Unify department on quarterly goal(s)
 * User stories
 * Goal: Gain clarity and some consensus around high-level features
 * Planning poker
 * Goal: Get relative estimations of stories, identify dependencies, risks, etc.
 * Discussion and Prioritization [Arthur/Maryana/Tomasz]
 * Goal: Identify at a high level how stories evolved; identify areas of alignment/overlap between apps/web
 * Quick retrospective [Arthur]
 * Goal: Identify how to improve quarterly (and annual) planning meetings in the future.
 * After: Mobile apps/web cross-pollination
 * Open hack time, work on what you want - app/web pairing/defection/etc encouraged

What does success look like? What are your hopes?

 * Okay, okay, more realistic goal: we double our current mobile contributor pool :D
 * People tell us and their friends that mobile Wikipedia is awesome
 * Hmm, they already do: (GREAT SUCCESS!)
 * (Technical) Wikipedia Zero becomes further decoupled from MobileFrontend
 * Low error rates (for things like uploads)
 * Other teams and volunteers making mobile things / making mobile optimised features
 * Smaller codebase for MobileFrontend (upstreamed changes, HTML transformations killed with fire)
 * Apps are well liked by users, get significant usage share
 * Vector desktop skin looking more like mobile
 * Low to nonexistent community pushback
 * People suggest other great things to do with the apps and web that show how much they're using it
 * Experienced editors recommend Mobile as a way to 'get work done' to their friends
 * We've hit at least 1/4 of our annual goal!
 * Apps uptake increases, apps ease of use increases
 * Official apps have better ratings than 3rd party apps on both app stores
 * Apps make possible scenarios that aren't possible via Mobile Web or Desktop
 * People do useful things with our apps and mobile site
 * A selfy of Barack Obama on the Barack Obama article (that would be a success to me! (to me too :)))
 * More teams/projects build mobile-friendly features
 * Infinite ZeroRated partners in every country

What does failure look like?

 * MobileFrontend3 extension
 * https://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2013/04#Missing_author.2Fsource_parameters_on_mobile_uploads:_fix_coming
 * We can't sustain our current monthly contributors numbers (we dip below 1K)
 * People tell us and their friends that mobile Wikipedia sucks
 * Other teams create desktop-only features
 * People are confused about how to use our apps and or using the web so go back to desktop
 * People on wiki hate us, the word 'mobile' brings groans from multiple people
 * Apps aren't used/get poor reviews
 * Everyone works way too many hours - works late, works weekends
 * We can't retain any users; we just get drive-bys #selfiepocalypse
 * Users who do register become inactive
 * Apps and web go in completely different directions
 * Someone creates MobileFrontend3 haha snap
 * Community stones the mobile dept
 * People create lots of useless stuff that has to be cleaned up via the mobile site and apps
 * Apps usage drops or they are poorly received
 * More regressions than new features

Web (and possibly some apps ideas)

 * Post-registration: suggest a task [possibly contextual, based on what you read/have watched]
 * Left nav browse tasks & contribute - persistent link in the left nav for all registered users
 * Post-registration: takes user to home page w/ some stats about me and a CTA to contribute if I never have
 * Different post-registration experience depending on where you came from
 * Direct revert/thanks/warn
 * History and Watchlist Friendly Reverting (e.g., ability to revert, but automatically leave a talk page message to user, "Hey, we appreciate your edit, but it was reverted because there wasn't a citation. . .")
 * Images Actions
 * Flagging as inappropriate
 * Adding tags/categories
 * Rating images within categories
 * Firehose of new image with swipe gestures for triage (Up - ok, right - copyright, etc.)
 * Dabsolver
 * Adding Geo-coordinates to articles/images
 * simplified history version -- includes the most important for information for a editors to make a decision as to whether they want to view diff
 * User contribs (my, other users') view that doesn't suck
 * Better diff management -- fix UX (entry point is history, watchlist, recent changes, etc.)
 * Better way of viewing diffs that aren't next to each other (e.g., Be able to easily compare multiple and arbitrary revisions
 * Correcting locations on existing articles
 * "Rating/approving/reverting" contributions by IP users / Flag content
 * History - Sane mobile view that a human can understand with smiley faces
 * Better entry point into history (from article)
 * Post-registration: fill out quick "what do you love?" survey (multiple choice) - we give you tasks based on this
 * Make New Page Triage tool mobile friendly
 * Improve Wikidata Items with properties to wikidata items within specific categories like people, places, etc
 * Is this person alive?
 * What do they do?
 * Male/female/other

Image actions:
 * Rating on metrics of artistic, technical, educational
 * For automatic lead images for articles?
 * Hot or Not for images within categories (most representative for a place, thing, person, etc)
 * Banners to registered users [taking them to contribute page, point them to edit button, features like Nearby]
 * Post-registration: make an edit to userspace/fill out profile to learn markup
 * Summaries of article history on history page (e.g., top editors, most reverted editors, etc.); most helpful edits (e.g., large changes that haven't been reverted)
 * Text transcription from scanned Wikisource
 * Watchlist - Different filters. Same things as above (motion, people)
 * Unfriendly reverting (e.g., ability to warn/block user)
 * Thanking user for contribution (not from diff view)
 * Recent changes [WP power] Make into an app! AND a view on mobile web
 * Ability to view all changes from one editor (in succession) to one page
 * How much has changed since last time I viewed page
 * Make a campaign for Nearby
 * Rating search queries off-site to their target articles as a good match or not to improve article metadata (collaborate with Google)?
 * Translation- based on knowledge of a particular language, prompt the user to translate all or part of the article
 * Matching foursquare locations to article names
 * Collaborate with Foursquare?
 * Trump geotagged images with higher quality ones

Apps - specific

 * decentralize campaign creation and maintenance -- currently restricted because theres no edit history etc
 * campaign discovery: featured campaigns, active campaigns, [your interests?], keyword search, nearby
 * upload gamification: leaderboards, showing activity/stats of users
 * apps offline functionality -- easy to do fr baic campaigns; harder if we integrate geo search like wlm or nearby
 * machine readable licenses
 * image triage: show a stream [per campaign, per cat, per user?] and have buttons to flag as offtopic, inapprpriate, copyvio, etc
 * Image Info API work to be done!

App user stories

First release

Organizer features
 * I want to setup appropriate metadata for the Campaign so that people can upload images of cheese without worrying about licensing, categorizing and proper templates [1]

Backend Work (All covered in https://www.mediawiki.org/wiki/User:Yuvipanda/Campaigns_namespace_proposal Phase 1, 2, 3

Save it on the wiki [Commons]
 * Backend ability to store data

Front end to set / modify data User interface for creating and modifying campaigns

Scavengar Items Setup (Automatic List)
 * Requires 'query' functionality on WikiData
 * Require every item to be a WikiData item [superset of Wikipedia articles, less 'notability requirements' than wikipedia articles, gets us automatic translation/linking]


 * Ability to generate scavenger lists that can then be inserted into wikipages, limited to:
 * autogeneration of lists based on categories, existing wikidata objects, and other things we can get easily
 * manual generation of lists <- this is easiest :)
 * list columns: whatever we have in Wikidata

Contributor features
 * Multiple campaigns in one app
 * Find campaigns near me
 * Contribute to campaigns with campaign info prepopulated (mobile and desktop)
 * Recently added images per campaign? (helps people know actually what is going on, better way to describe than just desc)
 * [or start with just taking text description]

? General Commons features (may help campaigns)
 * What happens after the first upload?
 * CTA to add photo to articles [similar to mobile web's 'add photo' feature on the art]
 * Image Curation
 * Categories
 * -> think more about after-upload actions and discovery and reuse and organization
 * -> making, curating galleries

Wikiproject use case
 * As a campaign organizer, I would like create a campaign to take photos of cheese  [1]
 * I want to setup appropriate metadata for the Campaign so that people can upload images of cheese without worrying about licensing, categorizing and proper templates [1]
 * I want to setup appropriate lists so that people participating in the Campaign can discover the various types of Cheese, information about them and where they can find them (Note: This works better for geography stuff, than Cheese)  [1?, but limited in scope]
 * As a campaign organizer, I would like to be able to manually create a list (i.e., select articles myself)
 * As a campaign organizer, I would like to set the available licenses(force single license per campaign?)[1], custom fields[2?], tracking categories [1], default templates[1] for a campaigns (current functionality)


 * As a campaign organizer, I woud like to set the GPS location of a campaign, filtered POI list [1]
 * open issue: how do campaign managers use list (e.g., move around, put on wiki page, etc.)

Wiki meetup use case
 * As a Wiki-NY meetup organizer, I'd like to create a Wiki Takes Manhattan campaign , 
 * As a Wiki-Takes-Manhattan contributor, I'd like to use a mobile app to upload photos I take around the city (as I'm there, onlinie) [1]
 * As a Wiki-Takes-Manhattan contributor, I'd like to use a mobile app to take photos offline (without data roaming), label them immediately, then upload them later on my hotel wifi [1?]
 * As a campaign organizer, I would like to deactive, archive, and see meta information about my own campaign
 * As a campaign organizer, I would like to deactive, archive, and see meta information about my own campaign


 * As a campaign contributor, I would like to contribute to the Wiki Loves Cheese campaign easily
 * Opening the campaign pre-sets categories / templates for me, and picks a preferred license too [1]
 * I get list of cheeses that I can take pictures of, and I can click through to see more information about them [1? see above]
 * I can take a picture and upload that picture with all of the campaign info prepopulated [1, repeat of above]
 * I can see the other pictures people have taken via this campaign too[1?]
 * Relationship between scavenger lists and campaigns
 * One list per campaign, filterable / searchable 
 * As a campaign contributor, I would like to know what campaigns are near me so that I can contribute something locally [1?]
 * As a Campaign Contributor, I want to see the featured campaigns that are popular right now
 * Validate with community whether it can be manual


 * As a Campaign Contributor, I would like to search all meta data about a campaign and its items


 * As a Campaign Contributor, I would like to see a leaderboard (e.g., top contributors + uploads; mobile + desktop; other stuff we can do now like page views, usage; in the future ratings), per campaign so that I can see who's contributed the most (GeoCaching like Gamification)
 * As a Campaign Contributor, I would like to see new and popular contributions within a campaign so that I can see its activity
 * As a Campaign Contrubutor, I would like see other users contributions to one or many campaigns, so that I can easily see what they've contributed. (Remember to not clash with Flow's Boards)
 * As a campaign contributor (vs. regular user of commons), I see some stats on my campaign contributions (e.g., "you're participating in campaign cheese. You've uploaded 2 so far. . ."
 * As a campaign contributor, I would like to triage a campaigns images to filter what is and is not appropriate

(In the commons app, there would be a campaigns section, which would list all of the campigns. We will not, for example, have one app per campaign)

User story rubric: As a, I can , so that I can .

Personas:
 * New
 * Newish
 * Watchlist user
 * Uploader
 * Editor
 * Experienced Wiki user
 * Expereicned Commons user

http://etherpad.wikimedia.org/2012-2013-Q1-Mobile-Web-Stories

Planning poker instructions: 1) Each engineer selects a set of cards 2) Product owner reads user story to be estimated 3) Story is discussed 4) Each engineer PRIVATELY selects a card representing their estimate. The card is NOT shown to other estimators. 5) Once each engineer has selected a card, all cards are revealed at the same time. 6) If everyone played the same card, that's the estimate for the story. 7) If estimates are not the same, group discusses the estimate, focusing especially on outlying values 8) Repeate until estimates converge

Planning poker card values: ?, 0, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100, ∞

Simple, distributed planning poker website: http://hat.jit.su/ Mobile web: Room: 23032 http://hat.jit.su/23032

What worked well?

 * didn't feel like two days of meetings
 * was not exhausting ( or rly?!)
 * it was a beautiful exhaustion
 * prolific user story creation+
 * yesterday was awesome and productive
 * having arthur in the office+++
 * having design involvement
 * SO MANY STORIES \o/
 * broke down some more of our ideas for apps into manageable pieces+
 * collaboration of the team+
 * hearing about the analytic results+1
 * very creative brainstorming - lots of engagement from everyone :)
 * Got thrown into the water today, drank a lot.
 * GOOD contentious converstaions+

What didn't work well?
Apps and mobile web didn't mix too much+1++++++++
 * Talk a little more about what we plan to build, identify more places for cooperation
 * Thinking of stories in isolation was not good - maybe have a rep from each hanging out with the other
 * Get out of the office for this in the future, environment should invigorate discussion+++++
 * Need to be sure to support remoties
 * Lack of a human mission statement for the next 3 sprints+++++
 * not a number, something more qualitative; something you'd tell your mom and she would understand+

(Hammocks?)++
 * R37
 * Heat, noise (both for remoties and folks in the room)+++
 * Office LieFi sucks Note
 * R66 LiFi (TM), had to cannabalize ethernet cord from phone
 * 3 friggin days+++
 * Audio was worse than usual, especially today. I've got a headache from people constantly knocking on the table.+
 * Very little dev work++
 * Saturday Morning 2 AM!
 * apps didn't get to estimation, we had lots to talk about :)
 * apps depends a lot on WikiData, of which we didn't have enough information+
 * Monte's wifi connection&Jon's
 * i need coffee today
 * SO MANY STORIES \o/ <- writing them all together instead of individually might have helped us dedupe+ +
 * no general gauge of what 1 vs 400 planning poker score means for user stories that we created++
 * This iteration started on Monday but has been disrupted+
 * sometime people shot down ideas during ideation rather than just being creative+
 * need more veggie food :)+

What still puzzles you?
Isn't Kaldari supposed to wear a hat?+1 When do we start ordering pizzas for us remoties? How apps and mobile web are going to live together going forward+++++ How does Vector fit into the mobile web future+
 * overlapping more in sprint planning meetings, or other planning meetings in general?
 * finding more unity between features/feature ideas