Open main menu

Strategy/Wikimedia movement/2017/Sources/English Wikipedia

InformationEdit

What group or community is this source coming from?

name of group English Wikipedia
virtual location (page-link) or physical location (city/state/country) w:en:Wikipedia talk:Wikimedia Strategy 2017
Location type (e.g. local wiki, Facebook, in-person discussion, telephone conference) local wiki
# of participants in this discussion (a rough count) 28

SummaryEdit

The summary is a group of summary sentences and associated keywords that describe the relevant topic(s). Below is an example.

The first column (after the line number) should be a single sentence. The second column should be a comma-separated list of keywords about that sentence, and so on. Taken together, all the sentences should provide an accurate summary of what was discussed with the specific community.

Summary for the discussion:

Line Statement (summary sentence) Keywords
1 Improve offline access in emerging communities offline access, accessibility
2 Improve writing quality to keep ease of understanding foremost. Some medical students state they use WP rather than other sources is because we are easier to understand. clear writing, accessibility
3 Address the problem of undisclosed paid promotional editing quality, trust, neutrality, spam
4 Handle rich content, such as maps, graphs, and other interactive features quality, features, rich-content
5 Develop and expand upon collaborations with other movement partners partners, collaborate
6 Improve relations and expand collaboration between the formal organizations and individual editors. Community Tech team as a good example. movement growth, movement interaction
7 Help guide non-English new contributors to the Wikis in their primary language, to ease their acclimatization. Encourage the growth and quality of non-English wikis. translation, growth, global, collaboration
8 Fix Wikidata issues that are hindering its utility, so that it can benefit everyone more easily wikidata, software, disambiguation
9 Spam and paid-advocacy concerns are growing, as the power and networks of spammers grows. Invest in methods to help prevent this problem before it balloons. spam, features
10 Focus outreach and growth efforts on the non-large projects, which currently have extensive Eternal September problems and thus lowered patience. outreach elsewhere,
11 Emphasis on quality instead of quantity. Software is needed to help triage the poor-quality and high-quantity articles. quality, features
12 WMF should invest in overhauling MediaWiki before it becomes outdated. Enterprise support contracts, to enable surplus funds that can be used on high-priority features (community tech initiatives, GLAM outreach, anti-abuse tools and terms of use enforcement) mediawiki, enterprise, features, software
13 Use AI more to help AI
14 Technical or social solutions should exist to protect high-quality articles from low-quality edits, often by newer editors. quality, prevention, featured-articles, user rights
15 Software should automatically flag edit summaries that use certain words or phrases, so neutral editors can review those edits mediawiki, software, features, edit-summary, collaboration
16 A third "shared" project should be created alongside Wikidata and Commons, to handle maps projects, rich-content, features
17 Move forward experienced editors by granting them with additional rights. experienced editors, user rights
18 Focus on editor and user experience, don't ignore their feedback. features, software
19 Fight with harassment. harassment
20 Better, easy to find and maintain documentation. documentation
21 Collaborate with education-oriented sites. collaboration, education
22 Clearer and more consistent communication pathways between software makers and users. software, features, communication, collaboration
23 Become a software that auto-adapts to suit the educational needs of the user. software, features, accessibility
24 Have our content well-used in external educational content. education, outreach
25 Develop better and more powerful editor-oriented tools, and distinguish the urgent tasks from the non-urgent tasks. software, features, editing
26 Improve our patience and friendliness, reduce the probability of angry interactions between new/naive and grumpy users with social efforts and software tools. conduct, trust and safety
27 Get students and libraries involved. involvement of existing networks, education, GLAM
28 Develop a legal strategy, defend our Terms of Use by taking legal actions more often. legal, protection
29 Use blockchain for Edit history of articles for author rights management. features, software
30 Make better deals with sources, or outright buy access for a selected number of editors. sources, access
31 Develop a "free source directory/finder". sources, access
32 Counterbalance our dependence on business-oriented/corporate point-of-view mass media sources in our up-to-date content. sources, POV
33 Figure out a way to strongly encourage editors to write a proper edit summary. edit summary, features, software
34 Develop a stronger mechanism for dealing with COI and brochure/resume writing. quality, POV, COI, content
35 Make editing more "fun" to editors by improving user experience, simplifying citations, and gamifying some aspects of editing. user experience, fun
36 Make our content more shareable and embeddable for readers. re-use, content, readers
37 Communicate that Wikipedia is not complete, expose what content we're lacking, redlinks, content
38 Make the stub system more connected to the regular encyclopedia use. stubs, content
39 Kill the "portals" that get too little reader/editor attention, move their content to articles. portals, content
40 Allow editors being paid for their general efforts, and draw a line that says editors cannot be paid for editing specific articles. paid editing, policies

If you need more lines, you can copy them from Strategy/Wikimedia movement/2017/Sources/Lines.

Detailed notes (Optional)Edit

If you have detailed notes in addition to the summary, you may add them here. For example, the notes may come from an in-person discussion or workshop. If your discussion happened on a wiki or other online space, you do not need to copy the detailed notes here.