Jump to content

社群願望清單調查/更新

Add links
From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Community Wishlist Survey/Updates and the translation is 33% complete.
Other languages:

2024年7月1日：社群願望清單將於2024年7月15日重新開放。該期待什麼、該準備什麼

社区愿望清单帮助社区发现技术和用户体验问题和机会，以便维基媒体基金会和社区能够优先考虑并共同解决这些问题。

与过去几年一样，贡献者可以通过全年提交“愿望”来提出问题和机会。基金会将确定愿望之间的模式，并提出共同问题的愿望“重点领域”，鼓励贡献者对重点领域发表评论和投票，以突出需要优先处理的领域。然后，基金会、附属机构和志愿者开发人员可以采用重点领域，并与贡献者合作解决这些问题。阅读更多。

2024年4月24日：编辑恢复更新

编辑恢复现在可作为“所有wiki上的选择加入功能”使用。2月初，我们将该功能部署到法语、英语和阿拉伯语维基百科进行测试和错误修复。从链接的项目页面阅读更多信息。

2024年4月4日：社区愿望清单调查的潜在修改

2024年1月，Community Tech分享了关于社区愿望清单调查变化的一些早期决定，不久之后，我们邀请您参与正在进行的对话（如果您还没有加入，请加入），了解新的愿望清单调查应该是什么样子。我们的最新更新涵盖了愿望清单的潜在修改。请阅读这些变化。

2024年3月1日：多块设计更新

在过去的几周里，我们一直在设计用户体验和用户界面，同时与一些管理员讨论Multiblocks。我们有一些设计决策想要实现，我们已经用截图分享了这些决策。

2024年1月4日：塑造社区愿望清单调查的未来意向

Community Tech对社区愿望清单调查的未来做出了一些初步决定。

总结来说，我们希望针对社区技术要求开发一个新的持续接收系统，以改善愿望的优先级、资源分配和沟通。在新系统建立之前，社区技术团队将优先近期的愿望审计积压 ，而不是在 2024 年 2 月进行调查。我们也希望让更多的志愿开发人员参与愿望清单流程，从 2024 年 3 月举办的首届社区 Wishathon 开始。

请在 Diff 博客 或 MetaWiki 上详细阅读公告，以及 提供您的反馈。

2023年10月26日：编辑恢复现在可用于Beta测试

你好，社区，我们有一些更新。编辑恢复愿望（以前称为自动保存功能）现在可以在Beta Cluster上使用，我们邀请您对其进行测试。

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.

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.

Impact of wish

  • 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

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

Problem: When view feeds such as Special:Contributions or Special:RecentChanges we can currently filter by tags, but not by the negation of tags.

Work was completed and will be out in the set of deployments occurring the week of January 3, 2023.

  • Original Wish
  • Relevant Tickets and Patches
    • ✅ 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
  • 状态：
    • 866,814 already in prod (i.e. on Special:Contributions)
    • 6 patches merged, two tasks closed, one wish fulfilled
  • Next steps:
    • 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.

Impact of wish

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.

  • Original Wish
  • Relevant Tickets and Patches
  • 🏆 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!

调查各阶段的日期如下：

  • 第1阶段：提交、讨论和修改提案--2023年1月23日至2023年2月6日
  • 第二阶段：WMF/社区技术审查和组织提案--2023年1月30日至2023年2月10日
  • 第三阶段：WMF/社区技术审查和组织提案--2023年1月30日至2023年2月10日
  • 第四阶段：发布结果：2023年2月28日

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.

2022年5月3日：在夥伴項目中發佈實時預覽

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. 瞭解更多

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!

2022年2月15日：2022年CWS結果

The Community Wishlist Survey 2022 is over! We would like to thank everyone who participated in this year's edition and express our special gratitude to those who made outstanding contributions to the survey below the results. We could not have done it without all of you!

Curious about what happens next? Learn about our prioritization process and check out the ranking of prioritized proposals for this year. 瞭解更多

2021年11月8日：链接至消歧义页面时请给予警告

We have an update about the wish. We have finished user tests. 瞭解更多

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!

2021年11月2日：维基文本的实时预览

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. 瞭解更多 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!

2021年10月19日：拒絕「文獻機器人」的願望

願望標題:文獻機器人

用於研究的Phabricator票據

願望排名：第14名

原因簡述：工作範圍太大、票數不夠。

經過仔細考慮和與維基媒體基金會的其他團隊及夥伴進行多輪意見反饋後，我們決定拒絕這個企劃。

根本原因：首先，我們的工程師及設計師探討了這個願望（T243150）在問題陳述中所述涉及的工作範圍，並推定這個企劃的工作量本身已經遠遠超越我們原來的估算。

這個願望在我們的優先化程序得到很高的分數，因為，眨眼來看，複製維基數據的Citoid行為看似非常簡單直接。我們本假定這個企劃在技術和設計方面涉及低程度的複雜性，因為我們應該可以重複使用以前的設計及程式碼。不過，要達到這個願望，維基數據中的引文必須以參考資料的形式連結到數據庫中的其他方塊。這個大大增加了項目的複雜性。

這個願望並沒有獲選為十大最熱門願望；它排名僅第14，而我們進行了錯誤的初步估算。事實上，這個企劃在維基數據/維基媒體德國花費了多個月的時間，而在當時有限的資源之下，最終的方案過於複雜。這樣會花費群體技術團隊多個月的時間完成，而我們還有另外更加熱門的願望需要達成。

2021年9月4日：Wikitext的实时预览

We have made progress working on the Real Time Preview for Wikitext tool. We have two questions about its design. We invite you to answer on the project talk page. 瞭解更多

