Talk pages consultation 2019/Phase 1 community discussion summaries

On this page are the summaries from the different communities that have participated to the talk pages consultation. Please don't edit other participants' summaries (except to fix typos).

Some comments? Please use the talk page.

FAQ
What is a community summary?

The goal of a community summary is to wrap up the discussions and provide a summary of what your participants said. That way, other communities can learn about your community's needs, concerns, and ideas. We have seen very different feedback on different wikis, and it is time to discover what everyone thinks!

Please include in that summary:


 * every perspective or idea your community had, and
 * how frequent each idea was; for example,
 * how many users shared a given opinion
 * whether an idea was more common among different types of contributors (newcomers, beginners, experienced editors...)

You can add as much detail as you want in that summary.

Can't the Wikimedia Foundation read all the feedback?

We are trying, but we really need your help. For most conversations, we have to use machine translation, which has limitations. This can help us find the most common needs or global ideas. Machine translation is useful, but it does not tell us how people are feeling or what makes your community unique.

Your community summary should be built from your community's perspective, experience and culture. You might also know of relevant discussions in other places, which we did not find (for example, perhaps someone left a note on your user talk page – it is okay to include that!). Your summary is extremely important to us.

What are the next steps?

Phase 2 will happen in April. We will analyze the individual feedback, your community summary, and some user testing. We hope to have a clear view of everyone's ideas and needs at the end of April.

Some ideas generated during phase 1 may be mutually exclusive. Some ideas might work better for some purposes or some kinds of users. During Phase 2, we'll all talk about which problems are more urgent, which projects are most closely aligned with the overall needs and goals of the movement, and which ideas we should focus on first.

Discussions about these ideas may be shaped and be moderated by the Wikimedia Foundation, guided by our decision criteria, listed on the project page.

Wikimedia Commons
I (Jc86035) was the only participant, although I did advertise the discussion on the village pump and on the centralized discussions template. I don't think it's necessary to summarize my own views, since I also commented extensively in the English Wikipedia and Wikidata discussions.

Although I was asked to inform new users of the discussion, I was unable to do so. I don't know whether this had any significant effect on the amount and variety of participants. Jc86035 (talk) 10:13, 4 April 2019 (UTC)

Wikidata
I (Jc86035) will be summarizing the discussion section-by-section. It is difficult to summarize some sections due to the small number of participants; in many cases I have only stated what individual users have said.

A total of 15 registered users (including myself) and two unregistered users (including one vandal) participated. By almost all measures, this is less than 1% of active Wikidata editors; there are about 1,800 editors who make more than 100 edits per month. Most participants appear to be experienced editors.

Although I was asked to inform new users of the discussion, I was unable to do so. I don't know whether this had any significant effect on the amount and variety of participants.

When you want to discuss a topic with your community, what tools work for you, and what problems block you?
Several editors like Flow and think it works fine but could be improved, and several editors say the same about the wikitext discussion system. (Whether one system objectively works better is out of scope; however, considering the comments made in the English Wikipedia discussion, restarting the implementation of Flow would be controversial at best.) Almost all community processes on Wikidata are conducted without Flow, with the only(?) major exception being the French-language project chat, and most participants say that those processes function satisfactorily (although the unregistered user complains that WikiProjects are typically abandoned; I think this issue is valid but out of the scope of the consultation).

One editor (Jmabel) suggests section watchlisting as an improvement to wikitext discussions. Two editors (PKM and Sabas88) indicate that they prefer real-time discussion fora such as Telegram groups; both mention mobile notifications as a factor, and Sabas88 also mentions "[a] usable mobile interface" and threading as factors.

The criticisms of Flow are a subset of those mentioned in the English Wikipedia discussion.
 * "Bugs need to be fixed" (VIGNERON)
 * Lack of diffs (Ymblanter)
 * Infinite scrolling (Ymblanter)
 * Unnecessary notifications when watchlisting a Talk-namespace page, as opposed to a Topic-namespace page (Ymblanter)

