Reading/Readers contributions/Reading team thoughts

From MediaWiki.org
Jump to: navigation, search

Rough guide to what the Small, Medium and Large estimations correspond to is below.

Ways that readers might support contributors[edit]

Description Ease of ux implementation Ease of backend implementation User joy User Commitment Onboarding difficulty Community concerns Moderation needs Value created Helping community? Dependent on Blockers Notes
vandalism review? L M S M M S L M M
identifying "citation needed" or other inline markers user selects sentence and chooses from small set of template options M S S S S
article level feedback (preset) user selects from preset group of feedback about article (more info needed, possibly biased, etc.) M
recording of audio titles M M M S S S M M M Backend ability to store audio files (commons?)
wikidata description editing M (UX feedback) S S S S S S L M Might need to investigate ways for editors to educate or block users who continuously violate
suggesting edits open form article feedback tool... S S (assuming suggestions will go on Talk page) S S S M M M M
request more information see link
image moderation users can categorize, approve or reject new commons uploads XL L M S S L L L L Community interest community, infras This would involve a LOT of community consultaiton
image submission users can upload images (only if we help with moderation) L S M M M (without moderation, L) L L L Moderation Thorny, and theres a commons app, but big payoff
lead image centering/cropping user can center lead image to avoid things like this: https://en.m.wikipedia.org/wiki/Bradley_Cooper?mobileaction=beta M M (if there is metadata storage in commons with API) S S S S M S We don't need to propagate changes to the image beyond the android app until moderation is in place
lead image selection user can scroll through gallery in Android or iOS and select a better lead image M S S S S S S M S changes to Images API Could require fair use protections if policy goes a certain way
show nearby items that need image user of app gets a notificaiton that something nearby needs an image, other readers can moderate by answering "is this a picture of the eiffel tower" before it gets submitted S M L S S S M M M
infoboxes from Wikidata, with editing XL S S M M M L L L
edit simple english version make simple english more prominent and promote editing there S
identify table or other thing that doesn't look good let editors know when a template or something else doesn't look good on phones S (M from design) S (blocked on metadata in article) M S S S S S M UX and storage infrastructure
Find a citation hunt for citations directly from article-probably hard for most mobile users S
Article rating/voting grade article to give editors another metric S L S S M S M
Readers thank editors let editors know they are making an impact S Unknown S S S S S S S infrastructure infrastructure Could be a small win if infrastructure is in place...otherwise, not worth it
wikigrok 2.0 quiz that populates wikidata

For readers only, would probably not help contributors[edit]

Description Ease of ux implementation Ease of backend implementation User joy User Commitment Onboarding difficulty Community concerns Moderation Value created Helping community? Social driver Dependent on Blockers Notes
Annotations L M M M L L M L
social highlighting S M S S S S S M
Gather - curation of articles, images (sharing) M M M L S M M M Web
Discussion forums about article topic, not article writing M
suggest pre-reading articles S
More visible question and answers (Reference desk ) M
Comment rating/voting S
Kinda: Reveal existing interactivity of editors S S S S S S M S?

T-Shirt size estimation legend[edit]

Loose guide to T-shirt size estimations. T-shirt estimates are made specifically to avoid specificity and allow planners to quickly assess the rough impact and cost of a project. That being said, this guide might be helpful for those who would like a general sense for how we came up with them. The definitions were written up after the fact.

Ease of ux implementation Ease of backend implementation User joy User Commitment Onboarding difficulty Community concerns Moderation needs Value created Helping community?
L = more than a quarter (>3 months) for design, community consultation, design research and implementation

M = roughly a quarter for same

S = less than a quarter for same

L = very complex, would require new infrastructure, storage or changes to other. Might require cross-team collab.

M = the pieces are in place, it is just a lot of work.

S = minimal, we just plug into existing services

L = a reason to use wikipedia

M = a feature some will appreciate

S = a feature that people might do if we make it easy and prompt them

L = this takes a lot of thought, knowledge and/or research

M = this takes a moment to think

S = easy, on the spot task

L = many rules/skills required to learn this

M = it takes a minute to learn

S = a sentence-long prompt

L = this risks going against one or more principles closely associated with the movement or create an unmanageable amount of work for editors

M = this is controversial or has the potential to create more work for editors

S = this is a change, but shouldn't negatively impact community members

L = due to the high potential for abuse or mistakes, this will require significant oversight

M = this will require some form of oversight

S = this is not expected to require additional oversight

L = this will greatly improve the quality or utility of wikipedia

M = this will improve the quality or utility of wikipedia

S = this will hardly make a difference to the quality of Wikipedia

L = this signficantly reduces the workload of existing contributors

M = this mildly reduces the workload of existing contributors

S = this is not expected to alleviate or improve any existing workstreams