قائمة أمنيات المجتمع/تحديثات
قائمة أمنيات المجتمع |
|
October 5, 2026: Call for working group volunteers
Hi, I’m Trizek and I'm a senior Movement Communications Specialist working on this new wishlist process. As Sonja mentioned in previous updates, we’ve been working on thinking through the logistics behind the working group that will help us with triaging wishes and finalizing our wish plan. We’ve created a working group sub-page, where you can find details on the goal of the group, roles and expectations, as well as norms we’ll follow, and most importantly: how to sign up. We’d like to invite you to come check it out to see if you might want to participate. There is no formal selection process, but instead this is an open invitation for collaborative work with relevant stakeholders.
Trizek_(WMF) (talk) 13:07, 5 October 2026 (UTC)
September 30, 2026: Latest updates for the Community Wishlist
Hello everyone, here are some updates about ongoing wishes over the past month by WMF teams, affiliates and volunteers:
The work we did in the last month
- Customizable number of 'Because You Read' tiles in the Wikipedia app (W386): Mobile Apps team released to 50% of iOS users as of September.
- Discovery feed in Wikipedia app similar to social media apps (W506): Mobile Apps team released to 50% of iOS users as of September.
What we currently have in progress
- Add Wikipedia Mobile App’s Reading Lists to the Website (W102): Save articles to read later - on all wikis by end of September. Customized collections within saved items - aiming for end of October.
- Special pages should have language links (W385): This has been prioritized for an upcoming sprint and work should begin in October.
What we are scoping next
- Contributor Growth team replaced Apply AI to article improvement suggestions on the homepage (W100) with Suggested tasks based on contributions history (user interests) also for experienced editors (W316), aiming to release new Home experience to pilot wikis in November.
- Reader Experience team is preparing for an experiment to Show recommended articles on Wikipedia Main page on desktop & mobile web, not just in app (W505) in October. It will run on mobile web and desktop to see whether providing reading recommendations based on "interests" selected by a user will improve reader retention.
- Editing team is preparing for an experiment for the Highlight edit button (W496) in October. It will invite logged-in readers and editors to edit by showing them signals about articles that can be improved, starting with the number of edit suggestions available within the articles they are reading.
- The Wishlist UX and Reader Growth teams are finalizing the scope and initial mocks for the updated A proper audio player (W317) - these will be tracked in the newly filed Phabricator ticket phab:T428062.
Some statistics
This is a snapshot taken on September 29, 2026. Use the filters on the Wishes page to dive deeper into examples or see live metrics as they are regularly updated.
We need your feedback
To wrap up the wish for a set of tools for image editing directly in Wikimedia Commons (W222), we propose surfacing relevant tools into a new toolbar section as they are distributed across different locations. This will provide better visibility to all Commons users on what has been developed, and then track engagement to see where to invest time for deeper integration. Please follow the discussion on Phabricator for the latest.
As always, if you have questions or feedback about it, please let us know in the Community Wishlist’s talk page. We are eager to hear from you!
September 29, 2026: Update on Lead Program Manager role
Hi everyone! I’m writing to let you know that we filled the Lead Program Manager role for the Wishlist. As you know we were looking specifically for someone with a strong connection to the community as well as a technical background, and I'm happy to share that Britta Gustafson (Dreamyshade) has decided to join the team with a start date of October 20. Britta will be responsible for leading the Community Wishlist program, so she'll lead us through the wish submission, triage, and voting stages moving forward. She'll work with the teams assigned to prioritized wishes to ensure we stay on track for delivery, while also engaging with any community members interested in wishes. You’ll continue to hear from me throughout this wishlist cycle as Britta will be onboarding still, but I’m sure she’ll also post something here once she’s settled in to introduce herself in more detail.
Here are a few words from Britta: “I’m extraordinarily excited to start working for the community as the Wishlist program manager. Being a Wikipedia editor influenced me to go into a whole career in community management and product management, including work with external developer communities and leading engineering teams to deliver products, and I’m delighted to bring this home in service of the people of Wikimedia projects. I will do my best to be the staff member that I would want to see in this role - to listen, make space, figure things out, communicate, and help make things happen. Soon!!”
As a reminder, here are a couple of key dates for you to keep in mind:
- Wish submission will be open until Nov 8, 2026 with Central Notice banners running in the weeks leading up to that date
- The working group will go through the triage process between Nov 9 and 20
- To honor the end of year break, voting will happen Jan 8 - 24, 2027
- You will be invited to comment on our wish plan in early to mid February 2027
- We’ll start implementing wishes as early as March 2027
You will hear from us again with details on the working group and how to sign up within the next week or so. SPerry-WMF (talk) 16:42, 29 September 2026 (UTC)
September 29, 2026: Pages updates in progress
Following the discussions mentioned below, we are beginning the process of updating the various documentation pages. This will take a few days; in the meantime, some pages may not be consistent with others.
Trizek_(WMF) (talk) 13:27, 29 September 2026 (UTC)
September 14, 2026: Updated Community Wishlist Process 2027/2028
Thank you to everyone who engaged in the discussion around my proposal from August 26. I’ve processed your feedback and made changes accordingly. Note that I wasn’t able to implement all of it for this cycle, mostly for logistical reasons, but this is merely meant to be a first step and we will continue to improve this process with you all before we run through the next cycle. We plan to use this updated version for the Wishlist 2027, and I look forward to hearing from you all during the submission and voting periods.
SPerry-WMF (talk) 23:08, 14 September 2026 (UTC)
August 26, 2026: Wishlist 2027, invitation to share feedback
Hi, I’m Sonja and I lead some of the teams at the Foundation who will be responsible for picking up wish work under the new wishlist process. If you've been following along, you'll have seen updates from me here before. For those just now catching up, I'll provide a quick summary: As you may know, the Community Wishlist started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically.
In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver.
I would like to get community input specifically on these three stages of the Wishlist process:
- The triage stage, meaning how wishes are fleshed out, organized and filtered prior to voting
- We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together
- The voting stage, including who may vote and how votes are structured
- The post-vote stage, including how to bring equity into what work is prioritized
- One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and sister projects, so that top-voted wishes from smaller projects also get attention
This message is an abstract of the full proposed process. As you read the proposed ideas, please speak up (in any language) about whether you think this will work well or if there are ways to make it stronger. This consultation is open for two weeks.
For this year’s cycle, we plan to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together.
SPerry-WMF (talk) 21:14, 26 August 2026 (UTC)
August 25, 2026: Latest updates for the Community Wishlist
Hello everyone!
We’ll post separately about upcoming changes to the new wishlist process, but in the meantime, we have some updates about ongoing wishes over the past month by WMF teams, affiliates and volunteers.
The work we did in the last month
The beginner-friendly ChartWizard (W414) has been deployed to Commons for testing. Some more work continues including bug fixing, testing and monitoring feedback by MusikAnimal and Reader Growth. Feedback is welcome on the wish talk page.
The Language and Product Localization (LPL) team has finished deploying allowing users to pin/unpin specific languages in interwiki links (W264). In the language picker on wiki, click the three-dot menu in the lower right-hand corner to access language settings, where there is a new option for pinning your preferred languages. Improving the discoverability of this feature is an open task and note that you must be logged in to access these preferences.
The Wikidata team has been working on giving editors an easy and seamless experience when contributing to Wikidata on mobile (W389). Soon this will be default on wikidata.org, and it is already a Beta feature that can be enabled on Wikidata itself.
What we currently have in progress
The top-voted wish to support full colour 3D models on Wikimedia projects (W326) continues to fully fix rendering of 3D images with support from This Dot, who have been doing Wishlist work on a contractual basis since November 2025, along with collaboration with WMF teams and volunteers.
Guidance on categories on upload (W526) and chunked uploading to Special:Upload (W46) have patches pending some remaining guidance. These wishes are being worked on by This Dot, along with support from Sohom Data, Cormac Parle and TheDJ.
Aude is working on deploying the ability to add a date range filter for MediaSearch (W221) to CirrusSearch, which has had one more patch merged and two more pending reviews.
An intern from Outreachy is implementing the automatic verification of duplicate references in the Visual Editor (W278), along with continued support from Wikimedia Brasil, Wikimedia Deutschland, and the Editing team. The patch for the VisualEditor duplicate reference validation is currently under review on Gerrit. More details are in this Diff post.
What we are scoping next
The Language and Product Localization (LPL) team has taken over the wish for special pages and language links (W385), which was previously planned by CommTech. They have also prioritized fixing persistent markup leakage from Content Translation tool (550), which has seen fast growth in support from the community working on translations.
The Editing team is working on a forthcoming project page for increasing suggestion discoverability, which is relevant for the highlight edit button (496) wish.
Our WMF UX Design team is currently scoping and discussing how to improve license compliance and attribution of embedded maps (W419), which was previously prioritized because of the request to invest more in Commons by the Unsupported Tools Working Group.
Some statistics
This is a snapshot taken on August 24, 2026. Use the filters on the Wishes page to dive deeper into examples or see live metrics as they are regularly updated.
We need your feedback
There has been work done by This Dot and community members such as affiliates to provide more image editing tools (W222) and we are currently discussing with UX how to make these more visible - you may join the discussion in Phabricator to see an overview and add suggestions. Note that a similar wish (W298) has recently been marked as a duplicate.
We are seeking feedback on a proof of concept user script created by Bawolff to see why a file is somewhere underneath a specific category (W393) that may satisfy the underlying wish need without merging it into the Deepcat gadget.
Note that this is not an exhaustive list of wishes in progress. For others, we recommend following updates on their respective project pages or Phabricator tickets.
As always, if you have questions or feedback about it, please let us know in the Community Wishlist’s talk page. We are eager to hear from you!
July 31, 2026: Update on wishlist next steps and program management support
Hi, I want to share an update with you about our Wishlist proposal and about who will support the Wishlist.
Last week at Wikimania, I hosted a session to gather ideas for how wishes should be prioritized in the future. The idea behind this session was that we want to create a prioritization framework with the community, so that the wishes we prioritize reflect the community’s needs and expectations. To make that happen, vote count and other community criteria (to ensure smaller communities also have a chance to be heard) should be the biggest factors in determining prioritization. I’ve already posted the ideas we’ve gathered during my session, and as a next step I will follow up later in August with a proposal for what the process could look like to get feedback from the broader community.
In addition, we have heard feedback that deep involvement with contributors and technical experience are critical for the program manager for the new Community Wishlist. Based on that feedback and through discussion with the current program manager, MikeZ-WMF, we are designing a new program manager role for the Wishlist to be more focused on community engagement, relationship building, and ownership of delivery and execution of wishes. You'll see the job posting go live in the next few days. Going forward, Mike is going to support the Reader Engagement goal. Our commitment to Wishlist resourcing remains, and this change is to ensure we have the right skills to support the Wishlist going forward.
If you have any questions, please feel free to reach out to me, or directly to the teams working on the current wishes. SPerry-WMF (talk) 14:57, 31 July 2026 (UTC)
July 9, 2026: Update on near-term wish work
Hi, I'm Sonja and I work with Marshall on building out the future process for the wishlist. A couple weeks ago, Marshall shared some suggestions we have for the long-term, which is something we're planning to solidify over the next couple of months. This update is mainly about the near-term, but just to reiterate some of the main things for the long-term: we heard your concerns that the current voting and prioritization process didn't meet community expectations, and that ideally a future wishlist would complement our annual plans with dedicated wishlist work that can sit outside the Foundation's strategic goals. We are committed to shaping the new process around that. One big point to highlight here is that prioritization will rely mainly on votes moving forward, and we want to figure out with volunteers how to best use the votes to prioritize wishes. We still need to resolve some open questions, for example how we might ensure that smaller communities and projects don't get overlooked. We're planning to hold a wishlist vote later in 2026, to prioritize wishes starting in 2027.
Regarding the near-term: until we have new voted-on wishes in place in January, we will continue working on the wishes from the existing process. To be clear: we know the existing process did not capture community needs the way previous years of the wishlist had. But many useful wishes are currently underway, nominated and voted on by volunteers. This is an approach that closes out the old process, knowing that we will stand up a new and more community-aligned process over the next couple of months. Below is a list of all the work that in one way or another impacts currently open wishes and that is planned either by the Foundation, volunteers, or affiliates between now and December 2026 (so that's why there are a lot of wishes in the list). We're sharing this table as a one-time snapshot to create clarity for the next few months and plan to share a closeout report before we start picking up new wishes in January. In the meantime, you'll be seeing our regular monthly updates in the usual format.
Here is what the timeline will look like:
- Now through December
- Work on previously prioritized wishes will be continued, either through larger related projects or dedicated wish work (more details in table below).
- October / November
- Wish submission and voting period takes place. We are ironing out the details for this and plan to co-create this process with the community.
- January
- The Foundation starts picking up explicit wish work per new prioritization process, based on a prioritization framework built with community. Exact details are still to be determined in collaboration with the community.
We need your ideas for creating a process that meets the needs of the community, so please participate in the discussion on the talk page. You can post in your own language if you prefer – my colleagues will help translate so every input is considered. I'm especially interested in hearing about how we can set up the process to surface wishes that can make a big difference for experienced editors.
| Wishes overview | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
July 6, 2026: Services and Ownership Update
Hi, I’m Sonja and I lead the Contributor product teams at the Foundation. I’m currently helping with closing out the current wishlist process and defining what the future of the wishlist should look like. You’ll soon hear more from me to follow up on Marshall's last update on long-term proposals and next steps. In the meantime, I have an update on maintenance assignments for the 27 tools and production services previously maintained by CommTech – we know that many of these are critical tools for editors, and so it is important that there are teams ready to address issues when they occur. Suman and other engineering leaders worked on this list. While filing Phabricator tasks and other modes of contacting WMF will work to raise issues, contacting the product managers or engineering managers on these teams is also an option. Note that since our last post we've added a few more tools to this list per volunteer feedback.
- Popular Pages Bot – Data Platform Engineering
- CopyPatrol – Technical Partnerships team (to manage Turnitin contract); Moderator Tools
- Pageviews Analysis – Data Platform Engineering
- XTools – Moderator Tools
- Extension:CodeMirror – Editing
- Extension:LoginNotify – Product Safety and Integrity
- Database Reports – Data Platform Engineering
- Extension:PageAssessments – Data Platform Engineering
- SVG Translate – MediaWiki Engineering
- Extension:TemplateWizard – Editing (front end); Content Transform Team (back end)
- Commons deletion notification bot – Moderator Tools
- Event Metrics – Connection
- Wikisource Export – MediaWiki Engineering
- Wikimedia OCR – MediaWiki Engineering
- Google-api-proxy – Tools Infrastructure
- Extension:WikiSource – MediaWiki Engineering
- Who Wrote That? – Moderator Tools
- WikiWho – Moderator Tools
- Edit Recovery – Editing
- Template recall and discovery – Editing (front end); Content Transform Team (back end)
- Extension:CommunityRequests – Technical Program Management (team link coming soon)
- Watchlist Labels – Moderator Tools
- Extension:GlobalPreferences – MediaWiki Engineering
- Realtime Preview – Editing
- AutosuggestSiteLink – MediaWiki Engineering
- Extension:ArticleCreationWorkflow – Language and Product Localization
- Community Tech Bot – MediaWiki Engineering
- Extension:UrlShortener – MediaWiki Engineering
- Multiblocks – Product Safety and Integrity, as part of the blocks system
- Watchlist Expiry – Moderator Tools
As we shared in our June update, in April we introduced our approach to ensuring continuity of ownership for production services: every service we run in production will have an assigned team responsible for it. This is an important step for the Foundation. Our goal is to move away from individual ownership of tools and services, and instead establish clear team assignments. By assigning teams, we can create a more sustainable and reliable model for maintaining and supporting our production services.
In that vein, this “Maintainers” page is being updated to indicate some of what I listed above (though not all of the tools will be on the Maintainers page, as that page is meant for production software).
June 24, 2026: Latest updates for the Community Wishlist
Hello everyone,
Since our last monthly update on 13th May, substantial changes have been made to how the wishlist will work going forward, and there has been a large amount of community discussion. You can read those updates here and here, and we are asking for community input on how exactly the wishlist should operate in the future. Please join the discussion.
We’re proposing several changes to how we take in and prioritize wishes (such as a return to annual voting), but even as we discuss with communities how the wishlist will work in the future, existing wishes are in progress and continue to be completed by the various teams in the Product and Technology department, by affiliates, and by volunteers. So this is an update on those recently completed wishes, in-progress wishes, and upcoming ones.
The work we did in the last month
The Mobile Apps team has been working on more games (W514): “Which came first?” is now available on Android, and an iOS release will follow in July; “Did you know?” is on hold due to technical and linguistic constraints, though feedback is still welcome.
The Reader Growth team evaluated an experiment to Make 'Table of Contents' available in Wikipedia (Web) Mobile (W423). Results showed it lowered the retention rate for readers (primary success metric) by about 1.5% and shortened the amount of time they spent on wiki. As a result, the team will not implement the Table of Contents for readers on mobile web. Feedback is still welcome on the experiment talk page.
Make subreferencing work with inline refs and reflist (W309) is now done. The feature will be gradually deployed to all wikis starting June 2026 (deployment plan). Feedback can be shared with the WMDE Technical Wishes team on the project page.
Along with Sage (Wiki Ed), SuperGrey and Xinacod, MusikAnimal (WMF) is wrapping up adding new languages to “Who Wrote That” and to the P&E Dashboard (W503) with 56 languages total. Chinese, Japanese and Korean are taking additional time due to large XML dumps to import.
What we currently have in progress
The Wikidata team is working on giving editors an easy and seamless experience when contributing to Wikidata on mobile (W389). Editors can now enable a beta feature for mobile statement editing. The team is taking all the feedback into account as part of the mobile editing work, which will eventually also come to desktop.
The Moderator Tools team has continued the expansion of the Personal Dashboard (W313) to make it easier for editors to identify where their attention is needed. Users with more than 100+ edits (and no more than 500 edits on English Wikipedia) received a UI invite and personal tools menu link to view the page. Learn more about this on their project page.
Aude is working, with support from the Search and Wikidata teams plus Matěj Suchánek, on a patch to ensure to add a date range filter for MediaSearch (W221).
Make the Chart extension beginner-friendly (W414) will be owned by Reader Growth as MusikAnimal wraps up the implementation with their support. This week the realtime preview feature will be added to the JSON editor. The project page will be updated.
Three mobile app wishes related to discovery (W506), customization (W386), and personalization (W384) are informing the Mobile App team’s Explore Feed Refresh project, which is a large redesign to increase engagement through several smaller improvements and experiments. Phase 1 has recently had an Android beta rollout to 50% of users in production. iOS is being targeted for July. You can post feedback on the talk page.
The Language and Product Localization (LPL) team is working on allowing users to pin/unpin specific languages in interwiki links (W264). They aim to release it as part of the language selector UX improvements by the end of June.
The Unsupported Tools Working Group has prioritized Commons work such as uploads, including guidance on categories on upload (W526) and chunked uploading to Special:Upload (W46), which are being worked on by This Dot along with support from the group’s members Sohom Datta and Cormac Parle.
What we are scoping next
The Unsupported Tools Working Group has prioritized additional Commons wishes to be implemented by This Dot, who have been doing Wishlist work on a contractual basis since November 2025, along with collaboration with teams such as Reader Growth and Wishlist UX for an updated audio player (W317), while the latter team focuses on the related spoken Wikipedia (W304) wish. Moreover, we continue to scope tools for image editing directly in Wikimedia Commons (W222), while support for brightness, contrast, and saturation filters was made possible thanks to support from Bawolff.
The Editing team has started to scope ways to highlight the edit button (W496) for potential new editors who may not be aware that they can edit. An initial experiment is planned for next quarter (July through September). A project page with more details is forthcoming.
With support of Wikimedia Brasil, Wikimedia Deutschland, and the Editing team, an intern from Outreachy is planning the automatic verification of duplicate references in the Visual Editor (W278). More details are in this Diff post.
Wikimedia Deutschland’s Technical Wishes team has also started a project page to possibly scope improving VE references' automatic names and reuse (W17). Possible solutions are listed on the project page, where you can also join discussions on the respective talk page.
Some statistics
Here is a recent snapshot all current wishes followed by notes on diffs since our last update on 13th May:
The most notable shifts in numbers are “in progress” growing from 18 to 24. These wishes are actively being worked on as seen in patches and user-facing experiments and beta phases.
For wishes marked “Done” in the pie chart, we have heard that some of these should have been declined for existing functionality. A few months ago we added a new sub-status for “Decline” that covers this use case.
You can read more about status details in the FAQ.
We need your feedback
For adding the mobile app reading lists to desktop (W102), the Reader team has updated their project page with a timeline and experiment details – you can join the talk page discussions, and also follow how feedback will be incorporated in Phabricator.
As always, if you have questions or feedback about it, please let us know in the Community Wishlist’s talk page. We are eager to hear from you!
June 17, 2026: Wishlist program in the future
Hi everyone – I’m Marshall Miller; I’m a senior director of product working with the teams that build the user-facing parts of the wiki software, which will be doing much of the work of accomplishing wishes going forward. As I posted on the talk page last week, Sonja Perry, MikeZ and I are on point for working with communities on how the wishlist program will operate in the future.
Over the past few weeks, over 100 volunteers have spoken up about what they need from the wishlist and how they think it should function, and we committed that we’ll work with volunteers over three months to clarify those plans. We’ve heard that the wishlist is a vital way that the needs of experienced editors get voiced. We’ve heard about the importance of the annual cadence of voting to draw volunteers’ attention to the wishlist and to create a moment when the community considers priorities together. We’ve heard that it’s important to ensure that sufficient WMF resources will be dedicated to accomplishing wishes. We’ve heard that volunteers need clear points of contact to whom they can ask questions and bring up problems around wishlist work.
Sonja, Mike, and I have been discussing with some users with extended rights (thank you!) to make some proposals about how the wishlist program can meet those needs. The proposals listed below are meant to cover some of the large aspects of the wishlist, but don’t cover all the many smaller details (we will get to those!). Please let us know on the talk page what you think of these. I also list some open questions we want to hear from communities on.
I want to note that while the below points are about how the wishlist program might run in the future, we also need to share with communities how we’ll accomplish wishes in the nearer term, over the coming months. We’ll get into those details in another update.
Proposals for the future
- We’ll return to a widely-advertised annual wishlist vote to identify the wishes that are the highest priority for the communities.
- To make the voting as useful as possible, a working group coordinated by the wishlist program manager will categorize and de-dupe wishes, and ask clarifying questions to the wishers. The working group will have staff from the various WMF teams that will work on the wishes (e.g. someone from the Editing team, someone from the Moderator Tools team, etc.) We will also invite volunteers to join in this process to prepare for voting, and we want to figure out how that can work best.
- After wishes are voted on, WMF will take those vote counts and all the volunteer discussion into our annual planning process, so that we can prioritize them alongside the other non-wishlist work that we’re planning – making sure that highly-voted wishlist work gets resourced (and is not an afterthought). At that point, we’ll figure out which teams are well-positioned to work on which wishes, and build in time on team roadmaps to work on wishes. It’s important to note that, just as in the past, not all highly-voted wishes can be worked on – some wishes may be technically infeasible, or negatively affect certain users, or need to wait for the attention of a team that is focused on a different important priority.
- To make sure we’re dedicating sufficient resources toward wishes, we’ll look at past wishlist years and plan to accomplish similar amounts of wishlist work in upcoming years (with the knowledge that wishes vary in size).
- As part of sharing our annual plan with the communities in coming years, we’ll share which wishes will be worked on, by which teams, and roughly when in the year.
- We will make clear who the WMF contact points are for each wish that we’ll work on, so that volunteers can easily contact them with ideas and questions.
Open questions – we want to hear from you
- Sometimes there are multiple wishes that are related to each other, or especially large wishes. These might indicate some important area that requires major investment for editors. An example is the Page Curation and New Pages Feed improvements from the 2019 wishlist, which constituted substantial upgrades to that system. How might the wishlist help surface those major areas?
- In the past, the wishlist tried various approaches to make sure that wishes from sister projects and smaller languages were prioritized. How might we make sure that smaller projects and languages get attention?
- Although it is crucial to have a period of high visibility for soliciting wishes and voting, would it be good to still allow submitting wishes year-round, so that when people have ideas/needs, they can submit them instead of needing to remember to do so months later?
- Past wishlist years have used various systems for determining exactly which highly-voted wishes are prioritized, and have taken into account aspects like the size of the wish and how to serve smaller projects and languages. We’re still thinking about what would work best going forward and want to hear your thoughts.
We hope to hear from you on the talk page, and we’ll continue to share updates.
5 يونيو/حزيران 2026: تحديثات الملكية والخطوات التالية
مرحباً جميعاً، سومان مرة أخرى، وأنا نائب رئيس منتجات وتكنولوجيا في مؤسسة ويكيميديا. أنا أكتب لكِ لأشاركِ بعض التحديثات منذ الأسبوع الماضي
- ملكية الأدوات والخدمات: تساءل الكثيرون منكم عن ملكية الأدوات التي كانت تُديرها المجتمع التقنية. نحن على دراية بـ 27 أداة وخدمات الإنتاج التي كانت تُديرها المجتمع. تم إعداد هذه القائمة بمساعدة أعضاء فريق المجتمع التقنية السابقين، وهي تتوافق مع ما شاركه معنا أعضاء المجتمع. نعلم أن استمرارية ملكية الكود أمر بالغ الأهمية لضمان استمرار عمل الأدوات. في أبريل/نيسان، شاركنا المجتمع كيفية إدارة المؤسسة لاستمرارية ملكية الخدمات في بيئة الإنتاج - حيث سيتم تخصيص فريق لكل خدمة نُشغلها في بيئة الإنتاج. هذا الأمر قيد التنفيذ حاليًا. نحن بصدد تطبيق هذه العملية على خدمات الإنتاج التي كانت مملوكة سابقًا للمجتمع، مما يعني أننا سنُعيّن فرقًا جديدة لصيانتها ودعمها المستمر. أما بالنسبة للأدوات التي كانت مملوكة للمجتمع التقنية (والتي تختلف عن خدمات الإنتاج)، فنحن نعمل مع مهندسي المجتمع التقنية السابقين الذين تم نقلهم إلى فرق أخرى في قسم الإنتاج والتكنولوجيا لتحديد الفرق الأخرى التي ستتولى صيانة هذه الأدوات وملكيتها.
- ملكية رغبات المجتمع التقنية النشطة: كان فريق المجتمع التقنية يعمل على 9 رغبات عند إعادة الهيكلة: جعل أداة "من كتب هذا؟" تعمل بجميع اللغات؛ إضافة خيار "إخفاء القوالب" إلى الروابط هنا؛ تعديل المقدمة بدلاً من المقالة بأكملها؛ جعل إضافة المخطط سهلة الاستخدام للمبتدئين؛ دعم نماذج ثلاثية الأبعاد ملونة بالكامل في مشاريع ويكيميديا؛ السماح بفرز المناقشات في صفحات النقاش؛ يجب أن تحتوي الصفحات الخاصة على روابط لغوية؛ فتح صفحة ملف ويكيميديا كومنز مباشرة، وعمل تصنيفات قائمة المراقبة المتبقية. من بين هذه المشاريع التسعة، كان اثنان منها على وشك الاكتمال، وسيبقيان مع أعضاء فريق المجتمع التقنية السابقين الذين تم تكليفهم بهما، بالإضافة إلى مطورين متطوعين ("من كتب هذا؟" و"إخفاء القوالب"). أما المشاريع الأخرى، فقد تم تقسيمها ودمجها في خطط العمل الحالية لفريق التحرير وتجربة المستخدم، وفريق أدوات المشرف، وإدارة برنامج قائمة الأمنيات، والذين سيتعاونون مع المتطوعين عند الحاجة في أعمال التطوير.
- مجالات التركيز: كما أشارت سيلينا في تحديثها، لن يتم تطبيق مجالات التركيز بعد الآن، حيث أوضحت غالبية ملاحظات المجتمع أنها تجعل العملية أقل وضوحًا. سنقوم بتحديث وثائقنا لتعكس هذا التغيير في مجالات التركيز خلال الأسبوع القادم، وسنواصل تقديم التحديثات بناءً على ملاحظاتكم خلال الأسابيع المقبلة.
- فرز وتتبع الطلبات الواردة: خلال الأسبوع الماضي، واصلت فرق منتجات المؤسسة فرز الطلبات الواردة. وعلى مدار الأيام القليلة الماضية،
أعطى فريق PSI الأولوية لأدوات تحليل المشاعر، و[1] أعطى فريق هندسة موثوقية الموقع (SRE) الأولوية لـتفعيل بروتوكول Encrypted Client Hello (ECH) لمواقع ويكيميديا. وفيما يتعلق بالمتابعة، فقد أجرينا محادثات مع أعضاء المجتمع حول تحسين تتبع التقدم المحرز في الطلبات من خلال الفابريكيتور والتحديثات الشهرية على ويكي، مع الإشارة إلى المطورين المتطوعين وفرق المؤسسة وأي شخص آخر يساعد في دعم هذا العمل. يمكنك متابعة عملية الفرز والتتبع هذه، بما في ذلك الرغبات الفردية المقدمة، من خلال تحديثاتنا الشهرية وإحصائياتنا. - على المدى البعيد: على الرغم من أننا نتحدث عن بعض التحسينات الواضحة التي يجب إدخالها على قائمة الأمنيات مستقبلاً، إلا أن هناك العديد من الأفكار الأخرى التي طرحها المتطوعون والتي ينبغي علينا دراستها معًا. وكما ذكرت سيلينا في تحديثها السابق، هذا ما نرغب في مواصلة العمل عليه خلال الأشهر الثلاثة القادمة، وسنعمل على إيجاد طريقة لتنظيمه بشكل أفضل ودمج جميع الأفكار والمقترحات - لذا دعونا نستمر في الحوار.
منذ التحديث الأخير، انضم عضو واحد من فريق المجتمع التقنية إلى فريق هندسة ميدياويكي، حيث يركز على البنية التحتية للوسائط، بالإضافة إلى عضوين آخرين (عضو واحد وعضوان) من فريق أدوات المشرفين. تتمتع هذه الفرق الحالية، إلى جانب فرق أخرى، بوضع جيد لمواصلة العمل مع المجتمع لتلبية الاحتياجات المستقبلية المتعلقة بهندسة ميدياويكي وأدوات المشرفين.
References
- ↑ بعد مزيد من النقاش، ولأن لدينا بعض الأعمال المرتبطة ارتباطًا وثيقًا بهذا الطلب، ولكننا لا نعرف بعد ما إذا كنا سنتابع هذا الطلب تحديدًا، فإننا نعيده إلى "قيد المراجعة". للمزيد، راجع تعليقاتنا لصاحب الطلب، وصفحة المشروع ذات الصلة.
29 مايو/أيار 2026: تغييرات في عملية قائمة الأمنيات استجابةً للتعليقات؛ تحديث بشأن الموظفين
مرحباً جميعاً، أنا سيلينا ديكلمان، مسؤولة التكنولوجيا الرئيسية في مؤسسة ويكيميديا. لقد شاركتُ في صفحة النقاش وأتابع جميع المحادثات هنا وفي ويكيبيديا الإنجليزية، بالإضافة إلى المنتديات الأخرى، للتأكد من أنني أتلقى أكبر عدد ممكن من الآراء حول التغييرات التي أُعلن عنها في 20 مايو/آيار.
أودّ أن أشكر الجميع على ملاحظاتهم واقتراحاتهم لتحسين قائمة الأمنيات مستقبلاً. عند التفكير في مختلف جوانب العمل على قائمة الأمنيات، لاحظتُ بعض التوصيات التي يُمكننا البدء بتنفيذها، ولنواصل الحوار لنُحدّد بشكل أفضل كيف يُمكن لقائمة الأمنيات أن تُحقق نتائج أفضل في المستقبل.
- مجالات التركيز: أُضيفت مجالات التركيز ذات الطابع الخاص إلى قائمة أمنيات المجتمع حوالي عام 2024، نظرًا لكونها ميزة في قائمة أمنية ويكيميديا ألمانيا، والتي بدت أنها تُسهم في تحسين أداء النظام. يبدو أن هذه المجالات قد جعلت العملية أقل وضوحًا بشكل عام. نلتزم بإزالتها.
- وقت الاستجابة: أشار العديد من المحررين إلى بطء الاستجابة أو انعدامها لطلبات الرغبات وتذاكر فابريكاتور. أنا مهتم أيضًا بحل مشكلات تراكم الطلبات وسرعة الاستجابة في فابريكاتور، لكنني سأركز على قائمة الأمنيات في هذا النقاش. لقد التزمنا بوقت استجابة مدته 10 أيام عمل للطلبات المُقدمة. سننشر معلومات حول وقت الاستجابة مستقبلًا، كما فعلنا خلال الشهرين الماضيين في تحديثاتنا الشهرية، حتى يتمكن أعضاء المجتمع من متابعة أدائنا.
- التصويت السنوي على الأمنيات: في أكتوبر/تشرين الأول الماضي، أعدنا تفعيل التصويت. مع ذلك، لاحظ العديد من المحررين أننا لا ننشر إعلانات لدعوة الناس للمشاركة، مما أدى إلى مشاركة 30% فقط من العدد الإجمالي للمشاركين. أتفهم أهمية انتشار قائمة الأمنيات على نطاق واسع، لأنها وسيلة سهلة للمحررين العاديين للتعبير عن احتياجاتهم وأفكارهم (بينما يمثل استخدام الفابريكاتور أو التواصل المباشر مع فريق مؤسسة ويكيميديا عائقًا أكبر). يمكننا الالتزام بالعمل مع أعضاء المجتمع لتشجيع المشاركة. وقد فتح سومان نقاشًا حول شكل المشاركة السنوية في المستقبل. أرحب بمزيد من الحوار حول كيفية تطوير نظام تصويت أفضل.
- أمنيات الهاكاثون: لم يُطرح هذا الموضوع من قبل، ولكن خلال العامين الماضيين، أضفنا ميزة الأمنيات إلى هاكاثون ويكيميديا. ومن الأمثلة على ذلك، قيام المبرمجة كاتي فيلبرت بتلبية أمنية كتبها نوسفراتوس بإضافة فلتر نطاق التاريخ إلى محرك بحث الوسائط. ونعتزم الاستمرار في جعل هذه الميزة جزءًا أساسيًا من التحضير للهاكاثون.
- تحقيق الأمنيات: أُقدّر نشر باركيب لتحليل الأمنيات، وكذلك تحليل بروتوتايب بيرسبكتيف الذي نُشر قبل بضعة أشهر. طلب مايك من باركيب مقارنة ملاحظاته حول تحليله اليدوي لـ 46 أمنية. أنا مهتمٌّ بمعرفة سُبل تحسين دقة هذا التحليل مع مرور الوقت، واقترحتُ إنشاء تذاكر فابريكاتور تلقائيًا للأمنيات التي يتم اعتمادها. لديّ قائمة بالأماني التي التزمت بها فرق المؤسسة كجزء من الخطة السنوية للعام المالي 2026-2027 في مارس/أدار 2026، والمُخطط لتنفيذها خلال الاثني عشر شهرًا القادمة تقريبًا. سأضيف إلى هذه القائمة أي أمنيات جديدة يُمكننا الالتزام بها.
يُثير الرودودندريتس مسألة أخرى تتعلق بكيفية التواصل مع الأشخاص المناسبين في الوقت المناسب. لا تقتصر قنوات إسهام المجتمع في عمل مؤسسة ويكيميديا على قائمة الأمنيات فقط، بل تشمل أيضًا فابريكاتور، وديسكورد، والمناقشات في الفعاليات، وصفحات النقاش الخاصة بالمشاريع والفرق، والاجتماعات الدورية للمستخدمين ذوي الصلاحيات الموسعة. أودّ أن أتلقى منكم جميعًا مقترحات حول أفضل السبل للاستفادة من هذه القنوات مجتمعة، ولتمكين المتطوعين من الاطلاع على نتائج هذه الإسهامات.
وأخيرًا، إليكم آخر المستجدات بشأن التوظيف. كما ذكر فريقي في منشوراتنا السابقة، لا يزال جميع أعضاء فريق الدعم التقني المجتمعي الستة يعملون في المؤسسة، ويتلقون دعمًا داخليًا مُعجّلًا لإجراء مقابلات التوظيف للوظائف الشاغرة في المؤسسة. لقد أنهينا بعض عمليات التوظيف، ويسرّني أن أُعلن أن ثلاثة من المهندسين قد تلقوا عروضًا لوظائف في فرق أخرى، وقد قُبل اثنان منها بالفعل. وقد تم تشجيعهم على تحديث صفحاتهم في فرقهم وصفحاتهم الخارجية الأخرى متى ما شعروا بالراحة. ستدخل هذه التغييرات حيز التنفيذ رسميًا الأسبوع المقبل.
20 مايو/أيار 2026: يصبح تكنولوجيا المجتمع برنامج
مرحباً جميعاً، اسمي سومان، وأنا نائب رئيس قسم المنتجات والتكنولوجيا في مؤسسة ويكيميديا. أكتب إليكم لأشارككم قرارنا بإجراء بعض التغييرات الداخلية في آلية استجابة المؤسسة لرغبات المستخدمين ودعمها. بعد ملاحظة أن وجود فريق مركزي كان يؤدي إلى اختناقات وتأخيرات متكررة نتيجة تنسيق فريق تكنولوجيا المجتمع مع الفرق الأخرى، قررنا تحويل تكنولوجيا المجتمع إلى برنامج تتولى عدة فرق مسؤولية دعمه رسمياً. هذا نموذج أثبت نجاحه بالفعل، ولكنه سيستلزم حلّ فريق تكنولوجيا المجتمع وإلغاء مهام خمسة مهندسين ومدير واحد. لا يزال لدينا فريق متخصص لإدارة عملية استقبال قوائم الرغبات وفرزها، وسنواصل تقديم الدعم المالي نفسه لهذا العمل، ولكن ضمن هيكل مختلف.
في المستقبل، ستواصل قائمة الأمنيات العمل على تلبية رغبات المستخدمين من مختلف اللغات والمواقع الإلكترونية، وهي تُكمّل العديد من القنوات الأخرى التي نتلقى من خلالها بانتظام أفكارًا وملاحظات من المتطوعين (صفحات النقاش، وميادين، ومنصات الدردشة، والمكالمات، والمؤتمرات، إلخ). يُقدّم آخر تحديث للمجتمع تحديثًا مُفصّلًا حول تقدّمنا خلال الشهر الماضي، بما في ذلك تلبية رغبة في وسم وتتبع الصفحات التي يحتاج المستخدمون إلى تعديلها، وإضافة لغات جديدة إلى قسم "من كتب هذا؟" ولوحة معلومات P&E. في الأسابيع والأشهر القادمة، نأمل أن تلاحظوا جميعًا استمرارًا في زيادة سرعة وعدد الأمنيات التي نتمكن من تلبيتها بمرور الوقت من خلال إحصائياتنا الشهرية.
13 مايو/أيار 2023: آخر التحديثات من فريق المجتمع التقنية
مرحباً بالجميع! حان الوقت لمشاركة آخر المستجدات حول العمل الذي أنجزناه في الشهر الماضي، وما ينتظرنا من حيث ما سنعمل عليه.
العمل الذي أنجزناه في الشهر الماضي
كجزء من العمل على تسميات قائمة المراقبة، قمنا بإغلاق أمنية أخرى التي كانت تطالب بوضع علامات وتتبع الصفحات التي يحتاج المستخدمون إلى تعديلها بناءً على الأولوية ومستويات الاهتمام والمواضيع ومهام تحسين الصفحة. بالإضافة إلى ذلك، تم تضمين بعض الميزات المطلوبة من الرغبة في لوحة التحكم الشخصية التي تم نشرها حديثًا.
كما واصلنا العمل على إضافة لغات جديدة إلى أداة "من كتب ذلك" ولوحة معلومات P&E، حيث تتوفر الآن 12 لغة إضافية لهذه الأدوات. وقد تتوفر لغات أخرى في المستقبل.
علاوة على ذلك، كان فريق التحرير يعمل على أمنية تتعلق برسالة تحذير عند نسخ ولصق كميات كبيرة من المحتوى: ميزة وقد تم نشر هذا الآن في جميع مواقع الويكي، والفريق يطلب حاليًا التعليقات حوله.
أخيرًا، خلال هاكاثون ويكيميديا في ميلانو، عملت كاتي فيلبرت على رقعة برمجية لإضافة فلتر نطاق التاريخ لمحرك بحث الوسائط. الرقعة قيد المراجعة حاليًا.
ما نقوم به حاليًا
هذا ما نركز عليه حاليًا هذا الشهر:
- اجعل امتداد الرسم البياني سهل الاستخدام للمبتدئين: لقد انتهينا من بعض نماذج التصميم، والتي نشرناها على صفحة المشروع الجديدة، وبدأنا التنفيذ التقني للأمنية.
- دعم نماذج ثلاثية الأبعاد كاملة الألوان في مشاريع ويكيميديا: تم تحسين عرض النماذج ثلاثية الأبعاد (إضاءة المشهد وتوحيد مقياس النموذج، انظر هذا المثال). بالإضافة إلى ذلك، كنا نبحث في دعم GLB لـ 3d2png، لاستكشاف حل جديد محتمل للمشكلة، بعد أن وجدنا أن المحاولة الأولية لم تنجح. يمكنك متابعة التقدم على الفابريكيتور في phab:T424872.
- إضافة قوائم القراءة لتطبيق ويكيبيديا للهواتف المحمولة إلى الموقع الإلكتروني: تم نشر هذه الميزة لجميع مواقع الويكي في مرحلة تجريبية فقط بواسطة فريق القارئ، وسيتم مراقبتها لتحديد النشر الكامل للإنتاج.
ما سنحدده لاحقاً
وبالنظر إلى المستقبل، فقد حددنا بالفعل أولوياتنا للأشهر القادمة:
- أضف خيار "إخفاء القوالب" إلى صفحة "ماذا يصل هنا"، وهي أمنية كانت بالفعل ضمن أفضل 6 في استطلاع قائمة أمنيات المجتمع لعام 2022 والتي تحظى بدعم كبير في حلها من قبل المستخدمين الآن، وتركز على إزالة المقالات من صفحة "ماذا يصل هنا" إذا تم تضمينها في قالب، بدلاً من تضمينها مباشرة في النص.
- تعديل المقدمة بدلاً من المقالة بأكملها، وهي أمنية تطلب إمكانية تعديل مقدمة المقالة فقط، بدلاً من فتح المقالة بأكملها للقيام بذلك.
- طريقة لمعرفة سبب وجود ملف ما في مكان ما ضمن فئة معينة (أداة لعرض مسار الفئة)، وهي أمنية تطلب وظيفة تُظهر مسار تصنيف الملف إلى التصنيف الأصلي، بحيث يمكن للمرء اكتشاف التصنيف الخاطئ وإصلاحه.
- مشغل صوتي مناسب، وهي أمنية تدعو إلى تحسين الطريقة الحالية التي يعرض بها ويكيميديا كومنز ملفات الصوت ويستمع إليها.
- السماح بترتيب المناقشات في صفحات النقاش، وهي أمنية مُقترحة بالفعل في عام 2023، لمساعدة المشاريع والصفحات التي تعتمد ترتيبًا غير قياسي للمناقشات. فبدلاً من إجبار جميع المستخدمين على ترتيب واحد، يمكننا السماح لكل مستخدم بترتيب المناقشات زمنيًا حسب تفضيله، أو حتى حسب "آخر تعديل".
بعض الإحصائيات
فيما يلي لمحة سريعة توضح تفاصيل حالة الأمنيات خلال الشهر الماضي:
تتغير هذه الأرقام باستمرار نتيجةً لورود طلبات جديدة ومراجعة الطلبات قيد الدراسة بشكل معمق مع الجهات المعنية. وقد شهدت الأرقام الأكثر تغيراً خلال الشهر الماضي انخفاضاً في الطلبات قيد الدراسة (من 87 إلى 79)، وارتفاعاً في الطلبات ذات الأولوية (من 15 إلى 21)، وارتفاعاً في الطلبات التي تمثل فرصاً طويلة الأجل (من 204 إلى 210).
أخيراً، في أبريل/نيسان، وصلنا إلى وقت التحول الذي يقل قليلاً عن 3 أيام عمل لكل الأمنيات الجديدة المقبلة.
نحتاج إلى ملاحظاتك
وكما هو الحال دائماً، هناك مواضيع ومجالات نرغب في الحصول على ملاحظاتكم بشأنها. على وجه الخصوص:
- نُشرت الخطة السنوية لمؤسسة ويكيميديا للفترة 2026-2027، وتتضمن ست نتائج رئيسية ذات صلة بالأمنيات المتكررة. انضم إلى صفحة النقاش التي تتضمن العديد من المواضيع، والتي كتبها فريق قسم المنتجات والتكنولوجيا.
- على سبيل المثال، انظر إلى مناقشة حول الوافدين الجدد، وهو أمر ذو صلة بالرغبة الشائعة تمييز زر التحرير.
- نُشرت الآن المسودة التي شاركناها الشهر الماضي حول كيفية فرز وتحديد أولويات الرغبات التي يجب العمل عليها، وتمت إعادة تنظيم الصفحة إلى أقسام بسبب زيادة طولها.
- مع دخولنا السنة المالية الجديدة في يوليو، بدأنا بالتفكير في تحديث مجالات التركيز ونشرنا بعض الأفكار الأولية حيث يمكنك المشاركة.
وكما هو الحال دائمًا، إذا كانت لديكم أي أسئلة أو ملاحظات، يُرجى إخبارنا بذلك في صفحة نقاش قائمة أمنيات المجتمع. نتطلع بشوق إلى سماع آرائكم!
April 7, 2026: What we have done so far and what the team will be working on in the next months
Hello everyone! This time, we have a lot of news to share regarding the work done so far, and what’s coming next. This will also be the format going forward to provide more visibility into work.
The work we did in the last month
First of all, we are wrapping up work on Watchlist labels on all projects. This new feature allows users to add labels to items in their watchlist to help with managing and filtering watchlists, especially large ones. So far, 1,595 users across projects have created at least one label, and 3,554 labels have been created, for a total of 250,279 watchlist pages that have been assigned a label. We are happy about these initial results, and we expect these statistics to grow with time.
Other smaller wishes that we implemented in the last month are:
- "Preview page with this template" should not work with pages that do not transclude the template, a bug with the preview page feature;
- Google & DuckDuckGo search not indexing media files and categories on Commons, a wish related to the indexing of Commons on two main search engines that had quite some support;
- Allow editors to subscribe to community wishes, to allow editors to receive a cross-wiki notification if there is an update or reply;
- Editing mathematics is too difficult, a wish that requires simplifying the insertion of maths formulas in articles.
What we currently have in progress
We are also wrapping up work to be completed in the next few months, in collaboration with other Wikimedia Foundation teams, on wishes such as:
- Prevent VisualEditor from fabricating sources, that would fix a bug when generating automatically a reference through VisualEditor;
- Enable mul tags from Wikidata in the global watchlist, to let watchlists show the multilingual label from Wikidata when a local label isn’t entered;
- Three wishes related to Video2Commons (subtitle import, max resolution import, and enabling importing playlists);
- Allow abuse filters to be hidden to only oversighters, a request to mask private information needed for AbuseFilter needs;
- When searching Commons, under "Categories and Pages" show the category for the search term, a wish that was already presented in 2021.
What we are scoping next
Looking ahead, we already identified our priorities for the months to come, and it is a lot of work! Here’s a sneak peak at some of the work we defined as our next priorities:
- Add the "hide templates" option to What links here page, a wish that already made top 6 in the 2022 Community Wishlist survey and that has quite some support in its resolution by users now, that focuses on removing articles from “What links here” page if included in a template, rather than included directly in the text;
- Edit introduction instead of the entire article, a wish that asks for the possibility of editing only the incipit of an article, instead of opening the whole article in order to do it;
- we’re also about to conclude work on Make "Who Wrote That" tool and P&E Dashboard's Authorship Highlighting feature work in all languages, a wish about improving two well-used tools in the community.
We will also keep on our table the Support full colour 3D models on Wikimedia projects, a very popular wish among those submitted with 37 supporters. The team has already started working on it and is resolving new productionalization dependencies now. We also are continuing to evaluate and plan on how to scope and decompose Make the Chart extension beginner-friendly, since this is another well-supported wish (see discussion page to add feedback).
Meanwhile, we are working closely with other teams to solve other wishes, such as:
- Warn when large amount of content has been copy-pasted, that asks to warn users when they insert a large amount of content, and that will add a tag to the edit, so that patrollers are aware of a possible problem (we are working on this with the Editing team);
- Add Wikipedia Mobile App’s Reading Lists to the Website, to port the reading list functionality to the website, currently done with a browser extension (we are working on this with the Readers team);
- Make subreferencing work with inline refs and reflist, to expand the usability of the new subreferencing feature (see also the project page).
Some statistics
We also wanted to share some statistics with you regarding the current situation of wishes:
- so far, we closed 44 wishes as fulfilled (8% of the total of wishes);
- we have 17 wishes in progress and we have prioritized another 15 (meaning we will start working on them soon), totaling 7% of wishes;
- 204 wishes are categorized as long-term opportunities, but we commit to continually revisit these to determine whether some could become actionable in the near future;
- 78 wishes are considered community responses and we invite community to look at this to solve them;
- 79 wishes were closed due to duplication, alignment with community guidelines rather than technical issues, or lack of feasibility;
- lastly, another 87 are still under review by our various Foundation teams.
These numbers are regularly shifting due to new incoming wishes. For the past two months, we have also been responding to wishes consistently within a week of submission.
We need your feedback
To provide more transparency about how we triage and prioritize wishes, we want to also update our guidelines with tips on how to write a good wish. Please, join the discussion and have your say.
As always, if you have questions or feedback about it, please let us know in the Community Wishlist’s talk page. We are eager to hear from you!
18 فبراير/شباط 2026: آخر الأخبار عن العمل الجاري والقادم
مرحبا جميعا! لدينا بعض الأخبار الإضافية نشارككم إياها تتعلق بالعمل الذي أنجز حتى الآن وما سيجري تاليا في عملنا.
بادئ ذي بدء، نجحنا في تدشين ملصقات قائمة المراقبة على كافة المشاريع. هذه السمة الجديدة تسمح للمستخدمين إضافة ملصقات إلى بنود موجودة في قائمة مراقبتكم لتساعدكم في التعامل مع قوائم المراقبة وترشيحها، خاصة تلك الكبيرة. حتى الآن، أنشأ 1088 مستخدم من كافة المشاريع ملصق واحد على الأقل، وأنشأ عدد 2325 ملصق، في عدد إجمالي قدره 76,459 صفحة قائمة مراقبة أضيف إليها ملصق. يسرنا أن نرى هذه النتائج المبدئية ونتوقع أن تزيد هذه الإحصاءات بمرور الوقت.
Our team’s work is not done, by the way. We will take up two new wishes from the community. The first one will be “Add the "hide templates" option to What links here page”, previously wish #6 in the Community Wishlist Survey 2022, that focuses on removing articles from “What links here” page if included in a template, rather than included directly in the text.
The second one will be “Support full colour 3D models on Wikimedia projects”, a very popular wish among those submitted with 34 supporters. The team will probably work on it starting from what the community has already done in the past on the matter.
We also are evaluating and planning on how to scope and decompose “Make the Chart extension beginner-friendly”, since it's a very open wish. This is another very popular wish among those submitted. We will keep you posted on relevant developments.
As always, if you have questions or feedback about it, please let us know in the Community Wishlist’s talk page. We are eager to hear from you!
January 7, 2026: Update to statuses and to users’ watchlists
Hello everyone! For the first update of 2026, we got some interesting news to share with you.
First of all, we will revisit slightly the statuses for wishes, to better align our work with the needs of the users: more specifically, the “accepted” status will be merged with the “under review” status, and we will open the possibility to vote “under review” wishes; moreover, we will remove the “unsupported” status, that will be merged with the “community opportunity” status. This will mean that “unsupported” wishes can be part of the workstream of the Unsupported Tools Working Group, that has recently started an independent process to resolve some of these issues through shorter development cycles. In the next few days, we will update accordingly the statuses of the involved wishes.
In addition to this, we have some changes to Special:Watchlist that are coming, as part of our current work on the Watchlist labels project:
- we will update the display of Special:EditWatchlist as a first step towards watchlist labels;
- we will update pagination on Special:Search, as a part of the work on the Revamp pagination / page navigation wish.
As always, if you have questions or feedback about it, please let us know in the Community Wishlist’s talk page. We are eager to hear from you!