Community Wishlist Survey 2021/Archive

This page is an archive for Community Wishlist Survey 2021 proposals that won't go on to the voting phase. Proposals may be archived for various reasons, including: the proposal is too vague, the idea is technically unfeasible, the problem has already been solved, an existing product team is already working on it, the proposal is a social/community change rather than a technical one, or the proposal is asking to remove features that WMF product teams have built.

Only members of the Community Tech or Community Relations teams should move proposals into or out of the Archive. If your proposal has been archived and there's still time before the voting phase starts, please continue the discussion on your proposal! You may be able to fix a problem with the proposal, and get it back in the survey. Once the voting phase starts on December 8, 2020, we can't move any proposals out of the Archive.


Cómo poder enviar mensajes

¿Cómo Volver A Mandar Mensajes Otra vez si se saturó solamente con Unefon ilimitado

Discussion

Add the special characters menu on the mobile visual editor

  Request withdrawn Withdrawn by proposer (too many proposals)

  • Problem: The mobile browser version of the visual editor does not have the special characters menu of the full visual editor.
  • Who would benefit: Mobile visual editors.
  • Proposed solution: Add the special characters menu.
  • More comments:
  • Phabricator tickets:
  • Proposer: Keepcalmandchill (talk) 04:26, 17 November 2020 (UTC)[reply]

Discussion

Editing infos about hurricanes

 N Unclear / incomplete proposal

Discussion

Add Better Bots

 N Lacks a clear problem statement

Discussion

The right category for the photos

  Withdrawn by proposer (too many proposals)

  • Problem: Linking the right category during the upload of a photo is not evident for all commonors. It will be ore easy to have a button in the category page to invite users to upload photos directly to the same category.
  • Who would benefit: any user navigating through photos and catgeories
  • Proposed solution: a new button in the category page to invite users to upload more photos into the category.
  • More comments:
  • Phabricator tickets:
  • Proposer: Yamen (talk) 13:24, 21 November 2020 (UTC)[reply]

Discussion

wikidata downloading

Discussion

we need to download wikidata for our organizational wiki. thanks a lot mobile:09381899129

Adding "shark", "environment", etc. to the stub type

 N Proposes change that does not require engineering 한국어: 토막글 종류에 "상어", "환경" 등 추가하기

  • Problem: There are fewer types of stubs.
한국어: 토막글 종류가 적습니다.
  • Who would benefit: Editors
한국어: 편집자
  • Proposed solution: You can increase the stub type.
한국어: 토막글 종류를 늘리면 됩니다.

Discussion

grouping, labelling, tagging in watchlists

 N Unclear/incomplete proposal

Discussion

From OSM to Wikidata

  Withdrawn by proposer (too many proposals)

  • Problem: Many information are available on OpenStreetMap that can be imported into Wikidata and therefore benefit from the work done by OSM community. Currently it's very hard to export data from OSM and import it into Wikidata: besides the problem of licence that probably can be sorted it requires technical skills to export the data.
  • Who would benefit: All
  • Proposed solution: a tool to input a filter (e.g. schools in a specific town/country) and then export data that will be imported into Wikidata.
  • More comments:
  • Phabricator tickets:
  • Proposer: Yamen (talk) 13:33, 21 November 2020 (UTC)[reply]

Discussion

Allow viewing page history in the mobile app

 N Proposes an existing feature

  • Problem: The mobile app has no option of viweing the edit history for a page.
  • Who would benefit: Mobile users.
  • Proposed solution: Allow page history to be viewable on mobile.
  • More comments: I really don't see any reason why the mobile would not include such a key function for editing.
  • Phabricator tickets:
  • Proposer: Keepcalmandchill (talk) 03:51, 17 November 2020 (UTC)[reply]

Discussion

CORRECTION: I'm wrong, please withdraw this proposal Keepcalmandchill (talk) 03:52, 17 November 2020 (UTC)[reply]

No problem. For the record keeping I'm going to archive this rather than delete the page. Best, MusikAnimal (WMF) (talk) 04:20, 17 November 2020 (UTC)[reply]

Expiratory entries in watchlists

 N Proposes existing feature

  • Problem: I don't want to watch a page for the entirety of the universe.
  • Who would benefit: Anyone with the same problem
  • Proposed solution: Next to "watchlist" you can check a box if you want it to be automatically removed from your watchlist at a certain point in time.
  • More comments:
  • Phabricator tickets:
  • Proposer: HeartGlow30797 (talk) 14:43, 22 November 2020 (UTC)[reply]

Discussion

Create a mobile app

 N Proposes an existing feature

  • Problem:
  • Who would benefit:
  • Proposed solution: wikipedia should have a app so that it will be easy and faster to use because so many people don't know about wikipedia because it a website not a app so let make to app so billions of people will have access to it on a moblie app just like google
  • More comments:
  • Phabricator tickets:
  • Proposer: JEFFERY WASHINGTON OMOCARO (talk) 21:40, 17 November 2020 (UTC)[reply]

Discussion

Have our own dictionary but with words that are not found in google dictionary

 N Proposes existing project espoñol: Tener nuestro propio diccionario pero con palabras que no se encuentran en google diccionario

Discussion

COmo lo dije en el titulo

wikt:? — Draceane talkcontrib. 21:52, 29 November 2020 (UTC)[reply]

A new style for the webpage

 N Unclear/incomplete proposal

Discussion

  • Hi Fredrich Mauro! Could you elaborate on the technical problem you're seeing? This proposal as written presents not a problem, but an opinion. What specifically about the mobile web site is old, and how do you envision it being fixed? We need you to be more clear so that voters know what they're voting for. You can learn more by reviewing our documentation on the proposal phase. I'm going to archive this proposal for the time being, but we can move it back once it's more clear. Thanks for participating, MusikAnimal (WMF) (talk) 00:37, 18 November 2020 (UTC)[reply]

Moving categories

 N Requires community consensus

  • Problem: The non-mover and non-admin users are not allowed to move categories. Sometimes, they may wish to move a category to a new category due to error in category name or wrong category.
  • Who would benefit: All users.
  • Proposed solution: Let autoconfirmed and extended confirmed users to move categories.
  • More comments: All what's above.
  • Phabricator tickets:
  • Proposer: Empire AS (talk) 07:06, 22 November 2020 (UTC)[reply]

Discussion

Any Valid Information.

 N Does not propose a technical change

Discussion

I want anyone to add their valid information at any Wikipedia pages. As long as their valid from any sources at all. If some users doesn't believe it's true. Then, that specific editor must provide their evidence from any valid source at all. So, then they can be added and not removed. So, can you accept then implement this suggestion? Please reply.

Please review the documentation before creating anymore proposals. Thank you, MusikAnimal (WMF) (talk) 01:19, 20 November 2020 (UTC)[reply]

Requests or Suggestions

  • Proposed solution: La place de position du bandeau d'informations internes serait plus adaptée ailleurs sur la page, en bas ou sous une autre forme, pour libérer le haut qu'il serait préférable de réserver au titre.
  • Proposer: Jeanlouis11170 (talk) 20:47, 17 November 2020 (UTC)[reply]

Discussion

Enable visual editing on the mobile app

  Request withdrawn Withdrawn by proposer (too many proposals)

  • Problem: Visual editing is not possible on the mobile app.
  • Who would benefit: Mobile and visual editors
  • Proposed solution: Add visual editing as a feature of the mobile app.
  • More comments: Both the mobile app and visual editing are intended to make it easier to edit. But why haven't these two great things been incorporated into one?
  • Phabricator tickets:
  • Proposer: Keepcalmandchill (talk) 04:06, 17 November 2020 (UTC)[reply]

Discussion

Nope, not on the beta app. Keepcalmandchill (talk) 12:52, 17 November 2020 (UTC)[reply]
@Keepcalmandchill and @Strainu, the mw:Mobile visual editor is available to editors using a web browser (click the button shown in this screenshot), but not in the apps. Because of technical differences, I understand that it would have to be "a" visual editor, and not the same software that's used when you edit in a web browser. Creating the software would probably be a multi-year project. Whatamidoing (WMF) (talk) 01:32, 2 January 2021 (UTC)[reply]

Zoom article editing event creation link

 N Requires community consensus

  • Problem: People lack opportunities to connect with others doing meaningful, factual things.
  • Who would benefit: Anyone looking to join others to make a difference. Democracies that depend on constituencies living in reality.
  • Proposed solution: On every article page, create a button that enables the user to create a Zoom virtual event for people to collaborate to improve that article. The event is then listed in a common event calendar searchable by date and article subject area.
  • More comments:
  • Proposer: John 14:23 (talk) 05:20, 27 November 2020 (UTC)[reply]

Discussion

  • @John 14:23: Thanks for your proposal. It would be up to the community to agree on the process and technologies to use for this type of problem. I am going to archive this proposal. Thank you again for participating in this survey! Harumi Monroy 00:14, 04 December 2020 (UTC)[reply]

Any Valid Informations.

 N Does not propose a technical change

Discussion

Anyone who provides a valid information from any kinds of sources can be added or edited to the Wikipedia pages. As long as they;re true information. So, can you forward then accept then implement it? Please reply. — The preceding unsigned comment was added by EJY257 (talk)