VIGNERON also notes that "Flow is quite a good tool (no need to know the painfully unuseful wikisyntax, automatic signing and pinging, etc.)". ChristianKl suggests that the use of Flow in the French-language project chat could have increased participation, although he notes that "causation is always difficult to establish". On the other hand, Ymblanter notes his avoidance of Flow and thinks he will stop contributing if it is forced upon his talk page.

What about talk pages works for newcomers, and what blocks them?
Only three participants commented in this section. Jmabel is a software developer, and (as he implies) this experience probably made it easier for him to use wikitext and signatures. Masumrezarock100's comment is unrelated to the software/interface (it's about user conduct), so it's out of scope. The unregistered user criticizes indentation and advocates for Flow.

What do others struggle with in your community about talk pages?
Only two participants (including myself) commented in this section. The other person (ChristianKl) complained that Flow doesn't have rollback, which caused issues with his talk page (I think he might have been referring specifically to handling vandalism in the form of new topics). I didn't say anything concrete, only noting that Wikidata might have an unusually high number of users who don't know how to use wikitext discussions (since most of Wikidata is Wikibase and a lot of user talk pages use Flow).

What do you wish you could do on talk pages, but can't due to the technical limitations?
Only three participants commented in this section. phab:T106687 was specifically mentioned by VIGNERON, although only as an example of many unresolved Flow issues (I think this is only tangentially related, though). I don't totally understand the exact meaning of ChristianKl's comments, but I haven't asked for clarification.
 * Automatic notifications from comments in a particular section (Jmabel)
 * The same discussion appearing on multiple talk pages (ChristianKl)
 * Some sort of WhatLinksHere visibility/function improvement to show links and/or template values used on talk pages? (ChristianKl)
 * Improved links between comments and page history (ChristianKl)

What are the important aspects of a "wiki discussion"?
Only three participants commented in this section. I have omitted most of Ymblanter's Flow complaints since their comment is duplicated in a previous section.
 * Allowing for varied types of discussions, including both goal-oriented and "purely social" (PKM)
 * Suggestion that talk pages should be more helpful to newcomers by improving navigation and giving explicit instructions (Donald Trung)
 * [User-oriented] structuring "to see who replies whom" (Ymblanter)

Orphaned talk pages
Only Donald Trung made a comment in this section, suggesting that the talk pages of deleted pages be moved to a centralized archive instead of being deleted at the same time.

A discussion about talk pages, on a talk page, advertised on talk pages
Only three participants (including myself) commented in this section. The discussion concerns the effects of holding the discussion as a normal Wikidata RFC, and alternate ways of collecting feedback. As noted in the status updates, Whatamidoing (Sherry) did continue discussion of a Qualtrics survey with other staff members, so the relevant WMF staff are presumably already aware of relevant information mentioned in this section.

Conclusion
As noted above, few conclusions can be drawn due to the small sample size. In general, this phase of the consultation may have suffered from being organized primarily around wikitext discussion pages; this may have resulted in only dedicated experienced users (with some level of interest in WMF internal affairs) having any inclination to participate.

A possible issue with the feedback is that later commenters may have tried (intentionally or not) to avoid duplicating what has already been said. This would probably make triage more difficult.

None of the participants who mentioned Wikidata's community processes suggested that they were not functioning satisfactorily, although this may have been due to the inherent survivorship bias stemming from most of the participants being experienced editors to begin with. (Another factor may be that genuine new users are rarer due to many contributors coming from other Wikimedia projects; 82.3% of the last 10,000 new Wikidata user accounts were created automatically, compared to 32.8% for the English Wikipedia. In many ways, Wikidata is unique among WMF wikis.)

I think the results of the larger discussions, such as that of the English Wikipedia, would be more useful for identifying issues, since only a few specific issues were mentioned in this discussion. Jc86035 (talk) 10:13, 4 April 2019 (UTC)

