Wikimedia Meta-Wiki

Pesquisa de desejos comunitários/Atualizações

< Community Wishlist Survey
This page is a translated version of the page Community Wishlist Survey/Updates and the translation is 26% complete.
Other languages:

July 1, 2024: The Community Wishlist is re-opening Jul 15, 2024. Here’s what to expect, and how to prepare.

The Community Wishlist helps communities surface technical and user experience problems and opportunities, so that the Wikimedia Foundation and communities can prioritize and solve these issues together.

Like in years past, contributors can surface problems and opportunities by submitting “Wishes” year-round. The Foundation will identify patterns between wishes and propose “Focus Areas” of wishes that share a collective problem, and contributors are encouraged to comment and vote on Focus Areas to highlight the areas in need of prioritization. Then, the Foundation, affiliates, and volunteer developers can adopt Focus Areas and collaborate with contributors to solve these problems. Read more.

April 24, 2024: Edit Recovery updates

Edit Recovery is now available as an opt-in feature on all wikis. Earlier in February, we deployed the feature to French, English and Arabic Wikipedia for testing and bug fixes. Read more from the linked project page.

April 4, 2024: Potential modifications coming to the Community Wishlist Survey

In January, Community Tech shared some early decisions about changes coming to the Community Wishlist Survey, and soon after, we invited you to participate in ongoing conversations (please join if you haven't yet) about what a new Wishlist survey should look like. Our latest update covers potential modifications coming to the Wishlist. Please read about these changes.

March 1, 2024: Multiblocks design updates

Over the last few weeks we’ve been designing the user experience and user interface while talking to some admins about Multiblocks. We have some design decisions we want to implement which we have shared with screenshots.

January 4, 2024: Shaping the Future of the Community Wishlist Survey

Community Tech has made some preliminary decisions about the future of the Community Wishlist Survey.

In summary, we would like to develop a new, continuous intake system for community technical requests that improves prioritization, resourcing, and communication around wishes. Until the new system is established, the Community Tech team will prioritize work from the recently audited backlog of wishes rather than run the survey in February 2024. We are also looking to involve more volunteer developers in the wishlist process, beginning with the first-ever community Wishathon in March 2024.

Please read the announcement in detail either on the Diff blog or MetaWiki, and give your feedback.

October 26, 2023: Edit-Recovery is now available for testing in Beta

Hello community, we have some updates. Edit-Recovery wish (formerly known as Auto-save feature) is now available on Beta Cluster, and you are invited to test it.

Start editing any page on any Beta site, for example simple.wikipedia.beta.wmflabs.org, but don't publish your change. Wait 5 seconds and close the tab. Reopen the tab. Your edit should be recovered!

We are working to make the feature more visible with an element like a toast notification when restoring edit data, with the option of discarding the recovered data.

Questions and feedback are welcome.

October 17, 2023: An Update on Multiblocks Wish

We have selected Multiblocks the #14 wish in the Community Wishlist Survey 2023. The objective of the wish was to introduce layering blocks (a.k.a multiblocks). We have created a project page to share information about our approach. Please visit and give feedback.

September 25, 2023: It's Time for Wishathon!

The quarterly online hackathon known as Wishathon, organized by Community Tech to help fulfil more wishes from The Community Wishlist Survey, starts from Monday, 25 September 2023, to Friday, 29 September 2023.

Wishathon engages other Wikimedia Foundation staff to help fulfill more wishes, and also foster cross-team and cross-departmental collaboration.

August 8, 2023: Wish Updates

Hello everyone, there have been a few changes since our last major update in April 2023.

Displaying categories on mobile

We hoped to implement Display the categories on the mobile site for everyone – after completing the Better Diffs wish. Unfortunately, our key partner, the Web team, will not tackle this wish now. The importance of categories to readers must be researched further to prioritize this wish instead of other pending wishes. But wish fulfilment is often on a rolling basis, so your feedback is welcome. In the meantime, we are working on the Auto-save feature, the #8 wish in the Community Wishlist Survey 2023, which has been renamed to the Edit-Recovery Feature to reflect more accurately what the feature is.

Who Wrote That

Secondly, we have responded to the “Extend ‘Who Wrote That?’ tool to more wikis” and currently, Who Wrote That? (WWT) is now available on 8 more Wikipedias – French, Italian, Hungarian, Japanese, Indonesian, Portuguese, Dutch, and Polish. This brings the total number of wikis with WWT up from five to 13.

June 22, 2023: Next-steps for Auto-save feature

The CommTech team is reviewing any investigations, discussions, patches that have happened around the Auto-save feature wish to determine what is next.

Please read about the project, and help answer some questions including how long we need to save the data for the auto-save functionality and what we should store in the database to be able to make autosave functionality work.

June 22, 2023: IPA transition to Language Team

Community Tech will hand over the IPA project to the Language Team this June. This decision is due to the Language team's expertise in localization, and their focus to create a suite of open language-supporting services such as the MinT machine translation service among other things.

April 27, 2023: Continuing on 2022 and starting the 2023 Wishlist

Dear Community Wishlist Survey Participants,

We would like to thank you for your participation in the 2023 Community Wishlist Survey. The survey is a crucial element in helping us prioritize the development of new features and improvements to make Wikimedia projects better for everyone.

Starting work on 2023

We are pleased to announce that the Community Tech team has identified the "Display the categories on the mobile site for everyone" wish as the priority for the team to work on in the coming months after we complete the work on Better Diffs for paragraph splits. This was also Wish #18 on the 2022 Wishlist. This decision was based on the wish's technical and design feasibility, as well as its potential impact in improving the user experience of the mobile site for all users.

We understand the importance of this feature for the community, and we are excited to work on it. We will keep you updated on the progress we make and will provide more information on the timeline for implementation as soon as possible. In addition, we’ve begun investigating how to Extend “Who Wrote That?” tool to more wikis, the seventh #7 most popular wish from 2023 and hope to make great progress on that work in the coming months. We anticipate launching Who Wrote That? tool to French Wikipedia in the coming days, with several other languages to follow in the coming weeks.

Dark Mode

We want to provide an update on the "Dark Mode" wish that was voted for in the survey. We are excited to inform you that the Web team has taken on this wish and plans to work diligently on its development. However, due to technical constraints and design feasibility, the Web team will be releasing the first version of the "Dark Mode" feature in Beta. We understand the importance of accessibility and inclusivity, and we are committed to ensuring that this feature meets the needs of all users. Additionally, there are many templates that need to be adjusted, and volunteers need to be alerted to modify before the "Dark Mode" feature can be fully released. The Web team will work on documenting these issues, and we appreciate your patience in this process. We encourage you to subscribe to the Web team's newsletter to follow the updates about this project.

I would also like to take a moment to thank the volunteers who took the time to collaborate with me in good faith during my tenure here and share that I am departing the Wikimedia Foundation and this team. Thank you to those of you who took the time to participate in proposals, problem solving with us, and to those of you who volunteered and tackled technical pieces of granting wishes – I will carry that inspiration with me for the rest of my career.

In my absence, a Product Trio will absorb my responsibilities so you can expect to reach out to the Engineering Manager KSiebert (WMF), Tech Lead DMaza (WMF), and Principal designer JSengupta-WMF as a united Product Trio after my departure in early May. You can expect to communicate with the team in the same way as before, the Talk pages for Projects, Updates, and the Team are the best way to reach the team. We collectively would also like to thank you once again for your participation in the Community Wishlist Survey. Your input helps us prioritize and improve Wikimedia projects, and we look forward to your continued engagement in the future.

Sincerely,

NRodriguez (WMF) and the rest of The Community Tech Team

March 13, 2023: Better diff handling of paragraph splits update

The team has continued work on this wish on both the engineering and design side and we wanted to share the updates with you.

Impacto do desejo

Thank you to all of you who took the time to engage with us and provide feedback on the talk page. We read through all of the feedback and did an aggregate analysis on the points made. We then combined your feedback on those proposed designs, as well as unmoderated user research, and we've finalized the proposed designs to go into engineering for the improvements regarding the wish changes.

Please see the designs in this update which include:

  • Switching between diff modes via dropdown
  • Improving the accessibility of inline diffs with legends and tooltips for desktop
  • Improving the display of a change that introduced a new line or paragraph
  • Improving the display of a change that deleted an existing line or paragraph

In addition, a demo of the changes for the underlying comparison engine has been created.

Before you try out the demo to give us feedback, please note:

  • It's a work in progress, our QA engineers are currently using a list of comprehensive diffs to make sure the changes are consistent with the current version of the two-column diff experience or an improvement on the UI.
  • The demo page does NOT include all final UI changes but can give testers a good sense of how the completed two-column diff experience will end up looking.
  • To use the demo, paste the same text into the two boxes and modify the text in the right box. The diff under it will show what changed.

We'd love to hear your feedback on our talk page!

Next Steps

  • Accessibility of Design Colors: Our designer is working closely with our Design Systems team to determine the accessibility of the designs. We anticipate having to change the shade of them to a slight degree to make it more accessible but the colors will remain similar to the blue and yellow currently displayed on two-column and inline diffs.
  • Release plan: We are working out a release plan and a timeline of next steps and will be including this in our next project updates! Releasing changes to the underlying engine on the diff follows a different process than traditional releases in Mediawiki software so we will be sure to update you with steps and details next time.

We also want to include big thank you in this update to a non-Community Tech staff member, Tim Starling, who graciously stepped up to help us with the underlying changes in the C++ engine of wikidiff2. We are always happy to receive support fulfilling wishes from other members at the Foundation that have the expertise necessary to fulfill a wish even if they are not in the Community Tech team.

We're looking forward to hearing from all of you!

Open Questions from first update: We want to hear from you!

  • Are you interested in conducing user research on the new proposed interface to diff paragraph splits? If so, will you please post that you're interested in the Talk Page?
  • What other pain points manifest themselves when you view the diff?
  • How might we address the root pain points that address the confusion around paragraph splits?
  • How does the use of color indicate which content is added, removed, or stayed the same?

March 7, 2023: Community Wishlist Survey 2023 results published

The Community Wishlist Survey 2023 edition has been concluded. We have published the results of the survey and will provide an update on what is next in April 2023.

December 20, 2022: Wishathon Update

This year, the Community Tech started a tradition of hosting an internal WMF Wishathon. During this Wishathon, our team cancels meetings for an entire week and spends the entirety of our time working on "smaller" wishes outside of our regular "larger" wish workload. For example, the Better diff for paragraph split wish is a complex large wish that requires heavy planning with regards to design research, technical architecture as well as plans for quality assurance and dependencies with the Performance team. These wishes usually take months for us to grant. The Wishathon inspires us to grant wishes that are more straight forward and require less cross-team dependencies and planning. While these may not be the most popular wishes, we still believe they are impactful and heavily desired by the participants who voted on them.

This past December, we extended an invite of participation to other engineers, designers, and managers in different teams to join us for a week long Wishathon and help us make progress on the work required to grant these smaller wishes. Thanks to the additional participation from engineers on other teams, we were able to finish four wishes and refactor an important piece of code. Please note that in the spirit of moving quickly and building wishes people need, we did not conduct the full cycle of research and communication outreach that we usually complete on larger wishes. You can read about the wishes we completed last week, their impact, and their scheduled releases below.

Wish: Autosuggest linking Wikidata item after creating an article

This wish received 92 support votes and ranked as the #12 most popular wish in the list of the 2022 wishes.

Problem: Someone creates an article in Language A Wikipedia, but they do not know there is already the same article in Language B Wikipedia (often a smaller language version), so no Wikidata linkage is made. Proposer has seen many cases between Chinese Wikipedia (zh) and Cantonese Wikipedia (yue).

Work was completed and will be available as a gadget the week of January 16, 2023.

  • More Wikipedia (and other project) pages linked to corresponding Wikidata items
  • Greater awareness of Wikidata for wiki contributors
  • Better maintenance of links between Wikipedia languages, and other Wikidata benefits

Wish: Enable negation for tag filters

Este desejo recebeu 41 votos de apoio e foi classificado como o 27º desejo mais popular na lista dos desejos de 2022.

Problema: Ao visualizar feeds como Especial:Contribuições ou Especial:Mudanças recentes podemos filtrar por tags, mas não pela negação de tags.

O trabalho foi concluído e sairá no conjunto de implantações que ocorrerão na semana de 3 de janeiro de 2023.

  • Desejo original
  • Tarefas e patches relevantes
    • ✅ Closed T119 072: Allow Tag negation on Special:Contribution
    • ✅ Closed T174 349: Allow Tag negation on Recent Changes
    • ✅ Merged Patch 866 814: UX for Tag negation on Special:Contribution
    • ✅ Merged Patch 867 726: fixed testing for forms to work better with hide-if (to allow next)
    • ✅ Merged Patch 866 817: UX for Tag negation on Special:Log (out of scope, but easy)
    • ✅ Merged Patch 867 255: Expose Tag negation in API and feed (to allow next)
    • ✅ Merged patch 867 731: Prevent tagfilter param from being set to 'all' (to allow next)
    • ✅ Merged Patch 867 224: UX for Tag negation on Recent Changes / Watchlist
  • Status:
    • 866 814 already in prod (i.e. on Special:Contributions)
    • 6 patches merged, two tasks closed, one wish fulfilled
  • Próximos passos:
    • Deploy to prod for Recent Changes and Special:Log with next train
  • 🏆 Special thanks to Team Members: Roan Kattouw, Denny Vrandecic, James Forrester, Moriel Schottlender

Honorable mention to Matěj Suchánek, a volunteer who laid the groundwork for this by writing this patch in 2020.

Impacto do desejo

Users will be able to filter out edits based on a tag on Recent Changes, Watchlist, Special:Contributions, and Special:Log.

Wish: Enable Thanks Button by default in Watchlists and Recent Changes

This wish received 62 support votes and ranked as the #33 most popular wish in the list of the 2022 wishes.

Problem: The Thanks button is only available on individual Page Histories, which very few people interact with on a regular basis -- especially more experienced editors. The number of newbies looking at individual history pages, is miniscule.

  • Desejo original
  • Tarefas e patches relevantes
  • 🏆 Special thanks to Team Members: Jon Robson
  • Status: The work has been merged and is available for testing in Beta, and will be deployed to users with the first train of 2023 which is scheduled for the week of Jan 3.

Impact of wish

Users will now be able to thank other users from inside Watchlists and Recent Changes pages.

This wish received 18 support votes and ranked as the #162 most popular wish in the list of the 2022 wishes.

Problem: The tag on the change line currently looks like this: 

   14:33 John Callahan's Quads!‎ (diff | hist) .. (−12) .. Rng0286 (talk | contribs) (lorem ipsum) (Tags: Visual edit, Mobile web edit)

The tag name is either a link to a help page or just plain text. It is not easy to find edits with the same tag.

Impact of wish

Users will now be able to click on the tag name to find edits with the same tags within change lines.

Refactoring code from the Page Triage codebase for easier collaboration

Impact of work

Modernizing the codebase to help make bug fixing and feature development easier

What's Next?

In addition to the wishes granted above, we were able to make some progress on a handful of other wishes. Community Tech will be assessing which wishes we can finish based on the progress left on them. We are excited to continue this Wishathon tradition and welcome your feedback in the talk page of this update! Thank you for participating in the Wishlist, we hope to see you in the upcoming annual survey opening January 23, 2023.

December 16, 2022: Realtime Preview is coming out of beta

The Realtime Preview for Wikitext is coming out of beta as an enabled feature for every user of the 2010 Wikitext editor in the week of January 9, 2023. It will be available to use via the toolbar in the 2010 Wikitext editor. The feature was the 4th most popular wish of the Community Wishlist Survey 2021.

December 5, 2022: The 2023 Community Wishlist Survey will happen in January

Do you have an idea for a tool or platform improvement for Wikimedia projects? This announcement is for you!

The Community Wishlist Survey (CWS) 2023, which allows contributors to propose and vote for tools and improvements, starts next month on Monday, 23 January 2023, at 18:00 UTC and will continue annually.

We are inviting you to share your ideas for technical improvements to our tools and platforms. Long experience in editing or technical skills is not required. If you have ever used our software and thought of an idea to improve it, this is the place to come share those ideas!

The dates for the phases of the survey will be as follows:

  • Phase 1: Submit, discuss, and revise proposals: Monday, 23 January 2023, to Monday, 6 February 2023
  • Phase 2: WMF/Community Tech reviews and organises proposals: Monday, 30 January 2023 to Friday, 10 February 2023
  • Phase 3: Vote on proposals: Friday, 10 February 2023 to Friday, 24 February 2023
  • Phase 4: Results posted: Tuesday, 28 February 2023

If you want to start writing out your ideas ahead of the Survey, you can start thinking about your proposals and draft them in the CWS sandbox.

We are grateful to all who participated last year. See you in January 2023!

December 1, 2022: Better diffs usability testing

We have been working on different design alternatives for Better diff handling for paragraph splits, the #1 wish in the Community Wishlist Survey 2022! We have invited the community to sign up for usability tests and give feedback.

May 3, 2022: Real Time Preview launching to partner projects

We have launched a version of the Realtime preview feature to Polish Wikipedia. Its community has agreed to partner with us and give us feedback on how to improve it before we launch to the rest of the users. Please find our complete Release Plan. Leia mais

This feature touches one of the most used editors (Wikitext 2010) across wiki projects. We've thus decided to roll it out as a Beta Feature before we release the feature to everyone. This will allow us to collect feedback and make improvements before we release to everyone.

We are partnering with users early on to understand behavior on the new tool and make improvements. Depending on the user’s connection, we are aiming to observe and evaluate patterns regarding the automatic and manual reloads of the preview pane, as follows:

  • Automatic reload: Debounce time. When the preview pane is automatically reloading, is our debounce time sufficient to provide a fluid experience?
  • Automatic reload: Discoverability of the manual reload button. When the preview pane is automatically reloading, is the manual reload button that appears while hovering over the preview pane easy to find?

and/or

  • Manual reload: Discoverability/Display time of the manual reload status bar. When the preview pane is NOT reloading automatically, the user will see a status bar inviting them to manually reload. Is the discoverability of the bar sufficient? Is the status bar obstructive to the users’ workflows?

We will aim to observe both of these scenarios for users with stable high-speed internet connections. In both cases, we will be performing the test on two pages: one short article without images (for faster reload time) and another one with a large content and multimedia assets (for slower reload time).

Aside from our main investigation, we will also be observing the following during our screen-sharing sessions with users:

  • Discoverability of the overall feature: although users will be notified of the existence of the realtime preview feature, and the potential relationship between the latter and the "Show preview" feature.
  • User screen sizes- This data could be helpful to understand how useful the Realtime Preview is for folks with a smaller screen. Does this make their experience too crowded?
  • Usage of syntax highlighting/Code Mirror
  • Understanding that both panes do not have a synced scrolling behavior.

If you would like to give us any feedback on any of the open questions above, please reach out to us in the talk page as we are eager to hear about the usability of this new feature. Thanks for building with us!

February 15, 2022: CWS 2022 results

A pesquisa de desejos comunitários 2022 chegou ao fim! Agradecemos a todos os que participaram na edição desse ano, e exprimimos nossa sincera gratidão àqueles que fizeram contribuições excepcionais à pesquisa. Não poderíamos ter feito tudo isso sem vocês!

Quer saber o que acontece agora? Saiba mais sobre nosso processo de priorização e confira a classificação de propostas priorizadas para esse ano. Leia mais

8 de novembro de 2021: Avisar quando linkar a páginas de desambiguação

We have an update about the wish. We have finished user tests. Leia mais

Hello everyone,

Many thanks for your great support and feedback on the proposed user experience and designs for this wish. This update is regarding the usability testing, which was conducted in parallel with community members on the talk page, as well as the first “Talk to Us hours” video call last September. Thanks again for your valuable inputs!

The goal of this round of usability tests was to determine if our proposed designs were successful in warning users about the potential risks of adding a link to disambiguated page in the 2010 wikitext editor without inhibiting users from continuing to edit. We conducted the test on usertesting.com with 5 editors total.

Here are the insights we gathered from the tests:

  • 2/3 of users successfully noticed the new notification warning them about the disambiguation link they added. Two users were not able to see the notifications due to complications with the testing interface and instructions.
  • All users who saw the notification found it helpful and easy to understand. When users noticed the disambiguation notification and understood its purpose, most of them stated that it was useful without being disruptive to their edit flow.

Acknowledgments: This test was conducted on beta-wiki with a limited content pages. Before we could push some recent user experience and engineering improvements for this wish, including the new link selector widget for the Wikitext editor. We are hoping that these changes will mitigate some of the difficulties encountered by the users during this usability test.

Not all of these editors from this panel are experienced users. Although this wish is intended to be helpful for every user – we assume that less experienced editors will tend to use the VisualEditor over the wikitext editor, thus making this new feature less relevant for them.

We are grateful for your feedback on this talk page and the Talk to Us for our team to get a better understanding of your needs as experienced contributors. Thanks so much for your feedback on the talk page!

2 de novembro de 2021: Visualização em tempo real para Wikitexto

Thank you for your comments on the talk page, as well as the latest "Talk to Us" video call. Also, we have conducted usability testing. We are sharing the most important findings. Leia mais

Hello everyone,

Many thanks for your support and great feedback on the proposed designs. Thank you for comments on the talk page, as well as the latest "Talk to Us" video call. We have learned more about how experienced users edit.

Also, we have conducted usability testing on the usertesting.com platform. 5 editors took part. Below you will find some of the findings and insights:

  • Half of the users found the new "Preview" button in the toolbar. One of the reasons for this could be behavioral patterns developed over the existing "Show preview" button in the footer of the editor box. We are designing a low-friction pulsating dot with a guide popup. We hope this will make it easier to notice the new feature.
  • All users found the existing "show preview" button.
  • All users understood the difference between both buttons. One could be used while editing (offering a quick glimpse at the output). The other could be more helpful for proofreading before publishing the changes.
  • One user reported that it might always be easy to understand the relationship between the Wikitext input and the preview output. To mitigate this, we are exploring ways to highlight the text in both panes and align the scrolling or editing behavior.

Acknowledgments:

  • Not all of these editors are experienced users. Although this wish is intended to be helpful for every user – we assume that less experienced editors will tend to use the Visual Editor over the wikitext editor. This will make the new feature less relevant for them.
  • We are also working on improving the scaling of both panes. We want to allow for optimal support to both small and ultra-wide displays alike.

Again, thanks so much for your feedback!

19 de outubro de 2021: Recusando o desejo do robô bibliográfico

Título do desejo: Robô bibliográfico

Tíquete do Phabricator para investigação

Rank do desejo: #14

Resumo do motivo: Escopo de trabalho muito grande, votos insuficientes.

Decidimos recusar este projeto. Fizemos isso após uma consideração cuidadosa e várias rodadas de feedback dentro da equipe e conversas com outras equipes da WMF e afiliados.

Justificativa: Primeiro, os engenheiros e designers investigaram o escopo do trabalho definido na declaração do problema do desejo (T243150). Determinamos que o trabalho sozinho excede em muito nossa estimativa inicial dele.

Este desejo teve uma pontuação muito alta em nosso processo de priorização porque, à primeira vista, parecia simples duplicar o comportamento de Citoide dentro do Wikidata. Presumimos que envolvia uma baixa complexidade do ponto de vista técnico e de design, porque poderíamos reutilizar o código e os designs. No entanto, as citações no Wikidata devem ser vinculadas como referências a outros objetos no banco de dados. Isso aumenta significativamente a complexidade.

Este desejo não marcou os 10 desejos mais populares. Ele veio na posição #14. Estávamos errados sobre a estimativa inicial. Na verdade, o trabalho para este desejo foi realizado pelo Wikidata/Wikimedia Alemã por vários meses. A solução final era muito complexa para ser concluída, dados os recursos disponíveis no momento. Isso levaria vários meses para a equipe da comunidade tecnológica ter concluído e há outros desejos mais populares que trabalharemos.

4 de setembro de 2021: Visualização em tempo real para Wikitexto

Progredimos trabalhando na ferramenta de pré-visualização em tempo real para Wikitexto. Temos duas perguntas sobre o design. Convidamos você a responder na página de discussão do projeto. Leia mais

Obrigado pelo seu comentário

Olá a todos, estamos de volta com uma atualização dos designs propostos para este desejo. Obrigado por todos os seus comentários na página de discussão. Ouvimos o que você disse e sintetizamos o feedback da seguinte maneira:

  • O botão para visualizar o resultado do wikitexto deve ser mais intuitivo, a pessoa que clica nele deve saber o que ele faz.
  • O botão para visualizar o texto deve estar na barra de ferramentas.

Em seguida, fizemos uma segunda tentativa de criar o seguinte conjunto de designs. Estamos propondo que um novo botão apareça na barra de ferramentas:

 

Estamos propondo que, quando o usuário visualizar o conteúdo, o botão de visualização permanecerá "azul" para indicar que o estado de visualização está ativado:

 

O botão de visualização voltaria a ficar preto se os usuários clicarem e a visualização desapareceria.

Horizontal vs Vertical

Observe que esses projetos propostos são ilustrativos. Incluímos apenas uma versão vertical porque estamos investigando se a capacidade de ter uma tela ampla ainda será uma opção, dado o trabalho planejado nas melhorias na área de trabalho, que limitará as páginas em 960px de largura, tornando assim muito confuso a visualização.

Perguntas abertas: Queremos ouvir você!

  • O novo posicionamento do botão parece mais intuitivo para os trabalhos na barra de ferramentas?
  • No layout proposto atual há espaço suficiente para visualizar o wikitexto e o resultado final?

Muito obrigado por seus comentários na página de discussão!

27 de agosto de 2021: Visualização em tempo real para Wikitexto

Estamos dando os primeiros passos na ferramenta de pré-visualização em tempo real para Wikitexto. Temos dúvidas sobre o design. Convidamos você a responder na página de discussão do projeto. Leia mais

Designs propostos

Layout horizontal no computador

Um novo botão aparecerá. Isso dá aos editores a opção de visualizar o texto na lateral em tempo real:

 

Observação: a caixa rosa acima é apenas para chamar a atenção para o botão, ela não aparecerá para os usuários.

Os editores poderão clicar no botão destacado acima. Se eles fizerem isso, o layout a seguir permitirá que eles visualizem o resultado em um contêiner fixo rolável:

 

Layout vertical no computador

O novo elemento de interface do usuário a seguir aparecerá quando um usuário tiver uma tela vertical:

 

Observação: a caixa rosa acima é apenas para chamar a atenção para o botão, ela não aparecerá para os usuários.

Os editores poderão clicar no botão destacado acima. Se eles fizerem isso, o layout a seguir permitirá que eles visualizem o resultado em um contêiner fixo rolável:

 

Os engenheiros começaram a trabalhar nessas mudanças. Estamos introduzindo as mudanças dentro do núcleo do MediaWiki. Adoraríamos ouvir sua opinião sobre nossos designs propostos. Gostaríamos especialmente de receber feedback sobre:

  • Tornando a colocação de cópias e botões intuitiva
  • A sensação geral dos designs propostos

Estamos ansiosos para ouvir sua opinião sobre nossos designs propostos e quaisquer outras considerações!

Perguntas abertas: Queremos ouvir você!

As soluções acima são propostas e em estágios iniciais. Adoraríamos ouvir seus comentários na página de discussão. Sua visão pode nos ajudar a entender outras abordagens, riscos e soluções.

Estas são as nossas perguntas para você:

  • Como você acha que isso influenciará a maneira como você edita?
  • O ícone no botão de expansão prepara os editores para entender o que ele faz? É perturbador?

20 de agosto de 2021: A Pesquisa de desejos comunitários 2022 acontecerá em janeiro

Olá pessoal,

Esperamos que todos vocês estejam o mais bem e seguros possível durante estes tempos difíceis! Gostaríamos de compartilhar algumas novidades sobre uma mudança na Pesquisa de desejos comunitários 2022. Gostaríamos de ouvir sua opinião também.

Estaremos realizando a Pesquisa de desejos comunitários de 2022 em janeiro de 2022. Precisamos de mais tempo para trabalhar nos desejos de 2021. Também precisamos de tempo para preparar algumas alterações na lista de desejos de 2022. Enquanto isso, você pode usar uma página de testes dedicada para deixar as primeiras ideias para as solicitações de 2022.

A proposta e a realização do desejo acontecerão no mesmo ano

No passado, a equipe de tecnologia da comunidade realizava a Pesquisa de lista de desejos da comunidade para o ano seguinte, em novembro do ano anterior. Por exemplo, executamos a pesquisa de desejos para 2021 em novembro de 2020. Isso funcionou bem alguns anos atrás. Naquela época, começávamos a trabalhar na pesquisa de desejos logo após a publicação do resultado da votação.

No entanto, em 2021, houve um atraso entre a votação e o momento em que poderíamos começar a trabalhar nos novos desejos. Até julho de 2021, estávamos trabalhando nos desejos da pesquisa de desejos para 2020.

Esperamos que ter a pesquisa de desejos 2022 em janeiro de 2022 seja mais intuitiva. Isso também nos dará tempo para atender a mais desejos da pesquisa de desejos de 2021.

Incentivar uma participação mais ampla de comunidades historicamente excluídas

Estamos pensando em como tornar a pesquisa de desejos mais fácil de participar. Queremos apoiar mais traduções e incentivar as comunidades com poucos recursos a serem mais ativas. Gostaríamos de ter algum tempo para fazer essas alterações.

Um novo espaço para conversar conosco sobre prioridades e desejos ainda não atendidos

Teremos ficado 365 dias sem uma pesquisa de desejos. Nós encorajamos você a nos abordar. Esperamos ouvir de você na página de discussão, mas também esperamos vê-lo em nossas reuniões bimestrais do Fale Conosco! Eles serão hospedados em dois horários diferentes, amigáveis para fusos horários ao redor do globo.

Começaremos nossa primeira reunião 15 de setembro às 23:00 UTC (20:00 BRT). Mais detalhes sobre a agenda e formato em breve!

Brainstorm e rascunho de propostas antes da fase de proposta

Se você tiver ideias iniciais para desejos, pode usar a nova página de testes da Pesquisa de desejos comunitários. Dessa forma, você não se esquecerá deles antes de janeiro de 2022. Você poderá voltar e refinar suas ideias. Lembre-se de que as edições na página de testes não contam como desejos!

Feedback

  • O que devemos fazer para melhorar as páginas de desejos?
  • Como você gostaria de usar nossa nova página de testes?
  • Quais, se houver, riscos você prevê em nossa decisão de alterar a data da Pesquisa de desejos 2022?
  • O que ajudará mais pessoas a participar da Pesquisa de desejos 2022?

Responda na página de discussão (em qualquer idioma de sua preferência) ou em nossas reuniões Fale Conosco.

18 de agosto de 2021: Avisar quando linkar a páginas de desambiguação

We have moved forward with the design. We would like you to answer our questions. Leia mais

Progress with the design

Hello everyone, and thanks to those of you who have been active on our talk page and tested the proof of concept script for displaying a warning. We have moved forward with designing for the last two requirements in our proposed solutions and wanted to share them with you so that we could hear your input!

As an Editor using the link toolbar to search for knowledge to reference in my article, I can:

  • See a warning before publishing if I have introduced a disambiguation link in my article
  • Visibly differentiate disambiguation links as a different type of content than articles that come up on my suggestions

For the first solution above, we are proposing displaying this yellow box warning when wikitext users add a link:

 

For the second solution above, we are proposing changing the copy to better describe what a disambiguation page means in the wikitext link button and in the visual editor link pop-up:

 

 

Open questions

We'd love to hear your thoughts on our proposed designs. We'd especially love feedback on:

  • Making the copy accessible and making it easier to glean what a disambiguation page is
  • Making sure the warning for wikitext editors feels preventative without coming off as discouraging-- editors should still be able to publish even if they have introduced faulty links

We're looking forward to hearing your thoughts on our proposed designs!

5 de agosto de 2021: (Des)deletar página de discussão associada

We have completed our first investigation. You can track this inside this ticket on Phabricator. The bulk of the work here will be around security and performance considerations. We estimate tackling this work within the coming months. Leia mais

2 de agosto de 2021: Avisar quando linkar a páginas de desambiguação

We have completed our first part of the wish. As a result, we will release a new change in a few days. Thank you for all the comments you have given. Leia mais

The first part is about the following improvement:

As an Editor using the link toolbar to search for knowledge to reference in my article, I can see specific articles as the first search results.

This effects the link search function in VisualEditor and the 2017 wikitext editor.

The change should go live this week. In the meantime, if you would like to preview the changes, you can try it out on the beta cluster. For instance, when adding a link and you type out the term "New York", New York City and New York (state) appear above the disambiguation page New York in the search results.

We are looking forward to hearing your feedback!

After this change is released, we will be monitoring the numbers inside The Daily Disambig to see if it has any impact on the number of unwanted dab links being added (thanks for pointing us in the direction of this page).

23 de julho de 2021: Avisar quando linkar a páginas de desambiguação

We have begun design planning on this wish. Our designer, NAyoub is working on setting up some user tests where we ask new editors to link from the Jupiter article to the Mars article and see if they fall for the disambiguated page since it's the first result. We will take notes and write up next steps based on the results. Our engineers are also investigating the feasibility of moving search results for disambiguated terms to the bottom of the results. Leia mais

16 de julho de 2021: Copiar e colar diffs

We are making initial steps on the Copy paste diffs tool. We have questions about its design. We invite you to answer on the project talk page. Leia mais

Engineering investigation

We have begun the engineering investigation for this work inside this Phabricator ticket. We are optimistic in the solutions we've found to fix this problem.

Video demonstrating copy and paste interactions for diff selection

Open questions

  • In which contexts do users usually copy and paste from diffs?
  • What syntax manifests itself as intrusive? Is there any syntax that would be desirable to keep in the clipboard?
  • What feedback do you have on our proposed solution?

15 de julho de 2021: Relatório de status

There have been and will be changes to our team. We have made decisions what will be the sequence of wishes we will be working on. We would like you to learn more about our methodology. There are reasons why the voting is not the only criterion. Please tell us what you think about it. Leia mais

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey/Updates/pt-br&oldid=27646628"