Similar to your other proposal, this seems to be about changing the content of articles, which is something that is not done through the Community Wishlist Survey. Please seek assistance from your local wiki, if needed. You can learn more about the Survey by reading our documentation. Thanks, MusikAnimal (WMF) (talk) 20:54, 18 November 2020 (UTC)[reply]

Traduceri Notițe

 N Outside the scope of Community Tech

  • Problemă: Imposibilitatea editării notelor și traducerii automate a template-urilor.
  • Cine ar beneficia: Toți editorii wiki + vizitatorii paginilor deoarece ar crește gradul de corectitudine.
  • Soluția propusă: Repararea acestora.
  • Mai multe comentarii: -
  • Ticket Phabricator:
  • Propunător: Dairrow (talk) 18:43, 18 November 2020 (UTC)[reply]

Discuție

Give reason when reverting edits

Original title: Every edit done by me was reverted by someone without knowing the fact whether I added the value to article or not, Such monopoly should be stopped for betterment of Wikipedia.  N Proposes a social/policy/licensing change rather than a technical feature

  • Problem: Edits on Wikipedia are reverted by auditors, that discourages the editors for further edits.
  • Who would benefit:
  • Proposed solution: Every edit's revert should be given a reason so that the editor's feelings does not get hurt.
  • More comments:
  • Phabricator tickets:
  • Proposer: Darshan Singh knl (talk) 11:07, 22 November 2020 (UTC)[reply]

Discussion

No unregistered users

 N Proposes a social/legal change rather than a technical feature

Discussion

  • Requiring account registration goes against the founding principles of Wikimedia. As such I'm archiving this proposal. Thanks for participating.
español: Requerir el registro de una cuenta va en contra de los principios fundacionales de Wikimedia. Como tal, estoy archivando esta propuesta. Gracias por participar, MusikAnimal (WMF) (talk) 19:47, 30 November 2020 (UTC)[reply]

Add dark mode for desktop website.

 N Declined in a previous survey

  • Problem: No Dark mode for web app (PC)
  • Who would benefit: The readers as your eyes dont
  • Proposed solution: Add dark mod in the settings (Web Wikipedia)
  • More comments: None, thank you
  • Phabricator tickets:
  • Proposer: Unieo: Mikhail's Unieo (talk) 05:21, 23 November 2020 (UTC)[reply]

Discussion

All As "Edit" Only.

 N Does not propose a technical change

Discussion

All of the Wikipedia pages will have the "Edit" button. There won't be anymore "View Source" button anymore in the future. So, anyone can edit and/ add any valid information at all or any Wikipedia pages. So, can you forward then accept then implement this suggestion? Please reply. — The preceding unsigned comment was added by EJY257 (talk)

Hi EJY257! It sounds like you're asking all pages to be unprotected. The protection of pages is up to local administrators. The Community Wishlist Survey is for proposing technical changes and new features. We do not handle administrative duties of wikis. For this reason I'm archiving this proposal, but thanks for participating nonetheless! MusikAnimal (WMF) (talk) 20:50, 18 November 2020 (UTC)[reply]

Admins

 N Proposes social change and/or opinion

Discussion

Wikipedia administrators should be scientists and specialists, not gamers with inflated subjective self-importance and violating the Wikipedia Rules. They consider themselves the masters of Wikipedia, although banging on the keyboard quickly is just a skill. Konstantine Gunin (talk) 09:27, 26 November 2020 (UTC)[reply]

Adding a reference

 N Not a proposal

Discussion

I wish somehow someone will add the following to the References section of the Wikipedia article on Louis Harold Gray. It’s clear from my bungled efforts that I can’t do it. Thanks. That’s all. O Underwood

Wynchank, Sinclair (2017). Louis Harold Gray, FRS: A Founding Father of Radiobiology. London, England: Springer International Publishing. ISBN 978-3-319-43396-7. OSUnderwood (talk) 09:49, 22 November 2020 (UTC)[reply]

Please edit the article directly or request edits be made on the talk page. This is the Community Wishlist Survey. We don't make content changes through this process. MusikAnimal (WMF) (talk) 19:56, 22 November 2020 (UTC)[reply]

Add more links on the pages of Wikipedia

 N Does not require engineering resources / out of scope

  • Problem: There are not enough links on the encyclopedia pages. Please consider adding more links
  • Who would benefit: The Users
  • Proposed solution: The Users should add more links like links of the meanings of words that are difficult.
  • More comments:
  • Phabricator tickets:
  • Proposer: Saregamapadhanisa (talk) 09:30, 21 November 2020 (UTC)[reply]

Discussion

text to speech

 N Proposes existing solution

  • Problem: More than 95% of the content in Wikipedia is in text format and needs to be read.
  • Who would benefit: Almost everyone! However, people with poor vision will benefit the most.
  • Proposed solution: Almost all cloud providers offer Text to Speech conversion API. In addition, there are many free libraries are available that do Text to Speech.
  • More comments:
  • Phabricator tickets:
  • Proposer: Ssathya (talk) 21:51, 19 November 2020 (UTC)[reply]

Discussion

Take a look to mw:Extension:Wikispeech -Theklan (talk) 09:34, 20 November 2020 (UTC)[reply]

Searching of words in the page

  • Problem:
  • Who would benefit:
  • Proposed solution: There should be an option by which we can search for a keyword we are looking for in the page. This helps us in saving time.
  • More comments:
  • Phabricator tickets:
  • Proposer: Excellenc1 02:50, 17 November 2020 (UTC)[reply]

Discussion

Quién se beneficiaría

 N Lacks a clear problem statement

Discussion

la sintaxis de las entradas podría ser más limpia y más similar al resultado final. Mi meta es mejorar wikipedia para ser una pagina que podamos buscar cualquier cosa y encontrar resultados verdaderos no como brainly.lat porque hay uno puede hacer cualquier cosa con preguntas y respuestas. Les dejo mi propuesta: pueden mejorar mejor calidad , no errores, una portada limpia. Mi meta es poder desarollar una mejor pagina que se pueda utilizar bien

Dynamic Spidergram

 N Unclear / incomplete proposal

Discussion

Add a tutorial

  • Problem: For people who want to make their own documentary on something but they are new to it and want to add things, but they don't know how to.
  • Who would benefit: It would benefit beginners and people who don't know how to edit.
  • Proposed solution: Like on the programming on khan academy, there should be videos explaining how to do something, while at the same time you can interact with it.
  • More comments: I understand there are youtube videos of this but if you like editing at school, I think it's a great solution.
  • Phabricator tickets:
  • Proposer: Apersonthing3000 (talk · contribs) 23:47, 22 November 2020

Discussion

  • @Apersonthing3000: Thanks for the proposal! This sounds like a great idea, but it's a content-editing project, rather than something that requires technical software development work, and as such is out of scope for the wishlist. Commons supports the uploading of videos, and they can be displayed wherever required on the wikis. As this is a non-technical proposal, I'll archive it. —Sam Wilson 07:50, 23 November 2020 (UTC)[reply]

College Football Template

 N Proposes a social change rather than a technical feature

  • Problem: When editing the page of an American football coach the colors of his or her teams are always displayed (even college teams) throughout the NFL player or coach template, however when it comes to the college football template it will not show any NFL team colors throughout
  • Who would benefit:
  • Proposed solution: I propose that the 32 NFL teams are added to the college football template, for when a college coach spend a year or two in the NFL
  • More comments:
  • Phabricator tickets:
  • Proposer: Bigmike2346 (talk) 23:49, 17 November 2020 (UTC)[reply]

Discussion

  • @Bigmike2346: Hi! This does not require engineering resources from developers. Simply update the template yourself as desired or contact maintainers of that template to make the changes for you. For this reason I'm going to archive this proposal. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 00:04, 18 November 2020 (UTC)[reply]

Recommendation for Survey instructions

 N Not a technical proposal

  • Problème:
  • Qui en bénéficierait:
  • Solution proposée: Ce point fondamental doit être mis au tout début de la présentation/page : "La proposition doit concerner une modification technique et non une politique ou une modification sociale"
  • Autres commentaires:
  • Tâches sur Phabricator:
  • Proposant: Tifroumi (talk) 14:44, 20 November 2020 (UTC)[reply]

Discussion

  • Translation: This fundamental point must be put at the very beginning of the presentation / page: "The proposal must relate to a technical modification and not a policy or a social modification". Quite frankly I agree! We can add something like this to the edit intro. Thanks for the suggestion, though for future reference you can use the talk page for this rather than create a proposal. MusikAnimal (WMF) (talk) 19:51, 30 November 2020 (UTC)[reply]

Allow watermarks on photos if requested by the content owner.

 N Proposes existing solution

  • Problem: I have lost original work (Kodachrome transparancies) but would still like to use my photos here.
  • Who would benefit: People in my position who have digitized work but are missing original content.
  • Proposed solution: 1. Change policy to allow usage; or 2. Supply a watermark-removal service.
  • More comments:
  • Phabricator tickets:
  • Proposer: BrettA343 (talk) 23:52, 20 November 2020 (UTC)[reply]

Discussion

Wikipedia Live Videos

 N Proposal is very broad, out of scope, and may require consensus

  • Problem: We should be able to see live footage of things (ex: Hurricanes, tropical storms, tornados, e.t.c ).
  • Who would benefit: Users and Editors.
  • Proposed solution: Make Live footage.
  • More comments:
  • Phabricator tickets:
  • Proposer: Avishai11 (talk) 17:15, 19 November 2020 (UTC)[reply]