Dutch Wikipedia
Summary of the talk page consultation on the Dutch Wikipedia (nl.wikipedia.org), see w:nl:Wikipedia:Overlegpagina's_raadpleging_2019/Summary.


 * 16 registered users participated in the consultation: Bdijkstra, Ciell, Encycloon, Lidewij C J., Lotje, Mar(c), OSeveno,  Oxygene7-13, Richardkiwi, Robotje, Schilbanaan, TaalBarbaar, Thieu1972, Vinvlugt, Wikidrinker, and Woudloper.

general remarks

 * Although the number of participants is small, this is an important issue on the Dutch Wikipedia. A recent survey (over 300 respondents) showed half of them not satisfied with working atmosphere. Those people are not satisfied with how people interact with each other, which has to do with edit summaries, talk pages, and user talk pages. Only 8 percent of respondents visits the Village pump, a place notorious for unfriendly interactions.
 * Almost all participants on this talk page consultation comment on behavior of people, the way they respond to each other, or do not respond to each other. These behavioral aspects of talk pages dominates the technical aspects. People tend not to believe in technical solutions to behavioral issues. Nonetheless some ideas have been floated which might help a little bit in some areas.
 * Some commented on general distrust in the Wikimedia Foundation and their developers. Some believe the approach is biased, or negative, or that already decisions about changes have been made.

summary per question

 * 1) When you want to discuss a topic with your community, what tools work for you, and what problems block you?
 * 2) * How to attract more people into a conversation and increase diversity in participation and points of view?
 * 3) * Veterans notice the echo system, and newcomers do not notice the bell with a number on top of the page. Long ago a screen wide orange bar did notify you got a message on your talk page. That was intrusive, and effective to induce a response.
 * 4) What about talk pages works for newcomers, and what blocks them?
 * 5) * Newcomers face a hostile frontier of veterans (not all veterans). Some newcomers regret an AfD after they have been pushing NE/POV.
 * 6) * Newcomers don't engage on talk pages. Email notifications of messages on talk pages result in OTRS tickets rather than replies on talk pages.
 * 7) * Design of talk pages is too different from current other social media websites
 * 8) * Newcomers prefer top posting on talk pages
 * 9) * Idea: post human and not bot messages op (IP) talk pages
 * 10) * Idea: post friendly feedback (don't bite the newcomers)
 * 11) * Idea: six tildes signing to show functionary status
 * 12) * For newcomers to sign and indent is too complicated, the current design is non-intuitive. [user story: (opt out functionality) as a new user I want to post a reply on a topic that automagically is indented and signed]
 * 13) What do others struggle with in your community about talk pages?
 * 14) * Sign (three times)
 * 15) * Adopt Flow (three times, although some veterans don't like it)
 * 16) * Enforce edit summary
 * 17) What do you wish you could do on talk pages, but can't due to the technical limitations?
 * 18) * Refer to a specific position on the article page (two times). On the article page itself can be added, to pinpoint a comment to a specific position.
 * 19) * Flagging inappropriate comments (with something like a small button, so a functionary can follow up)
 * 20) * Delete or suppress inappropriate comments
 * 21) What are the important aspects of a "wiki discussion"?
 * 22) * Some discussion on Dutch wiki tend to escalate to quickly, like a flame war.
 * 23) * Idea: technically slow down number of comments on such a page
 * 24) * Idea: New "Add reply" button, just like "Add topic" tab, to prevent edit conflicts.
 * 25) * Tools to prevent gridlock
 * 26) * Too much ad hominem arguments on the Dutch wiki
 * 27) * Idea: forum lay out

Russian Wikipedia
In the flow "Best" practices analysis, the developers showed an overview of some sites. There were social networks. It was the impression that they were summing up - hey, look at them so let's do the same. This is suitable for "cute" unimportant conversations.