Thank you for your feedback

Hello all, we are back with an update on the proposed designs for this wish. Thanks for all of your comments on the talk page. We heard what you said and synthesized the feedback as follows:

  • The button to preview the wikitext output should be more intuitive, the person clicking it should know what it does.
  • The button to preview the text should be in the toolbar.

We then took a second try at creating the following set of designs. We are proposing a new button appears in the toolbar:

We are proposing than when user previews the content, the preview button label remains "blue" to indicate that the preview state is on, and activated:

The preview button would turn back to black if users toggle it off and the preview would disappear.

Horizontal vs Vertical

Please note that these proposed designs are illustrative. We only included a vertical version because we are currently investigating if the ability to have a wide screen will still be an option given the planned and upcoming work on Web desktop improvements which would limit the page to 960px in width, making it too cluttered to have a horizontal view.

Open Questions: We want to hear from you!

  • Does the new button placement seem more intuitive to the workflows in the toolbar?
  • Does the current proposed layout feel like there is enough space to view both the wikitext and the output?

Thanks so much for your continued feedback on the talk page!

2021年8月27日：Wikitext的实时预览

We are making initial steps on the Real Time Preview for Wikitext tool. We have questions about its design. We invite you to answer on the project talk page. 瞭解更多

Proposed Designs

Horizontal Desktop Layout

A new button will appear. This gives editors the option to preview the text on the side in real-time:

Note: The pink box above is just to draw attention to the button, it will not actually appear to users.

Editors will be able to click on the button highlighted above. If they do that, the following layout would allow them to preview the output in a scrollable fixed container:

Vertical Desktop Layout

The following new user interface element will appear when a user has a vertical desktop screen:

Note: The pink box above is just to draw attention to the button, it will not actually appear to users.

Editors will be able to click on the button highlighted above. If they do that, the following layout would allow them to preview the output in a scrollable fixed container:

The engineers have begun work on these changes. We are introducing the changes inside of MediaWiki core. We'd love to hear your thoughts on our proposed designs. We'd especially love feedback on:

  • Making the copy and button placements intuitive
  • The overall feel of the proposed designs

We're looking forward to hearing your thoughts on our proposed designs and any other considerations!

Open Questions: We want to hear from you!

The solutions above are proposed and in early stages. We'd love to hear your feedback on the talk page. Your insight can help us understand other approaches, risks, and solutions.

These are our questions to you:

  • How do you think this will influence the way you edit?
  • Does the icon on the expand button prepare the editors to understand what it does? Is it distrupting?

2021年8月20日: 2022社群願望清單調查將於一月進行

大家好，

我們希望您在這段艱困時期都安全無虞！我們帶來了數則關於2022社群願望清單調查的新訊息。我們非常期待聽到您的寶貴意見。

2022年社群願望清單調查將於2022年1月舉行。我們需要有更多時間來執行2021年的願望清單，亦需要時間來應對2022年願望清單的改動。在這段期間，您依然可以運用沙盒來發表您對於維基媒體技術發展的願景。

提議與願望實現將於同一年發生

過去，社群技術團隊在每年的11月進行下一年的社群願望清單調查。例如，我們在2020年11月進行了2021年的願望清單。這在過去的幾年運作良好。在那段時間，我們曾經在投票結果公佈後不久就開始有關願望清單的工作。

然而，我們在2021年的投票和開始著手實現新願望的時間之間出現了延遲。直到2021年7月，我們都在努力實現2020的願望清單中的願望。

我們希望於2022年1月建立2022年的願望清單，並讓這更加直觀。這也將使我們有時間實現2021年的願望清單中的更多願望。

鼓勵以往被排斥的社群可以更廣泛的參與

我們正在考慮如何讓願望清單更容易參與。我們希望支持更多的翻譯，並鼓勵資源不足的社群更加活躍。我們希望有一些時間來進行這些更改。

一個與我們討論優先事項和尚未實現的願望的新空間

我們將度過沒有願望清單的365 天。我們鼓勵您和我們聯繫。我們希望在對話頁面中收到您的來信，同時我們希望在我們每兩個月一次的「與我們交談」會議上見到您！這些將在對全球時區友好的兩個不同時間舉辦。

我們將在「協調世界時間9月15日23:00」開始我們的第一次會議。有關議程和格式的更多詳細信息即將推出！

在提案階段之前進行頭腦風暴和起草提案

如果您對願望有任何的早期想法，您可以使用 新的社群願望清單調查沙盒。這樣，您就不會在2022年1月之前忘記這些願望。您將能夠回來繼續，完善您的想法。請記住，沙盒中的編輯不算作願望！

反饋

  • 我們應該如何改進願望清單頁面？
  • 您希望如何使用我們新的沙盒？
  • 在我們決定更改2022年願望清單的日期時，您預見到哪些風險（如有）？
  • 什麼將幫助更多人參與2022年的願望清單？

請於對話頁面（用您喜歡的任何語言）或在我們的「與我們交談」會議上回答。

2021年8月18日：链接至消歧义页面时请给予警告

We have moved forward with the design. We would like you to answer our questions. 瞭解更多

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!

2021年8月5日：刪除/還原相關討論頁面

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. 瞭解更多

2021年8月2日：链接至消歧义页面时请给予警告

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. 瞭解更多

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).

2021年7月23日：链接至消歧义页面时请给予警告

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. 瞭解更多

2021年7月16日：复制粘贴差异

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. 瞭解更多

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?

2021年7月15日：状态报告

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. 瞭解更多

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey/Updates/zh&oldid=27646640"