Discussion

  • There is no infrastructure to allow for live video feeds, and I'm afraid inventing this may be too out of scope for this survey. Regardless, we don't have reporters on the ground working for us, rather content is written by volunteers based on previously released sources. Live video feeds could also be abused; e.g. start with a video of the tornado and turn into something inappropriate. For this reason it may require broader consensus before implementing this technology. As such I'm going to archive this proposal, but thank you for participating in the survey! MusikAnimal (WMF) (talk) 20:42, 19 November 2020 (UTC)[reply]

Antworten auf Diskussionen via mobiler Webseite

  • Problem: Wenn man auf einer Diskussionsseite in mobiler Ansicht antwortet und sich nicht im Wikitext-Modus befindet, dann werden Antworten nicht eingerückt, sprich der zusätzliche Doppelpunkt wird nicht gesetzt. Dieser Bug dürfte sich vermutlich schnell lösen lassen.
  • Who would benefit:
  • Proposed solution:
  • More comments:
  • Phabricator tickets:
  • Proposer: --Smarti (talk) 18:06, 16 November 2020 (UTC)[reply]

Discussion

Tracked in Phabricator:
Task T267813

תרגום - לא ניתן לתרגם פרקים ולהעביר אותם לערך קיים בעזרת ויקיפדיה תרגומים

 N On roadmap of another team

Discussion

Механизм удаления аккаунтов

  • В Википедии и других википроектах много неактивных участников и бессрочников,аккаунты которых не имеют смысла.Предлагаю для решения это проблемы создать механизм удаления аккаунтов:
  • Дополнительные комментарии:
  • Ссылка на задачу в Фабрикаторе:
  • 'Создал: GAZ1979 (talk) 17:12, 17 November 2020 (UTC)[reply]

Обсуждение

More access to things

 N Incomplete / unclear proposal Magyar: több hozzáférés dolgokhoz

  • Problem: little access to things
    Magyar: kevés hozzáférés dolgokhoz
  • Who would benefit: Hungarian accesses
    Magyar: magyar hozzáférések
  • Proposed solution:---
  • More comments:
  • Phabricator tickets:
  • Proposer: Koch1991 (talk) 17:14, 17 November 2020 (UTC)[reply]

Discussion

  • @Koch1991: Thanks for your proposal. Could you please elaborate further on what you want to achieve? As it stands there isn't enough information here to act on. Thanks! (Sorry for posting in English.) Sam Wilson 02:02, 18 November 2020 (UTC)[reply]
  • I'm going to archive this proposal for the time being. Once the problem statement is made more clear we can move it back. Thanks for participating in the survey.

    Magyar: Egyelőre archiválni fogom ezt a javaslatot. Amint a problémameghatározás világosabbá válik, visszahelyezhetjük. Köszönjük, hogy részt vett a felmérésben. MusikAnimal (WMF) (talk) 23:32, 19 November 2020 (UTC)[reply]

Suivi que d'une partie d'un article

  • Problème: Pouvoir suivre qu'une partie d'un article
  • Qui en bénéficierait: Tous les utilisateurs de Wikipédia
  • Solution proposée: Ajouter un lien de suivi au niveaux des sections de l'article
  • Autres commentaires: Sur des articles très long et souvent modifiés par les contributeurs, il est nécessaire de visualiser toutes les modifications effectuées les unes après les autres, afin de visualiser les changements intervenus dans les sections qui m'intéressent.
  • Tâches sur Phabricator:
  • Proposant: --13:47, 25 November 2020 (UTC)Thierry74 (talk)

Discussion

Video tutorials

 N Does not propose a technical change

  • Problem: It is often very complicated for new users to edit or contribute despite the plethora of information that exists.
    (fr): Il est souvent très compliqué pour les nouveaux utilisateurs de comment éditer ou contribuer malgré la pléthore d'information qui existe.
  • Proposed solution: To help them quickly identify this, it would be appropriate to make video tutorials that show how to contribute in all languages and this automatically on the home page of new users.
    (fr): Pour les aider à cerner rapidement cela, il serait opportun de faire des tutoriels vidéos qui montrent comment contribuer dans toutes les langues et ce automatiquement sur la page d'accueil des nouveaux utilisateurs.
  • Proposer: --Ross.Patrick (talk) 06:09, 17 November 2020 (UTC)[reply]

Discussion

Rechtschreibprüfung (D)

 N See Community Wishlist Survey 2021/Editing/Spellchecker

Diskussion

Dark Mode

 N Declined in a previous survey

  • Problem: Wikipedia does always have white theme
  • Who would benefit: Everyone that want to save their eyes
  • Proposed solution: Create Dark Mode on whole Wikipedia page
  • More comments:
  • Phabricator tickets:
  • Proposer: Kindle Uzer (talk) 15:53, 19 November 2020 (UTC)[reply]

Discussion

  • This was the #2 wish in the 2019 survey. We investigated and even began work, and as much as we wanted to finish it we unfortunately had to stop due to some technical challenges and conflicts with the Desktop Improvements project. You can learn more by reading our status report. This is not to say dark mode won't happen some day; I think it definitely will, but I'm afraid it won't be from Community Tech. As such I'm going to decline this proposal. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 02:18, 18 November 2020 (UTC)[reply]

Editing through wikipedia mobile app

 N Proposes existing feature

  • Problem: The Wikipedia app on google play is read-only. Users are not able to contribute by editing. Editing through mobile web browser is trouble to many people.
  • Who would benefit: The Wikipedia mobile app users
  • Proposed solution: Editing feature in the mobile app.
  • More comments: Editing through mobile web browser is trouble to many people. It would be better if editing feature is also available in the app.
  • Phabricator tickets:
  • Proposer: Huzaifa abedeen (talk) 03:35, 25 November 2020 (UTC)[reply]

Discussion

one-click removal from the watchlist

 N Proposes existing feature

  • Problem: If you see a page on a watchlist you no longer want to watch it takes a 3 mouse clicks to remove it (click on the page, click to remove from the watchlist, click to return to the watchlist, plus time to find where you were)
  • Who would benefit: people who want to control their watchlist
  • Proposed solution: add a link "[remove from watchlist]" next to each item to allow quick removal
  • More comments:
  • Phabricator tickets:
  • Proposer: Jarekt (talk) 21:47, 20 November 2020 (UTC)[reply]

Discussion

Enlaces rojos

 N Unclear/incomplete proposal

Discusión

Mi idea es rapida y sencilla aunque no se podria llevar a la practica es crear bots para identificar enlaces rojos utiles de aquellos que no lo son y eliminar los que no lo son y poner enlaces rojos para paginas que si se podrían crear nuevas paginas utiles para la comunidad y los lectores anonimos,esto benefeciaria a ciertos articulos en todos los idiomas llenos de estos enlaces faltos de utilidad y pondria estos enlaces posibilitando la creacion de nuevos articulos utiles para tod@s esa es mi idea para mejorar wikipedia protente Dr.Mas20

ejercicios para desarrollar en medio de un articulo

 N Proposes existing solution

  • Problema: comprensión de explicaciones en algunos temas, por ejemplo matemáticas, idiomas, alimentación, programación, etc..
  • A quiénes beneficiaría: principalmente a estudiantes y personas con curiosidad sobre un el tema.
  • Solución propuesta: añadir ejercicios dinámicos en el articulo después de la explicación, de manera que el lector pueda intentar resolverlo y pueda confirmar la solución una vez realizado el intento, y así poder conocer por si mismo su comprensión de lo explicado.
  • Más comentarios: pienso que simplemente se pueden añadir ejercicios de algunos libros de texto o de otras páginas web.
  • Informes de Phabricator:
  • Proponente: Dairo Quintero Vargas.

Discusión

Wikipedia API

 N Unclear proposal

  • Problem: it isn't too easy to develop new bots for Wikipedia.
  • Who would benefit: the community, the readers, the editors and the programmers.
  • Proposed solution: creating a Wikipedia Developer Platform just like Twitter has a Twitter Development. Creating an API that gives easy access to Wikipedia.
  • More comments: No more comments.
  • Phabricator tickets:
  • Proposer: Albin Schmitt (talk) 22:57, 18 November 2020 (UTC)[reply]

Discussion