But we solve problems on the wiki. Each topic is about a problem. We need problem solving tools. Probably worth a look in the direction of bug tracking systems. We did not chat, we solved problems, for us the logic and sequence of the entire conversation is important. We solved problems and developed some ways to solve them, using only the wiki layout available to us. All our discussions are examples of solutions to problems and we want to see the equivalent of how the same solution to a problem will be presented in a new system (and not screenshots "for dummies: how to talk and click on the buttons in a new system like YouTube"). This is not equivalent to just leaving comments.

If you make a system for the discussion pages of articles - then just tell us that the system will only be restrictedly used in the discussion of articles or how you see its widespread use. Because we immediately try to imagine the application of the system to the situation when a hot topic quickly gathers a lot of comments and when the system can potentially go to requests. For discussions in Wikipedia namespace, we need a strong tool.

This time I would like to have a separate test wiki site (possibly separated by languages en.testwiki de.testwiki, without articles). To be able to log in with an existing account (just come and log in), and not necessarily create a new login. And so that you can create your own additional accounts (for answers to yourself) that are not created in sul. And so there was a simple way to get admin rights. For a big change - a big sandbox.

often used: the division of the discussion by the subtitles h2,3,4 really affecting the structure and there are links from table of contents.

often used: view all new messages as diff in the topic/on the page.

would be interesting: to receive notification of new messages not from the whole topic, but only those that are after / deeper than a specific comment (for example, all replies to your comment and further down the tread)

Often used: toolbar for working with wikitext, gadgets for the toolbar. For example, there is a gadget that converts non-Latin links http://.../wiki/%A%A%A%:A%A%A%A% to human readable link Википедия:Форум (Wikipedia:Forum). Desirable simple guide for gadgets.

often used: quick rollback of last edits of one user. Single rollback action of different places. Undo changes one by one would be uncomfortable.

important: it is customary to see relevant topics as on a whiteboard - a limited number in a limited space, a working space. endless scrolling was like endless requests for deletion, we just drown in it. https://ru.wikipedia.org/wiki/Википедия:КУ archiving topics on a separate page is the same division and support of the whiteboard as relevant.

problem: the big indents between posts, the big font broke a principle of a whiteboard and after long scrolling the thought of discussion is already lost. Compactness gives the possibility of viewing "as a whole".

problem: logical parallel lines are mixed and it is difficult to understand who is responding to whom. It's not about the number of levels of indents. The point is the breaks of logical chains of reasoning about one thought. If you need to make a summary for the discussion/request, then you need to be a medium to realize all the broken chains. ( https://www.mediawiki.org/wiki/Topic:Sjh61at6k8mz21oy see the sequence/chain of red arrows in the screenshots )

Statements in discussions are valuable. Collected and discussed information should be achievable through search. Including filtering from other types of discussions (eg, articles, participants, wikipedia/forum, wikipedia/different types of requests).

--Sunpriat (talk) 09:13, 5 April 2019 (UTC)
 * switch between wikitext and tree view (2)
 * (in other words, do not take away from us the opportunity to gain access to the structure and the opportunity to re-arrange the discussion design at a lower level) (3)
 * allow the user to start a new topic or section in a topic, add a message to an existing topic, reply to an existing message, and also edit (but not delete/wipe) their own previous messages (2)
 * Automatically sign posts (2)
 * Automatically resolve edit conflicts (warn before saving if new messages appear in the chain/topic) (2)
 * The visual editor should not be displayed smoothly. Instead, it should run quickly and work stably on weak devices. (2)
 * move topic to another place (1)
 * change other people's messages by other users (not only administrators) (1)
 * should be answered how this system is supposed to be used for pages with requests (1)
 * Fast work at a speed of 64 Kbps (current connection speed of one of the users) (1)
 * for simple commenting, the author needs a quick way with a minimum of clicks on the buttons and movements (1)
 * Some participants use the user script that edits comments individually without opening the wikitext and wikitexteditor page (8)
 * see in the watchlist individual topics on the forum (1)
 * if there is a whole forum on the watchlist, then the ability to ignore certain topics from it (1)
 * in the table of contents of the forum topics with new posts (less than a day) highlight in color (1)