Single out the content translation module

  Withdrawn by proposer (too many proposals)

  • Problem: Content translation module needs to be activated in beta features per wiki, and is definitely problematic considering the code to be the same across multiple languages. Also, this is limited to Wikipedia when the module can be used in multiple occasions (e.g. wikiversity)
  • Who would benefit: Anyone who would need to use this module + wikipedia(and other projects') event participants
  • Proposed solution: Turn the current translation module into a standalone website/product (i.e. translate.wikimedia.org), and let it import pages from any Wikimedia sites and export it at any sites' user namespace
  • More comments: I suppose the whole thing needs to be manually checked considering the whole controversy behind the "bad translation" thing due to bad moderation that can be done(external force nonexistent). Thus, I suggest turning off the export to mainspace and restrict it to only export on user namespace unless the community had a thereshold to open it.
  • Phabricator tickets:
  • Proposer: 1233 T / C 06:01, 19 November 2020 (UTC)[reply]

Discussion

Wikiübergreifende Beobachtungsliste

 N In Entwicklung

  • Problem: Wenn man Seiten in verschiedenen Wikis beobachtet (WikiCommons, Wikidata, en.wikipedia, de.wikipedia usw), fällt es schwer, den Überblick über alle Beobachtungslisten zu behalten.
  • Wem würde dieser Wunsch helfen: Benutzern, die in mehreren Wikis tätig sind.
  • Lösungsvorschlag: Eine Gesamt-Beobachtungsliste, in der die Änderungen von beobachteten Seiten aus allen Wikis zusammengefasst wird.
  • Weitere Kommentare:
  • Phabricator-Tickets:
  • Antragsteller: Grullab (talk) 10:58, 17 November 2020 (UTC)[reply]

Diskussion

Rich search suggestions for desktop

  • Problem: Search on the mobile website displays suggestions that include the Short Description and a thumbnail image. The search on the desktop website does not.
  • Who would benefit: All users of the desktop website
  • Proposed solution: Update the search on the desktop website to display the same rich suggestions as the search on the mobile website.
  • More comments:
  • Phabricator tickets:
  • Proposer: — GhostInTheMachine talk to me 17:09, 25 November 2020 (UTC)[reply]

Discussion

This is already being worked on as part of the Desktop Improvements project. the wub "?!" 17:33, 30 November 2020 (UTC)[reply]

GhostInTheMachine, hello and thank you for submitting this proposal! Since this is already being worked on as part of the Desktop Improvements project, we will be archiving this wish. You can follow this feature request via the Desktop Improvements project. Thank you! IFried (WMF) (talk) 00:08, 3 December 2020 (UTC) [reply]

Centralization of templates

 N Outside the scope of Community Tech

  • Problem: Projects use similar templates but without joining the efforts of its developers in the different languages and above all this system is preventing the harmonization of the content. Although Wikidata has made it possible to do a some links, it is rare to align with templates from other projects.
  • Who would benefit: Everyone, especially developers and translators.
  • Proposed solution: Create a common meta space where all templates would be centralized and used independently of the project.
  • More comments: This has to be one of the biggest challenges of the projects for the years to come. Centralizing templates would allow the different language versions to evolve more jointly. This will also greatly facilitate translations. Without forgetting the concerns on licenses when copying the templates to another project.
  • Phabricator tickets:
  • Proposer: Baidax (talk) 16:55, 30 November 2020 (UTC)[reply]

Discussion

Return to default table sorting

 N Proposes existing feature

  • Problem: When sorting wikitable sortable, the sorting order is changed by the selected column. If there is no numbered column (e.g. 1-2-3-4…), a page reload is the only way to return to the default sorting.
  • Who would benefit: Readers
  • Proposed solution: Add a button to the corner of the table that would reset the table to the default sorting.
  • More comments:
  • Phabricator tickets:
  • Proposer: — Draceane talkcontrib. 21:34, 29 November 2020 (UTC)[reply]

Discussion

Add more machine translators to the translation editor

 N Proposes existing feature and financial/licensing change

  • Problem: The only machine translator available is the Google one, which is imperfect in many ways (can't handle dates very well, for example).
  • Who would benefit: Translators.
  • Proposed solution: Add more translation software options, such as Bing or Yandex translators.
  • More comments: This is of course not relevant to English Wikipedia. But it would be important for other languages, especially since Google Translate is most useful in English translation.
  • Phabricator tickets:
  • Proposer: HappyMihilist (talk) 16:09, 18 November 2020 (UTC)[reply]

Discussion

ブロック期間。

 N Proposes a social/policy change rather than a technical feature

  • 問題点: 明らかに間違っていることを書く者、嫌がらせをする者はブロックし、少なくとも数ヶ月か半年か.....長期間利用できないようにするのがいいと思います。wikipediaさんが現在どれだけの期間、利用できなくなるのかあまり調べていませんが。気になったので書かせていただきます。こういう人たちにいちいちかまうのは、かなり時間を無駄にしていると思いますので。ブロックすることを決めているのは一部の方々だと思いますが。その方々が不憫です。
  • 誰の役に立つか: ブロックすることを決めている方々。
  • 提案された決議:
  • その他のコメント:
  • Phabricator チケット:
  • 提案者: Taroukotarou (talk) 21:24, 17 November 2020 (UTC)Taroukotarou[reply]

議論

  • This proposal seems to be political or asks to change social behaviour on one or more projects. The Wishlist Survey is for requesting technical changes and improvements to the software you use. We can't help with the issue you speak of here. Regards, MusikAnimal (WMF) (talk) 17:22, 1 December 2020 (UTC)[reply]

CommunityCare

 N Proposes a social/policy change rather than a technical feature

  • Problem: Die deutschsprachige Wikipedia verliert seit Jahren engagierte User. Diese werden völlig alleine gelassen und ihnen kann unter dem aktuellen Gruppendruck nicht einmal mehr von Freunden und Kollegen Hilfe angeboten werden.
  • Wem würde dieser Wunsch helfen: Es geht darum, dass das editieren wiederum Spass macht und das Grundprinzip von NPOV wiederum zur vollten Geltung gebracht werden kann.
  • Lösungsvorschlag: In Sperrverfahren bekommen die ausgeschlossenen AUTOMATISCH eine (professionelle, WMDE, WMAT, WMDE finanzierte (Wikimedia 2030 Ziel: Inklusion) und mit entsprechenden Kompetenzen ausgestattet) "Pflichtverteidigung" zur Seite gestellt.
  • Weitere Kommentare: Wir haben bei WikiDienstag.ch eine Definition zu #CommunityCare entwickelt, welche 3 Punkte umfasst:
  1. To be a Party Host and
  2. To be a Traffic Cop (Not Police Officer).
  3. Always be a Full-time Enabler

Diskussion

Disallow IP editing on Meta

 N Requires community consensus and/or legal approval

  • Problem: Currently IPs are allowed to edit on Meta as well as on other WMF projects. One could make a case for allowing IP editing on content building WMF projects where some editors occasionally want to make a few edits without registering an account. But nobody comes to edit here on Meta without knowing exactly what they are doing. The practice of allowing IPs to edit on Meta only serves to enable sockpuppetry, block evasion and straightforward vandalism.
  • Who would benefit: Everybody.
  • Proposed solution: We should require mandatory account registration for editing on Meta. Or, at a minimum, have a rule that IPs are not allowed to participate in any Meta RfCs and other polls.
  • More comments:
  • Phabricator tickets:
  • Proposer: Nsk92 (talk) 21:15, 17 November 2020 (UTC)[reply]

Discussion

  • This is just a configuration change. No engineering is required for this to happen, so it doesn't need to go through the wishlist. All it needs is community consensus and possibly also approval from WMF legal. If you wanted to disallow contribs from IPs to RfCs, that can probably be achieved using AbuseFilter, but again it would need consensus. For these reasons I'm going to archive this proposal. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 21:28, 17 November 2020 (UTC)[reply]

Thanking unregistered users

 N Needs consensus / conflicts with privacy enhancement project

  • Problem: Not being able to thank an unregistered user
español: No poder agradecerle a un Usuario No Registrado.
  • Who would benefit: Unregistered users
español: Los usuarios No Registrados.

Discusión

español: De hecho, no se llegó a un consenso sobre cómo manejar esto en el pasado. Independientemente, no deberíamos intentar implementarlo en este momento porque entra en conflicto con IP Editing: Privacy Enhancement and Abuse Mitigation. Por eso voy a archivar esta propuesta, ¡pero gracias por participar en la encuesta! MusikAnimal (WMF) (talk) 22:51, 23 November 2020 (UTC)[reply]

Dark theme

 N Declined in a previous survey

Discussion

[User: PittsburghPlays] - Definitely a feature they should add. Been waiting for years!

  • This was the #2 wish in the 2019 survey. We investigated and even began work, and as much as we wanted to finish it we unfortunately had to stop due to some technical challenges and conflicts with the Desktop Improvements project. You can learn more by reading our status report. This is not to say dark mode won't happen some day; I think it definitely will, but I'm afraid it won't be from Community Tech. As such I'm going to decline this proposal. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 02:18, 18 November 2020 (UTC)[reply]

Sandbox shortcut in Simple English, Yoruba Wikipedia,Meta with others

 N Proposes an existing feature

  • Problem: Provision of sandbox sidebar in simple English Yoruba Wikipedia Meta and others
  • Who would benefit: All users will benefit due they will be able to navigate around easily to their sandbox.
  • Proposed solution: Addition of sandbox in the sidebar.
  • More comments:
  • Phabricator tickets:
  • Proposer: Tbiw (talk) 21:58, 17 November 2020 (UTC)[reply]

Discussion

The sidebar can be customised per-wiki by editing MediaWiki:Sidebar. A more general suggestion that may be relevant is Community Wishlist Survey 2021/Miscellaneous/Customizable sidebar. H78c67c (talk) 07:09, 18 November 2020 (UTC)[reply]

There's already mw:Extension:SandboxLink which adds a link to the current user's sandbox to the personal tools menu (same menu that has links to user/user talk pages and preferences, for example) that can be enabled on any wiki that requests it. Majavah (talk!) 07:56, 18 November 2020 (UTC)[reply]

В Википедии добавить кнопочку для гуглоперевода статьи.

  • Проблема: не все статьи есть на родном языке, много времени уходит чтобы перевести
  • Кто выиграет: читатели
  • Предлагаемое решение: встроить автоперевод - добавить кнопочку для гуглоперевода статьи
  • Дополнительные комментарии:
  • Ссылка на задачу в Фабрикаторе:
  • Предложил(а): denis_73 (talk) 20:37, 17 November 2020 (UTC)[reply]

Обсуждение

В каждом броузере уже есть такая функция. Воспользуйтесь ей. SSneg (talk) 21:39, 20 November 2020 (UTC)[reply]
denis_73, Спасибо, что отправили это желание! Мы храним это желание, потому что оно выходит за рамки. Однако мы рекомендуем вам взглянуть на это. Вам может быть интересно: https://www.mediawiki.org/wiki/Content_translation IFried (WMF) (talk) 21:12, 3 December 2020 (UTC)[reply]

Make wiki easier for most people

 N Proposal too broad / out of scope

  • Problem: A lot of things are complicated and nerdy requiring a lot of knowlegde about the system
  • Who would benefit:
  • Proposed solution: A user interface which is more friendly to people who do not know a lot about all the nerdy stuff. Clean up clutter, less is more. Cleaner menues, better visuals.
  • More comments:
  • Phabricator tickets:
  • Proposer: Raven rs (talk) 01:16, 18 November 2020 (UTC)[reply]

Discussion

  • Hi Raven rs! While I think many people will agree there is a learning curve to MediaWiki, this proposal does not do much beyond broadly stating the problem. In the Wishlist Survey, we ask you to present specific problems and (ideally) specific solutions that can be tackled reasonably by our team. This proposal as written is much too broad. Redesigning the whole system does not fit within our scope. You can learn more about the survey by reading the documentation. For now I'm going to archive this proposal, but if you have more specific and smaller ideas to improve MediaWiki, please clarify and we can move your proposal back. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 04:04, 18 November 2020 (UTC)[reply]

سلام

Bonjour et ne sois pas fatigué Apprenez du code à utiliser qui est très important

Autorize OpenDocument import

 N Requires community consensus

  • Problem: Actually, it's autorized to import : tiff, tif, png, gif, jpg, jpeg, webp, xcf, mid, ogg, ogv, svg, djvu, stl, oga, flac, opus, wav, webm, mp3, midi, mpg, mpeg.
  • Who would benefit: All
  • Proposed solution: WikiCommons could autorize OpenDocument filetype.
  • More comments:
  • Phabricator tickets:
  • Proposer: ComputerHotline (talk) 07:46, 17 November 2020 (UTC)[reply]

Discussion

See c:Commons:Project_scope#PDF for the policy. On Wikisource PDF and DjVu is used only from scans and then the text improved. There is no need for that with OpenDocument. Also in the policy it states that text only files are not permitted (you would copy the text to an wikipage, if it is out of copyright, in that case).--Snaevar (talk) 23:12, 28 November 2020 (UTC)[reply]

Remove (very) old entries from the block log

 N Requires community consensus

  • Problem: At face-value a user's block log can be used to the detriment of on an editor.
  • Who would benefit: Everyone to avoid time-sinks debating the behaviour of an editor who made mistakes in the past, but has improved.
  • Proposed solution: Much like penalty points for driving (in the UK), older blocks should be expunged from the log after a sufficient amount of time has passed (5, 8, 10 years??)
  • More comments:
  • Phabricator tickets:
  • Proposer: Lugnuts (talk) 14:57, 28 November 2020 (UTC)[reply]

Discussion

Administrators can hide log entries. You have to discuss the wish in your local community. Technically nothing can be done here.--𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 15:10, 28 November 2020 (UTC)[reply]
  • I don't think it's possible to automatically hide old log entries right now, but it seems extremely unlikely this would get implemented as it's contrary to the open principles of MediaWiki. Regardless, each community would have to make that decision for themselves. I'm going to archive this proposal as needs consensus. Thanks for participating, nonetheless! MusikAnimal (WMF) (talk) 15:42, 28 November 2020 (UTC)[reply]

searching categories on commons

 N Same as Community Wishlist Survey 2021/Categories/Display categories before pages

  • Problem: When typing to search field in comons, suggester suggest names of files and galleries, but not categories. ALso after search there are in results on the first place galeeries and then files. Categories are on the n-th page, when there are more than 20 results
  • Who would benefit: All users who search images for known thema with more images
  • Proposed solution: add option to include categories in basic search
  • More comments:
  • Phabricator tickets:
  • Proposer: JAn Dudík (talk) 21:29, 24 November 2020 (UTC)[reply]

Discussion

  • Possibly this is just something that needs a change of the default configuration. At the moment you have to click on 'search categories' to see the category search results; that could become the default, or a mix of categories/files/galleries could be the default. Searching categories should work a lot better now that the infobox is in so many categories (particularly for multilingual search). Thanks. Mike Peel (talk) 08:32, 27 November 2020 (UTC)[reply]
  • Categories are included in the default search, they just come last so you may never see them. Display categories before pages seems to propose the same thing, so I'm going to archive this wish in favour of that one. Hope this is okay :) MusikAnimal (WMF) (talk) 01:00, 3 December 2020 (UTC)[reply]

Einspruchsmittel gegen Administratorwillkür

 N Proposes a social/policy change rather than a technical feature

  • Administratoren agieren selbstherrlich wie Gutsherren und kleine Könige, gegen ihre Entscheidungen sind keine Einspruchsmöglichkeiten und Rechtsmittel vorhanden:
  • Allen einfchen Mitgliedern außerhalb der Wiki-Hierarchie:
  • Strafmaßnahmen durch Administratoren und andere Funktionsträger mit erweiterten Rechten bewirken die Einblendung einer »Einspruch«Schaltfläche. Die Einsprüche werden direkt zu einem in jedem Wiki zu schaffenden Gremium weitergeleitet, das personell nicht mit der Administratorenhieraerchie verbunden ist. Der Wechsel von Personen zwischen beiden Gremien wird konsequent ausgeschlossen. Administratoren werden zusätzlich rechenschaftspflichtig, ihre Amtszeit und Wiederwählbarkeit wird begrenzt. Die Einsprüche werden in der Sprache des Gemaßregelten abgehandelt. Unbefristete Maßregelungen werden abgeschafft. Administratoren, die ihre erweiterten Rechte missbrauchen, riskieren ihrerseits eine Sperrung, in schweren oder wiederholten Fällen den Ausschluss. Maßnahmen gegen Administratoren werden öffentlich gemacht.:
  • Weitere Kommentare:
  • Phabricator-Tickets:
  • Antragsteller: Falk2 (talk) 12:27, 29 November 2020 (UTC)[reply]

Diskussion

accents for foreign languages and names

 N Proposed existing feature

  • Problem: When typing in names that have various types of accents over individual letters, there is no simple way to get an accent.
  • Who would benefit: Newer editors creating or expanding pages.
  • Proposed solution: Create a choice of symbols. In Microsoft word I can just go to symbols and there are many accents to choose from. In microsoft word I can go to "symbols" and choose from many.
  • Phabricator tickets:
  • Proposer: ~SallystantonsaundersSallysstantonsaunders (talk)

Discussion

Searching for the intersection of articles

 N Proposes existing solution

  • Problem: Trying to find articles that share or don't share a relationship (articles sharing category A and category B; articles linking to both article A and article B; articles using template A and template B; articles using category A, category B, but not category C; etc.).
  • Who would benefit: Those exploring/browsing wikipedia, but also those looking for inconsistencies or gaps across defined topic areas, categories, and pages without appropriately assigned topic areas/categories.
  • Proposed solution: Method to see attributes of an article and/or attributes of a second article, select/deselect these attributes, and allow the user to search for articles with similar intersections (an 'intersection' meaning containing the same selected and deselected attributes). I believe Advanced Search allows for this in some ways, but not in such a manner where it self-populates the attributes of an article for you in order to assist the user in query building further.
  • Phabricator tickets:
  • Proposer: Engineerchange (talk) 05:10, 18 November 2020 (UTC)[reply]

Discussion

Name people without accounts "Guests"

 N Already in progress

  • Problem: If you are not logged in, and you try to edit a page, it says that it will share your IP address. Not only is this annoying, but it is invasive for privacy.
  • Who would benefit: Anyone who is edits and does not have a account
  • Proposed solution: Name people without accounts "Guest", then a unique number. This will remove the problem as it will not share the IP addresses, and it allows moderators to track down vandalism with the number.
  • More comments:
  • Phabricator tickets:
  • Proposer: BCM28 (talk) 15:37, 17 November 2020 (UTC)[reply]

Discussion

OCR tool

 N Already in road map for Community Tech team

Discussion

Contributions from under-resourced countries

 N Proposes a social/policy change rather than a technical feature

  • Problem: Many countries have limited resources available to support creating and improving articles on Wikipedia, with few newspapers and the like having archives readily available online, etc.
  • Who would benefit: Any one trying to contribute from most of the world.
  • Proposed solution: After I have spent many hours crafting an article from the meagre resources available, DO NOT delete it or object to it or anything like that, just because it does not meet the extreme standards of the very few massively rich countries with infinite resources available online for free. This is why Wikipedia is so heavily biased towards content about well-resourced countries. Otherwise, it is completely pointless that I waste my time trying to improve Wikipedia. Of course, it will be fantastic if instead of complaining about the lack of references, you were to fund the Wikipedia contributors to go and seek out the needed references in the paper-based archives in countries lacking massive online archives of everything.
  • More comments:
  • Phabricator tickets:
  • Proposer: Drackles (talk) 22:13, 26 November 2020 (UTC)[reply]

Discussion

What is the right venue?

Dark color theme

 N Declined in a previous survey

 
Wikibooks project in French with dark color theme.
  • Problem: Colors of wikimedia projects are white or near white, which on long view time causes damage to eyes, and consume more energy on laptop.
  • Who would benefit: Everyone
  • Proposed solution: Add a preference to activate a dark color theme for desktop/laptop computer.
  • More comments: This preference should activate an alternative stylesheet with dark colors for every wiki elements. And colors used in pages and templates should use alpha components to appear differently on white and dark background color.
  • Phabricator tickets:
  • Proposer:  ◄ David L • talk ► 08:05, 20 November 2020 (UTC)[reply]

Discussion

  • This was the #2 wish in the 2019 survey. We investigated and even began work, and as much as we wanted to finish it we unfortunately had to stop due to some technical challenges and conflicts with the Desktop Improvements project. You can learn more by reading our status report. This is not to say dark mode won't happen some day; I think it definitely will, but I'm afraid it won't be from Community Tech. As such I'm going to decline this proposal. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 20:04, 20 November 2020 (UTC)[reply]

To be able to delete small sized articles

  • Problem: Whenever I move an article, old page redirects to the renamed article. And if old and new names of the page are unrelated, we have to delete the old one. It is frustrating to consult a authorized person everytime we do this. It would be good if at least extended confirmed users could delete small sized pages.
  • Who would benefit: User who don't have extensive authorities and therefore cannot delete pages.
  • Proposed solution: Users who have at least some experience should be able to delete small sized pages.
  • More comments:
  • Phabricator tickets:
  • Proposer: Visnelma (talk) 23:23, 20 November 2020 (UTC)[reply]

Discussion

উইকিনিউজ পুরোপুরিভাবে চালু করা

  • সমস্যা: উইকিনিউজ পুরোপুরিভাবে চালু করা
  • কে উপকৃত হবে:সঠিক খবরের পাঠক
  • প্রস্তাবিত সমাধান:যাচাই-বাছাই করে দ্রুত উইকিনিউজ চালু করা
  • আরো মন্তব্য: এতে ফেইক ও ভূয়া নিউজ ছড়িয়ে পড়া রোহ হবে
  • ফ্যাব্রিকেটরে টিকেট:
  • প্রস্তাবকারী:TAUSIFnAKBAR TAUSIFnAKBAR (talk) 16:54, 19 November 2020 (UTC)[reply]

আলোচনা

আপনাকে আগে বাংলা উইকিসংবাদে অবদান রাখতে হবে। একটা সক্রিয় সম্প্রদায় গড়ে তুলতে হবে। তারপর ভাষা কমিটি উইকিসংবাদ চালুর অনুমতি দিবে। এখানে অবদান রাখুনআফতাবুজ্জামান (talk) 05:10, 23 November 2020 (UTC) [reply]

Ryan and Shane's Bridge

 N Out of scope

Discussion

Okay so..... this is the first thing I've ever posted on Wiki. I made an account just for this. On the Old Alton Bridge Wikipedia page, it is listed as "Old Alton Bridge, also known as Goatman's bridge". I believe that the bridge has been stolen by Ryan Bergara and Shane Madej from Buzzfeed Unsolved, and therefore, it isn't Goatman's bridge anymore. I say, either make this read "Old Alton Bridge, also known as Goatman's bridge, or Shane and Ryan's bridge," or "Old Alton Bridge, also known as Shane and Ryan's bridge." Thank you. — The preceding unsigned comment was added by Why am I Evan Heere (talk)

Hi Why am I Evan Heere! This is the Community Wishlist Survey, where you propose ideas for technical improvements to software used in the Wikimedia movement. We do not handle or moderate Wikipedia content through this survey.

I see Old Alton Bridge is currently protected. You can use this link to request changes be made, or simply start a discussion on article talk page. Hope this helps, MusikAnimal (WMF) (talk) 01:04, 19 November 2020 (UTC)[reply]

A bot

 N Unclear proposal / out of scope

  • Problem: too many content getting deleted as inapropriate if you share content from your own blog,link(is that not free information??)...etc... knowing where and when to share content would improve speed of posting accurate content to wikipedia platform it self...also once you would know where you can post what it would make it easier to post new content who ever you would be...new to wikipedia or pro...
  • Who would benefit:
  • Proposed solution: A bot that would tell you if text you submitted is good or bad and if bad it then would be revieved but if good then it would be automatically submitted instead of waiting or later deleted as inapropriate. Solution for this problem is simple : automatic bot that would know what where to put maybe a categories(or similar to like youtube has livestream or upload)which would included also new sites content information, also it would check if for like site content(not posting virus or porn...) but it would include content with https:// safe sites and content
  • More comments:
  • Phabricator tickets:
  • Proposer: Fortniter2728 (talk) 16:54, 19 November 2020 (UTC)[reply]

Discussion

  • Hello Fortniter2728! I admit I am unable to make much sense of your proposal. But what I can tell you is no bot will be able to tell you whether or not the content you try to add to the wiki will stay, because humans make these decisions. I have archived this proposal for the time being as unclear/out of scope. You can learn more about writing a good proposal by reading the documentation. Thanks, MusikAnimal (WMF) (talk) 17:58, 19 November 2020 (UTC)[reply]

Add Wikipedia categories to the Wikidata element

 N Proposes existing feature

  • Problem: It should be easy to find (via Wikidata Query Service) pages that are miscategorised (e.g. no birthplace category on the Wikipedia page even though a place has been entered in Wikidata).
  • Who would benefit: Wikipedia editors
  • Proposed solution: Add Wikipedia categories to the Wikidata element. Indeed, each category has a wikidata element. It must be possible to link the category to the Wikipedia pages that contain it via Wikidata. The difficulty lies in the number of elements across all the languages of Wikipedia.
  • More comments:
  • Phabricator tickets:
  • Proposer: Pelanch3 (talk) 08:29, 24 November 2020 (UTC)[reply]

Discussion

Enable visual editing for talk pages

  Withdrawn by proposer (too many proposals)

  • Problem: Visual editing is disabled on talk pages.
  • Who would benefit: Visual editing users.
  • Proposed solution: Enable visual editing for talk pages.
  • More comments: Visual editing is far more intuitive for the average non-experienced user, and it would good to encourage more talk page participation by allowing the visual editor to be used there as well. And even more experienced editors such as myself can greatly prefer visual editing.
  • Phabricator tickets:
  • Proposer: Keepcalmandchill (talk) 04:01, 17 November 2020 (UTC)[reply]

Discussion

A proper image and video search results page

 N Proposes existing solution

  • Problem: The search page is not too bad to search text pages, but utterly terrible to search images or videos. On my 1920x1080 computer, this search only shows 5 minuscule thumbnails at a time. On my 1280x720 mobile phone, this search only shows two minuscule thumbnails at a time. The search page shows more white background than anything.
  • Who would benefit: Readers
  • Proposed solution: The search page should show images and videos with a tiled grid format, like Google or Creative Commons. There should be an option to change the thumbnail size. When the user clicks on an image, it should show the full-size preview.
  • More comments:
  • Phabricator tickets:
  • Proposer: NaBUru38 (talk) 18:14, 21 November 2020 (UTC)[reply]

Discussion

Editable edit summaries

 N Outside the scope of Community Tech

  • Problem: It is common for editors to make an error in an edit summary, or wish to expand the edit summary. There is no ability to fix an edit summary after an edit is submitted. Editors will sometimes make a null edit just to correct a prior edit summary.
  • Who would benefit: All editors.
  • Proposed solution: Allow edit summaries to be edited by the person who made the edit. This could perhaps be limited to that editing session to prevent suppression of edit summaries that are being used in dispute resolution.
  • More comments:
  • Phabricator tickets:
  • Proposer: Hammersoft (talk) 13:05, 25 November 2020 (UTC)[reply]

Discussion

Add articles with templates about problems with the content into the 'suggested edits' que

  • Problem: The suggested edits are all very basic and boring, and not that useful to the community.
  • Who would benefit: Editors looking to improve articles.
  • Proposed solution: Add articles which have been flagged with a template of common problems (poorly written, lack of sources, etc.) into suggested edits.
  • More comments: The suggested edits function should also be itself added to the web version.
  • Phabricator tickets:
  • Proposer: HappyMihilist (talk) 16:17, 18 November 2020 (UTC)[reply]

Discussion

Thanks for your response and clarification, HappyMihilist! We will be archiving this proposal, since it is directly related to the Growth team work (and we don't reverse the work of other teams or work on projects that other teams are currently working on). However, this feedback may be very useful for the Growth team to see. For this reason, we recommend that you file a Phabricator ticket and tag the Growth team, where you can directly interact with them about the Suggested Edits feature. Thank you! --IFried (WMF) (talk) 21:37, 2 December 2020 (UTC)[reply]

Separate pages for editors and Users, So authentic information can only be provided to users

 N Requires community consensus / proposes existing feature

  • Problem:
  • Who would benefit:
  • Proposed solution: There should be separate pages for users and editors of a same topic/page, so only authentic information can be provided to users. In such a way that, Information edited/added/removed from editors' page appearing on users' page only after being reviewed by a confirmed user(editor)/ or only after a certain time period ( like 24 hours). So users are only shown authentic information/fact instead of any random edit by any random editor. It will increase more authenticity of information/fact/data on Wikipedia. Thank you.
  • More comments:
  • Phabricator tickets:
  • Proposer: Zainalee (talk) 05:01, 20 November 2020 (UTC)[reply]

Discussion

  • Hello Zainalee! Part of the reason Wikipedia became so successful is its philosophy that everyone should be able to edit. There are of course some topics that are subject to more misinformation, but fortunately there many solutions to deal with this. What you are describing sounds a lot like pending changes protection. This level protection means edits from new users must be reviewed before they are visible to most readers. The threshold of what constitutes a "new user" in this context is configurable, and it's even possible to make a second layer of protection where only experienced users are immediately visible. This is not currently enabled, but it can be if there is consensus to enable it. That will need to be decided by the community, and not here in the Survey. As such I'm going to archive this proposal. Nonetheless we thank you for participating! MusikAnimal (WMF) (talk) 20:43, 20 November 2020 (UTC)[reply]

Relatively unknown music bands

  • Problem: musicians all over the world are competing with each other. They are sometimes doing interesting things but do not have the funds to have a PR department, like the bigger bands have. This creates the idea that only big, rich music groups are relevant, while it also takes away possibilities for starting and unknown bands.
  • Who would benefit: These starting and unknown bands would now be able to point at a wikipedia entry, which makes them visible and more relevant. It may not be the taste of millions but the field of live music entertainment is diverging into smaller clusters.
  • Proposed solution: a new category 'unknown music bands' in where they can share their bio, and music, so as to be more visible to the world. I really hate it when I hear 'we're not going to include your 'garage band' and have to give in to the demand that my relevance is connected to the number of publications (a very contemporary view in the science industry) while these media are owned by a tiny group of people whose taste may or may not be similar to that of these unknown bands. Take them out of obscurity!
  • More comments: Most media are converging their views, thus excluding interesting developments as the shovel guitar, or cigarbox guitar, or home made electric cello. This of course also has economic effects: if my pages constantly get pulled, my PR is as well failing.
  • Phabricator tickets:
  • Proposer: Basvossen (talk) 21:04, 25 November 2020 (UTC)[reply]

Discussion

  • @Basvossen: Thanks for your proposal, but this is a content-related proposal and not something relating to technical software development, and so is out of scope for the Wishlist Survey. I'll move it to the archive. —Sam Wilson 00:40, 26 November 2020 (UTC)[reply]

Fonctions très utiles

 N Invalid proposal

Bonjour l'Équipe Tech ! Je m'appelle MrLune. Voici ma liste des idées pour Wikipédia (site) :

Astérix (signe) = Que pour les utilisateurs

  • Un thème sombre sur le site sinon je vais encore avoir des yeux qui se réveil pas le jour !
  • Une UI révisée car celle-ci traîne depuis longtemps
  • Un bouton "Révoquer" pour enlever des modifications car c'est plus pratique surtout pour les mobiles*
  • Des bandeaux plus petits (comme le Wikipédia espagnol ou anglais)
  • La possibilité de modifier le texte gris en dessous du titre de page car parfois y'a rien ou sinon c'est un mauvais texte*
  • Le système bloque automatiquement la permission de créer des pages utilisateurs sans être la cible (en gros bloquer une adresse IP de créer la page d'un admin)
  • Une redirection automatique pour plus d'accents, pour les majuscules ou les tiret-bas (_) (je sais pas comment ça s'appelle)

C'est tout ! J'espère que touts les idées (ou une d'entre elles) sera mise dans le site :).

Cordialement MrLune (talk) 18:07, 20 November 2020 (UTC)[reply]

Discussion

  • @MrLune: Bonjour MrLune! Vous devez créer une proposition distincte pour chaque idée. Si vous pouvez utiliser le bureau, veuillez le faire car il utilisera les modèles lorsque vous créerez vos propositions. Il existe actuellement un bug qui pose des problèmes aux personnes soumettant des propositions sur mobile. Vous êtes également limité à ne faire que trois propositions au maximum. Pour plus d'informations, consultez la documentation.

    "Un thème sombre" Je suis désolé, ça ne peut pas être fait. Voir Community Tech/Status report for 2019 wishlist#Night Mode pour plus d'informations. Merci d'avoir participé à l'enquête! MusikAnimal (WMF) (talk) 21:30, 21 November 2020 (UTC)[reply]

avance tecnologico

 N Unclear proposal / needs clarification

  • Problem: slowness of the page and little progress
español: lentitud de la pagina y poco avances
  • Who would benefit: better experience and quality of the reader and for greater speed when opening the page, the beneficiary will be the reader and the users
español: mejor experiencia y calidad del lector y para mayor rapidez al abrir la pagina el benificiado sera el lector y los usuarios
  • Proposed solution: enable the page for faster reader
español: habilitar la pagina para mayor rapidez para el lector

Discussion

I believe this does not have much to do with bots and gadgets, unless gadgets are severely affecting page performance, which I cannot comment on with much certainty. H78c67c (talk) 19:36, 20 November 2020 (UTC)[reply]

Create a Wiktionary mobile app

 N Outside the scope of Community Tech

  • Problem: Much like Wikivoyage and other Wikimedia projects, Wiktionary is rather inconvenient to use on a mobile browser. In addition, it also runs into the same issue of trad/simp switching being difficult when using the Chinese version on mobile.
  • Who would benefit: Existing Wiktionary users as well as language learners, enthusiasts, and people who need to look up words in a dictionary in general.
  • Proposed solution: Create an app similar to the Wikipedia app with a better UX. Have a solution similar to said app with different traditional and simplified versions being displayed as needed.
  • More comments: Adding a pop-up dictionary to look up highlighted words or phrases would be great, and I think it would be the most useful feature for many people.
  • Phabricator tickets:
  • Proposer: MSG17 (talk) 17:33, 26 November 2020 (UTC)[reply]

Discussion

Documentation page for Wikidata items and properties

 N Does not propose a technical change

  • Problem : Wikidata is great but it still a very complex universe. My opinion is that there is a lack of comprehensive resources in Wikidata and a lack of documentation. Properties have a documentation template which is hidden in the discussion page (see Property documentation). This is page is messy.
  • Proposed solution : One could imagine something clearer with real questions such as How many items use the property? What is the nature of (p31) of items using the property, etc. My opinion is that documentation should also be discoverable. It should have its own tabset. Documentation for properties is great but one could also imagine documentation pages for items. My idea would be to develop some simple template in the style of notebooks. One example would be what I have done for one first names : Notebook for first name Ada(sorry it's in French). The idea is to have a set of questions and corresponding SPARQL queries.
  • Who would benefit : Readers and beginners. It would be easier to understand how properties and items are related to each other.
  • Proposer : PAC2 (talk) 05:25, 17 November 2020 (UTC)[reply]

Discussion

  • I don't feel qualified to speak to the specific solution, but I very much agree that making Wikidata more beginner-friendly should be a priority. {{u|Sdkb}}talk 03:27, 19 November 2020 (UTC)[reply]
  • We also agree there's quite a learning curve to Wikidata! However the Wishlist Survey is a means to ask for technical changes and improvements, while this seems to be about documentation. For this reason I'm going to archive this proposal. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 04:11, 2 December 2020 (UTC)[reply]
@MusikAnimal: my proposition was unclear. The idea was to create documentation pages for items wikidata:Q5/Documentation and create a tabset in the page menu between item and talk pages. So it's somehow a technical change. PAC2 (talk) 07:51, 9 December 2020 (UTC)[reply]

User rights to control entire section of Wikipedia

 N Requires community consensus

русский: Создание флага, который позволит человеку управлять всем разделом википедии

  • Problem:
  • Who would benefit:
  • Proposed solution: I suggest introducing the "language section agent" flag. That is, a person who will have all the rights in a certain section of Wikipedia. In my opinion, this person should be alone, as there will be less chaos and disagreements. In this case, applicants for this flag must be elected by the participants.
русский: Я предлагаю ввести флаг "агента языкового раздела" . То есть человека, который будет иметь все права в определённом разделе википедии. По моему мнению этот человек должен быть один, так как так будет меньше бардака и разногласий. При этом претенденты на данный флаг обязательно должны избираться участниками.

Discussion

  • This would require widespread consensus from the community before doing any technical work. For this reason, I'm going to archive this proposal, but thank you for participating in the survey! MusikAnimal (WMF) (talk) 00:45, 22 November 2020 (UTC)[reply]
    русский Это потребует широкого согласия сообщества перед выполнением какой-либо технической работы. По этой причине я собираюсь заархивировать это предложение, но спасибо за участие в опросе! MusikAnimal (WMF) (talk) 00:45, 22 November 2020 (UTC)[reply]

Dark theme on web version

 N Declined in a previous survey

  • Problem: No dark theme
  • Who would benefit: Everyone
  • Proposed solution: Dark theme on web version would be good for people like me who reads at night.
  • More comments:
  • Phabricator tickets:
  • Proposer: Tercose 03:44, 17 November 2020 (UTC)[reply]

Discussion

Seconded. Keepcalmandchill (talk) 04:29, 17 November 2020 (UTC)[reply]

Bot for automatic archiving discussion

 N Out of scope

  • Problem: We need to archive old discussion manually. Many wikis (especially big wikis) has their own bot. But most wikis doesn't have a Bot (one of main reason they don't have any technical person who can run a bot)
  • Who would benefit: All
  • Proposed solution: Create a global bot (similar to en:User:lowercase sigmabot III)
  • More comments:
  • Phabricator tickets:
  • Proposer: আফতাবুজ্জামান (talk) 20:14, 24 November 2020 (UTC)[reply]

Discussion

Create WikiVoyage mobile app

 N Outside the scope of Community Tech

  • Problem: Using a mobile browser is a clunky experience while traveling.
  • Who would benefit: WikiVoyage users.
  • Proposed solution: A mobile app with an improved experience over mobile browser with ability to save pages for offline access while traveling.
  • More comments: Adding ability to sign in and check off places you have visited would be useful as well.
  • Phabricator tickets:
  • Proposer: Aventuristo (talk) 21:24, 18 November 2020 (UTC)[reply]

Discussion

  1. I think this will be useful for those who love to travel and explore.--आर्या जोशी (talk) 06:57, 21 November 2020 (UTC)[reply]

GlobalRecentChanges

  Withdrawn by proposer

  • Problem: The users cannot see all recent changes from all Wikimedia projects.
  • Who would benefit: The users who want to patrol on all Wikimedia projects.
  • Proposed solution: Add Special:GlobalRecentChanges, a page in which there are displayed all recent changes from all Wikimedia projects.
  • More comments: I don't know if this is technically possible.
  • Phabricator tickets:
  • Proposer: --NGC 54 (talk / contribs) 12:35, 25 November 2020 (UTC)[reply]

Discussion

  • @NGC 54: I doubt we could build a Special:GlobalRecentChanges that works just like Special:RecentChanges, with a dedicated database table, etc., but there are some existing external solutions like toolforge:event-streams that can be used for monitoring activity across all wikis. We could certainly improve these tools. Would that satisfy the wish? MusikAnimal (WMF) (talk) 16:27, 25 November 2020 (UTC)[reply]
  • @NGC 54: I also wonder if you have considered the sheer scale of 'everything on every wiki'... It would be immensely overwhelming for any person to look at that, with all the different languages, multiple scripts like latin, hebrew, korean, japanese etc all mixed together and also different directional alignment... It doesn't seem to me like anything that anyone would ever want to look at unless heavily filtered towards a specific subset. —TheDJ (talkcontribs) 22:31, 25 November 2020 (UTC)[reply]

Allow page creators to block other editors to the page

 N Proposes a social/policy change, needs consensus

  • Problem: Certain times, some Wikipedia users misuse the edit option and write negative things on the Wikipedia page created for a celebrity or famous person. It'll be also very okay if Wiki can ban a user or give an option to ban a user if he/she writes any hateful speech on a wiki page.
  • Who would benefit: Those celebrity personalities who recently spoke on a controversial topic or are hated by some Wiki users.
  • Proposed solution: The edit option should be valid but the creator of the wiki page should be able to block the editor of the page.
  • More comments:
  • Phabricator tickets:
  • Proposer: Pratishtha Karkee (talk) 06:26, 18 November 2020 (UTC)[reply]

Discussion

Two-factor authentication (2FA) for all users

Deutsch: Zwei-Faktor-Authentifizierung (2FA)

 N Declined in a previous survey

  • Problem: As far as I know, two-factor authentication is currently still in the field test for certain user groups. It would be desirable if the development could be pushed forward so that this function could be rolled out globally for all users and wikis. Many thanks
Deutsch: Soweit mir bekannt ist, befindet sich die Zwei-Faktor-Authentifizierung derzeit noch im Feldtest für bestimmte Benutzergruppen. Es wäre wünschenswert, wenn die Entwicklung voran getrieben werden könnte, so das diese Funktion global für alle Benutzer und Wikis ausgerollt werden könnte. Vielen Dank

Discussion

Dark Mode (2)

 N Declined in a previous survey

  • Problem:
  • Leuten die ehr im dunkeln erbeiten oder einfach den Darkmode bevorzugen:
  • Darkmode programmieren (css):
  • Weitere Kommentare:
  • Phabricator-Tickets:
  • Antragsteller: MR776 (talk) 14:48, 20 November 2020 (UTC)[reply]

Diskussion

  • This was the #2 wish in the 2019 survey. We investigated and even began work, and as much as we wanted to finish it we unfortunately had to stop due to some technical challenges and conflicts with the Desktop Improvements project. You can learn more by reading our status report. This is not to say dark mode won't happen some day; I think it definitely will, but I'm afraid it won't be from Community Tech. As such I'm going to decline this proposal. Thanks for participating in the survey, MusikAnimal (WMF) (talk) 00:50, 22 November 2020 (UTC)[reply]
    Deutsch: Dies war der Wunsch der #2 Wunsch in der Umfrage 2019. Wir haben nachgeforscht und sogar mit der Arbeit begonnen, und so sehr wir sie auch beenden wollten, mussten wir leider aufgrund einiger technischer Herausforderungen und Konflikte mit dem Projekt Desktop Improvements aufhören. Weitere Informationen finden Sie in unserem Statusbericht. Dies bedeutet nicht, dass der dunkle Modus eines Tages nicht mehr auftreten wird. Ich denke, das wird es definitiv, aber ich fürchte, es wird nicht von Community Tech sein. Als solches werde ich diesen Vorschlag ablehnen. Vielen Dank für Ihre Teilnahme an der Umfrage. MusikAnimal (WMF) (talk) 00:50, 22 November 2020 (UTC)[reply]

Watchlisting category would show pages added/deleted to the category

 N Withdrawn by proposer; proposes an existing feature

  • Problem: Currently, monitoring categories is not an easy task. Putting a category in your watchlist only shows changes to the category page but does not show if any pages are added or removed from said category. That creates issues for maintaining well defined categories (e.g. that no random person is categorized as an office holder) or controversial categories (e.g. sexual orientation categories).
  • Who would benefit: All category maintainers on all projects
  • Proposed solution: If a category is in your watchlist, then any edits that place or remove pages from that category would show up on your watchlist. To be clear, not looking for a feature that would display all edits to all pages in the category (that's the function of "related changes" tool), just edits that place/remove pages from the category.
  • More comments:
  • Phabricator tickets:
  • Proposer: Renata3 (talk) 02:28, 17 November 2020 (UTC)[reply]

Discussion

Doesn't this already work? * Pppery * it has begun 03:00, 17 November 2020 (UTC)[reply]

It certainly should. @Renata3: In your watchlist filters there should be a "Category changes" option under the "Type of change" heading. Is not that working for you? You can also save this to your default watchlist settings, either using the save button in the watchlist interface or by ensuring "Hide categorization of pages" is unchecked at Special:Preferences#mw-prefsection-watchlist. MusikAnimal (WMF) (talk) 03:19, 17 November 2020 (UTC)[reply]
Haha, bloody hell, it does work. Nevermind then. Please close/withdraw this. Renata3 (talk) 03:34, 17 November 2020 (UTC)[reply]
Glad it's working! I suppose it's easy to miss because it's not in the default filters. Per your request I will archive this proposal. Best, MusikAnimal (WMF) (talk) 03:44, 17 November 2020 (UTC)[reply]

The Special:ContentTranslation sometimes a bug occurs

  • Problem: When I prepare an article in Special:ContentTranslation (I don't know what happens), I hope to save it automatically; and when opening the draft again, it shows the previous version of the saved one.
  • Who would benefit: When I prepare an article on Special:ContentTranslation, I don't know what happens or if it happens to several users, that when I hope to save; and open the draft again, it shows the previous version of salvo
  • Proposed solution: The gadget needs to be reconfigured in the automatic saving part, forcing the user to wait (Clearly, the user will be able to refuse the save at that time) to completely save the draft of the translated article.
  • More comments: I don't know if that could be my mistake; plus the solution could be useful for gadget, in my opinion.
  • Phabricator tickets:
  • Proposer: Juan90264 (talk) 04:33, 17 November 2020 (UTC)[reply]

Discussion

@Matěj Suchánek: I will create a task in Phabricator, to discuss this "bug". I appreciate the answer! But, what do I do with this discussion? Juan90264 (talk) 19:49, 17 November 2020 (UTC)[reply]
Looks like this became phab:T268070 (though that one needs clarification by following mw:How to report a bug). --AKlapper (WMF) (talk) 11:05, 18 November 2020 (UTC)[reply]
I think you don't have to do anything. It will definitely get proper care by the survey organizers at some point. --Matěj Suchánek (talk) 11:07, 18 November 2020 (UTC)[reply]