Who joined?
I appear new users are many.

See w:ja:Wikipedia:2019年ノートページに関する協議/summary about their opinions.

General remarks
Participants are small and most of them are new users.

I infer their hard usage of smart phones when they edit Wikipedia by them.

Summary per question
1. When you want to discuss a topic with your community, what tools work for you, and what problems block you? 2. What about talk pages works for newcomers, and what blocks them? 3. What do others struggle with in your community about talk pages? 4. What do you wish you could do on talk pages, but can't due to the technical limitations?
 * Because explanations in English are basically many in the time of edits, articles and talks in Japanese do not increase.
 * Wikipedia app in iPhone does not work stably.
 * At the time of deleting characters, inputs are cancelled or 3Dtouch is unstable.
 * Are newcomers worried about ways to use and manner to other users?
 * Ways to use comments are hard to understand at the time of getting opinions and impressions from other users on a talk page learning ways to edit. Easier expressions on talk pages are necessary for easy response to other users.
 * Newcomers are worried about their signatures to forget and ways to do them.
 * A participant who did not know a tacit rule, “we consider silence as agreement”, as a newcomer asked many users’ opinions on their talk pages because no one responded proposal on a talk page. Tacit rules are hard to participate in the community as a newcomer.
 * Expressions such as ‘’help’’ for beginners that arrange most necessary basic rules concisely are good idea excluding traditional ‘’help’’. There are a little articles that arrange information totally on the Internet. Newcomers will spread and their reusages will be promoted. Articles that have been arranged about usage help me to join on the Internet.
 * Are ”Edit tools” not to see on talk pages under specifications?　Are a little rough writings of some people like ancient writings on talk page their tacit rules?
 * Harder to understand incompletely translated edit tools.
 * Hard to sign by a smartphone.
 * Easy mobile signature, please.
 * Hard to understand mobile edit very much and hard to do it as other users say. There is not any expression about mobile edit on talk pages about our signatures. Easier to understand by concrete mention of our writings at areas to write the text.
 * Proposing promotion of activity. In spite of objective that SNS ‘’itself’’ is not our goal as an assumed solution in, easy browses and writings to SNS are adopted to meet the needs of the times. You should think about it because they involve promotion of activity and self-realization people concerned by covered activities but not amendments to wiki system itself. Decrease of entry barrier to discussions by provision of system of involvement of personal talk pages and SNS including Twitter. Talk pages of articles are similar.
 * Protection is cause of parallel activities of users which are closed and hard to know. Covered nature of SNS above will make up for such a wiki’s limits. Improper utilization of sock puppetry also influence very much to this situation. Unreasonable operation of multi-direction will protect spread and progress in computer literacy in the true sense of the word on the contrary. In spite of some problems at expression of individual data for privacy issues, you should count including multi-accounts for statistical records.
 * Talk pages are to use to ask meanings of texts, to propose polished texts and to do other actions.

Other opinions
--Bletilla (talk) 00:42, 6 April 2019 (UTC)
 * 1) While I browsed, I do not understand why you are discussing like this or what problems make you to discuss like this. Unfinished translation of the page in MediaWiki into Japanese and little writings in this page mean little users are interested in this discussion at least in Japanese Wikipedia. I appear you are trying to solve local problems in English Wikipedia as global discussions including other languages’ Wikipedia.
 * 2) It is good because I can get acknowledge about many things in discussions with many types of users. While I am unaccustomed at edits about everything including edits of talks, I am editing hard.
 * 3) I want to write my sense to the present situation and response, variety of sense of incongruity and my knowledge but I am checking because of my little energy and times. While this is necessary and hasty comment, your invitation has given me mu own new knowledge and certainty. Good luck to Wikipedia’s more development.
 * 4) Other users pointed out my wrong edits and taught convenient functions in my talk page.
 * 5) When bot invited me at my talk page, because I did know the place, thing and your will, I apologize my late comment. While I am unaccustomed to Wikipedia totally, I am going to act as usefully as possible. I’ll express my opinions for you as a few mobile user.

Chinese Wikipedia
Our summary about this consultation has been published on Chinese Wikipedia with Chinese version. The following is the English version of this summary.

General information
The community consultation started on February 26, 2019, and finished on March 31. 24 participates joined this consultation. In addition, we consulted the female community in Taiwan on March 18 to offer the opinions of the female newcomers.

Currently, the discussion tools on Chinese Wikipedia include Wiki Markup talk pages, Structured Discussion (Flow), instant messengers (Telegram, Discord, QQ, IRC) and social network service (Facebook). Structured Discussion is available on the Knowledge Q&A (equivalent to the Reference Desk on English Wikipedia) and User talk page (optional). Most discussions on Chinese Wikipedia are on the Mutual Assistance Inn (equivalent to the Village Pump on English Wikipedia).

In addition, instant messengers are another popular and featured discussion tools on Chinese Wikipedia. We have a bot that can synchronize the talks on four messengers (Telegram, Discord, QQ, IRC).

Summery of the suggested questions
The followings are the summary of the feedback about the suggested questions from Wikimedia Foundation.


 * When you want to discuss a topic with your community, what tools work for you, and what problems block you?
 * translating.


 * What about talk pages works for newcomers, and what blocks them?
 * The followings are the feedback about this question:
 * Some unfriendly comments can be done on the talk pages by the users with the personal position (e.g. political position) and let the newcomers be uncomfortable.
 * Most of the talk pages uses the Wiki Markup, and decrease the newcomers' interest of participating discussion because of being unfamiliar with the Wiki Markup.
 * Most of the discussions about the articles are occurred on the Mutual Assistance Inn/Articles, and the talk pages of the articles become the archives from the Mutual Assistance Inn/Articles. If the newcomers leave the questions on the talk pages of articles, these questions cannot call attention of the expert editors.
 * The popular talk pages (e.g. Mutual Assistance Inn) are arranged in chronological order. The new comments are below the old comments, so that the newcomers' questions may not call the attention.


 * What do others struggle with in your community about talk pages?
 * The followings are the feedback about this question:
 * In the comments of the user talk pages (Wiki Markup mode), editors have two mode about the same topic:
 * Centralizing the sender's and receiver's comments to one user talk page;
 * Receiver go the the sender's talk page and open new topic to replay the sender's comments. Every editors' preferences are different, so the struggle about the process user talk page are occurred.
 * In Chinese Wikipedia, some editors have obvious personal position (e.g. political position), and the struggle about the position are often occurred.


 * What do you wish you could do, but can't due to the technical limitations?
 * translating.


 * What are the important aspects of a "wiki discussion"?
 * The followings are the feedback about this question:
 * The wiki discussion must be anonymous, open and free.
 * The wiki discussion can be connected with the old discussions, and can search the old discussions easily.
 * The wiki discussion can be readable with visualization instead of the text-featured mode.

Opinions about the female newcomers
The followings are the feedback about the talk page of the female newcomers.
 * 1) Female newcomers don't know whether the talk page is.
 * 2) Female newcomers are not used to do the comments on the public discussion mechanism, and usually want to weigh their words repeatedly when they do the comments.
 * 3) Female newcomers would want to know how to edit Wikipedia rather than use the talk page to communicate with the editors on the Internet.
 * 4) Female newcomers are not used to edit the talk page with Wiki Markup in comparison with the social network service (e.g. Facebook, Line). In addition, female newcomers that are not familiar with coding can feel fear for the Wiki Markup interface.
 * 5) The title of the talk page has the same style with the main page, and the female newcomers often confuse both of them esaily.
 * 6) The popular talk pages are too long to read, and the standard style of the username cannot be distinguished from other texts.
 * 7) Some customized styles of the signature on talk pages are too fancy to let the screen of the talk pages be readable.