我間唔中用香港公共圖書館電腦上維基百科，但發現近排（未有刻意紀錄幾時開始，應該大約3月開始）上維基百科（包括粵文、中文、英文），經常載入好耐後出現Timed out錯誤，頭一兩次遇到以為咁啱網絡繁忙，但接連幾次於唔同時段於唔同圖書館上都有問題，試過用Chrome同Firefox亦都一樣，都係時得時唔得。究竟係維基伺服器阻攔香港公共圖書館嘅IP，定係香港公共圖書館阻攔連去維基伺服器嘅連線？（送出呢個留言又出現「The server did not respond within the expected time.」，要重新載入先至可以送出）~2025-46706 (talk)2025年4月19號 (六) 07:02 (UTC)[回覆]
Sub-referencing: User testing
Apologies for writing in English, please help us by providing a translation below
Get a sneak peak and help shape theVisual Editor user designs
Help us test the new design prototypes by participating in user sessions –sign up here to receive an invite. We're especially hoping to speak with people from underrepresented and diverse groups. If that's you, please consider signing up! No prior or extensive editing experience is required. User sessions will startMay 14th.
We plan to bring this feature to Wikimedia wikis later this year. We’ll reach out to wikis for piloting in time for deployments. Creators and maintainers of reference-related tools and templates will be contacted beforehand as well.
Thank you very much for your support and encouragement so far in helping bring this feature to life!
We will be enabling the new Charts extension on your wiki soon!
(Apologies for posting in English)
Hi all! We have good news to share regarding the ongoing problem with graphs and charts affecting all wikis that use them.
As you probably know, theold Graph extension was disabled in 2023due to security reasons. We’ve worked in these two years to find a solution that could replace the old extension, and provide a safer and better solution to users who wanted to showcase graphs and charts in their articles. We therefore developed theCharts extension, which will be replacing the old Graph extension and potentially also theEasyTimeline extension.
After successfully deploying the extension on Italian, Swedish, and Hebrew Wikipedia, as well as on MediaWiki.org, as part of a pilot phase, we are now happy to announce that we are moving forward with the next phase of deployment, which will also include your wiki.
The deployment will happen in batches, and will start fromMay 6. Please, consultour page on MediaWiki.org to discover when the new Charts extension will be deployed on your wiki. You can alsoconsult the documentation about the extension on MediaWiki.org.
If you have questions, need clarifications, or just want to express your opinion about it, please refer to theproject’s talk page on Mediawiki.org, or ping me directly under this thread. If you encounter issues using Charts once it gets enabled on your wiki, please report it on thetalk page or atPhabricator.
Separation of the new right (checkuser-temporary-account) out to a new group (Temporary account IP viewers), as opposed to technically attaching it to anyexisting group (like patroller). 我哋基於幾個原因決定噉做：
While this isn’t an objection, the way this change is being phrased is odd and I find this very disconcerting if this is typical of how things are decided at WMF.
I am one of those users who have ever used the reveal IP function, and if my own experience is representative, thereason why very few users have ever used the function is probably because it is not obvioushow to reveal IP addresses; in fact, for a very long time I thought the right had no function at all, and I’d believe most people probably thought the same. (ETA: To clarify, who will go into their preferences to check for new options? hardly anyone ever.)Alıƨsi (傾偈)2025年5月16號 (五) 03:56 (UTC)[回覆]
PS: Sometimes I really wonder if there are designers working for WMF. Even a properly trained graphic designer would help, but a properly trained industrial designer would reveal a lot of process-related issues; this specific decision is totally related to not seeing pain points in the user journey. (Disclaimer: I am neither.)Alıƨsi (傾偈)2025年5月16號 (五) 04:09 (UTC)[回覆]
Hello @Al12si, sure, some people haven't used IP reveal because they don't know how to enable it. To address this, we are working on anonboarding dialog. It will be displayed when users visit Recent Changes, Watchlist, or History pages, and it will explain some things, including how to enable the feature. Check the Phabricator ticket for more details. (Note that our designer is working on the dialog - so you were very correct about what should be done and by whom ^^)SGrabarczuk (WMF) (傾偈)2025年5月16號 (五) 17:11 (UTC)[回覆]
@SGrabarczuk (WMF) – The general problem here is that the whole decision is based on a false premise. It’s useless to make the decision first, then try to address the false premise; the false premise has already been used to justify the decision, and from the wording of the announcement, the decision is already final. Zero consultation. Zero research.
This is part of a series of general process-related issues that I have been seeing (this specific one is relatively minor, I have been bullied before); I seriously suggest WMF take the time to look at these policies from an industrial designer’s POV, with user journeys as a start.Alıƨsi (傾偈)2025年5月18號 (日) 19:38 (UTC)[回覆]
Join the 6th Wikipedia Pages Wanting Photos Campaign – 2025 Edition
Dear Wikipedia community,
We invite your community to participate in the 6th edition of theWikipedia Pages Wanting Photos Campaign, a global campaign taking place from July 1 to August 31, 2025.
Participants will choose among Wikipedia pages without photos, then add a suitable photo from among the many thousands of photos in the Wikimedia Commons, especially those uploaded from thematic contests (Wiki Loves Africa,Wiki Loves Earth,Wiki Loves Folklore,Wiki Loves Monuments, etc.) over the years.
More than 80 Wikimedia affiliates have participated since the campaign was launched in 2020 and have added images to more than 400,000 Wikipedia articles in over 245 Wikipedia languages. Thanks to the volunteer contributors!
We now invite your community to organize and lead the campaign within your community. As a local organizer, you may:
Encourage individual members to take part by adding images to Wikipedia articles.
Host edit-a-thons focused on improving visual content.
Organize training workshops to teach contributors how to correctly integrate images into Wikipedia.
These activities will help build local capacity and increase visual content across Wikipedia.
Please note that for participants to be eligible to participate in the campaign, they need to have registered an account for at least a year before the official start date of the contest. That is, for the 2025 edition, they must have registered an account on or before July 1, 2025. The account can be from any Wikimedia project wikis.
The organizing team is looking for a contact person to coordinate WPWP participation at the Wikimedia user group or chapter level (geographically or thematically) or for a language Wikipedia.
Hi @UOzurumba (WMF), I don’t know if this is completely off-topic or if it counts as some sort of feedback, but I’m not sure if it’s a good idea to actively encourage translations. In my personal experience, translations (especially if it’s of a single section) often cause more problems than they solve (not just here, but also on the French Wikipedia where I also do some edits). There are a few reasons this is the case, but one major cause is a mismatch in overall article structure between the source and target Wikipedias.
(I have seen this happen even on the English Wikipedia, though merely at a copy editing level and not at a structural editing level, where an article was clearly translated from frwiki, but where the translator clearly was completely unfamiliar with frwiki conventions.)
If machine translation is involved, some people also don’t check their work afterwards (here specifically, if this isn’t a thing on other wikis); this can cause a whole load of problems, which can sometimes be very difficult to correct (in some cases, the easiest fix would be to scrap the entire translated section(s) and rewrite, which is something usually not done, partly out of respect for the translator and partly because the section(s) had been translated because it was (they were) difficult to write in the first place).Alıƨsi (傾偈)2025年6月26號 (四) 06:37 (UTC)[回覆]
Thank you @Al12si for this feedback. Your cross-wiki experience on both English and French Wikipedia provides a valuable perspective on translation challenges. However, it deviates from the communication in question, which is the proposal to enable the Contribute menu. I will clarify that the Contribute menu serves as a central access point for various contribution tools, and the translation tool is one of the many tools that will have its entry point in the Contribute menu.
You raise a relevant concern about the mismatch of article structure when translating content in sections and quality issues that can arise from translations, whether machine-assisted or manual. We're aware of the mismatch as reported here andthe team is working to resolve it.
For communities experiencing problems with machine translation (MT) quality and abuse of the support in the Content translation tool, I recommend discussing adjusting the machine translation limit, which is a mechanism that restricts the publishing of the initial automatic translation without reviewing and editing it with your community and agree on a suitable limit.
In deciding how strict the automatic translation should be, your community should consider different samples of the automatic translation as case studies and agree on a suitable thresholdbased on its accuracy and the extent to which translators edit the machine translation.
Once a consensus is reached on the percentage of adjustment (e.g., 99% automatic translation and 1% adjustment), you can create a Phabricator ticket likethis one so that the WMF Language team can adjust the machine translation limit.
I hope my response was helpful. Please don't hesitate to ask any additional questions, and if there are no objections, we will proceed with the deployment as planned.
Wikidata Item and Property labels soon displayed in Wiki Watchlist/Recent Changes
(Apologies for posting in English, you can help by translating into your language)
Hello everyone, theWikidata For Wikimedia Projects team is excited to announce an upcoming change in how Wikidata edit changelogs are displayed in yourWatchlists andRecent Changes lists. If an edit is made on Wikidata that affects a page in another Wikimedia Project, the changelog will contain some information about the nature of the edit. This can include a QID (or Q-number), a PID (or P-number) and a value (which can be text, numbers, dates, or also QID or PID’s). Confused by these terms? See theWikidata:Glossary for further explanations.
The upcoming change is scheduled for17.07.2025, between1300 - 1500 UTC.The change will display the label (item name) alongside any QID or PIDs, as seen in the image below:
These changes will only be visible if you have Wikidata edits enabled in your User Preferences for Watchlists and Recent Changes, or have the active filter ‘Wikidata edits’ checkbox toggled on, directly on the Watchlist and Recent Changes pages.
Your bot and gadget may be affected! There are thousands of bots, gadgets and user-scripts and whilst we have researched potential effects to many of them, we cannot guarantee there won’t be some that are broken or affected by this change.
Further information and context about this change, including how your bot may be affected can be found on thisproject task page. We welcome your questions and feedback, please write to us on this dedicatedTalk page.
另外，我哋想強調一下，第六版嘅《語言與國際化通訊》（2025年1月）可以喺呢度睇到：維基媒體語言同產品本地化/通訊/2025/1月。 呢份通訊提供咗2024年10月至12月季度嘅最新消息，包括新功能開發、各種同語言相關嘅技術項目同支援工作嘅改進、有關社群會議嘅詳情，同埋為項目作出貢獻嘅想法。 如果想緊貼最新消息，你可以喺佢嘅 wiki 頁面訂閱通訊：維基媒體語言同產品本地化/通訊.
Ukraine's Cultural Diplomacy Month 2025: Invitation
請幫手去譯做你嘅語言
Hello, dear Wikipedians!
Wikimedia Ukraine, in cooperation with theMFA of Ukraine andUkrainian Institute, has launched the fifth edition of writing challenge "Ukraine's Cultural Diplomacy Month", which lasts from14th April until16th May 2025. The campaign is dedicated to famous Ukrainian artists of cinema, music, literature, architecture, design, and cultural phenomena of Ukraine that are now part of world heritage. We accept contributions in every language!
The most active contesters will receive prizes.
If you are interested in coordinating long-term community engagement for the campaign and becoming a local ambassador, we would love to hear from you! Please let us know your interest.
We invite you to take part and help us improve the coverage of Ukrainian culture on Wikipedia in your language! Also, we plan to set up abanner to notify users of the possibility to participate in such a challenge!OlesiaLukaniuk (WMUA) (talk)
TheUniversal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review of the EG and Charter was planned and implemented by the U4C. Further information will be provided in the coming months about the review of the UCoC itself. For more information and the responsibilities of the U4C, you mayreview the U4C Charter.
Please share this message with members of your community so they can participate as well.
Call for Candidates for the Universal Code of Conduct Coordinating Committee (U4C)
The results of voting on the Universal Code of Conduct Enforcement Guidelines and Universal Code of Conduct Coordinating Committee (U4C) Charter isavailable on Meta-wiki.
RfC ongoing regarding Abstract Wikipedia (and your project)
(Apologies for posting in English, if this is not your first language)
Hello all! We opened a discussion on Meta about a very delicate issue for the development ofAbstract Wikipedia: where to store the abstract content that will be developed through functions from Wikifunctions and data from Wikidata. Since some of the hypothesis involve your project, we wanted to hear your thoughts too.
We want to make the decision process clear: we do not yet know which option we want to use, which is why we are consulting here. We will take the arguments from the Wikimedia communities into account, and we want to consult with the different communities and hear arguments that will help us with the decision. The decision will be made and communicated after the consultation period by the Foundation.
This year, the term of 2 (two) Community- and Affiliate-selected Trustees on the Wikimedia Foundation Board of Trustees will come to an end [1]. The Board invites the whole movement to participate in this year’s selection process and vote to fill those seats.
The Elections Committee will oversee this process with support from Foundation staff [2]. The Governance Committee, composed of trustees who are not candidates in the 2025 community-and-affiliate-selected trustee selection process (Raju Narisetti, Shani Evenstein Sigalov, Lorenzo Losa, Kathy Collins, Victoria Doronina and Esra’a Al Shafei) [3], is tasked with providing Board oversight for the 2025 trustee selection process and for keeping the Board informed. More details on the roles of the Elections Committee, Board, and staff are here [4].
Here are the key planned dates:
May 22 – June 5: Announcement (this communication) and call for questions period [6]
June 17 – July 1, 2025: Call for candidates
July 2025: If needed, affiliates vote to shortlist candidates if more than 10 apply [5]
August 2025: Campaign period
August – September 2025: Two-week community voting period
October – November 2025: Background check of selected candidates
Board’s Meeting in December 2025: New trustees seated
Learn more about the 2025 selection process - including the detailed timeline, the candidacy process, the campaign rules, and the voter eligibility criteria - on this Meta-wiki page[link].
Call for Questions
In each selection process, the community has the opportunity to submit questions for the Board of Trustees candidates to answer. The Election Committee selects questions from the list developed by the community for the candidates to answer. Candidates must answer all the required questions in the application in order to be eligible; otherwise their application will be disqualified. This year, the Election Committee will select 5 questions for the candidates to answer. The selected questions may be a combination of what’s been submitted from the community, if they’re alike or related.[link]
Election Volunteers
Another way to be involved with the 2025 selection process is to be an Election Volunteer. Election Volunteers are a bridge between the Elections Committee and their respective community. They help ensure their community is represented and mobilize them to vote. Learn more about the program and how to join on this Meta-wiki page[link].
Upcoming Deployment of the CampaignEvents Extension
Hello everyone,
(Apologies for posting in English if English is not your first language. Please help translate to your language.)
The Campaigns Product Team is planning a global deployment of theCampaignEvents extension to all Wikipedias, including this wiki, during theweek of June 23rd.
This extension is designed to help organizers plan and manage events, WikiProjects, and other on-wiki collaborations - and to make these efforts more discoverable.
Invitation Lists: A tool to help organizers find editors who might want to join, based on their past contributions.
Note: The extension comes with a new user right called"Event Organizer", which will be managed by administrators on this wiki. Organizer tools like Event Registration and Invitation Lists will only work if someone is granted this right. The Collaboration List is available to everyone immediately after deployment.
The extension is already live on several wikis, includingMeta, Wikidata, English Wikipedia, and more ( See the full deployment list)
If you have any questions, concerns, or feedback, please feel free to share them on the extension talkpage. We’d love to hear from you before the rollout.
This year, the Wikimedia community will vote in late August through September 2025 to fill two (2) seats on the Foundation Board. Could you – or someone you know – be a good fit to join the Wikimedia Foundation's Board of Trustees? [3]
Learn more about what it takes to stand for these leadership positions and how to submit your candidacy onthis Meta-wiki page or encourage someone else to run in this year's election.
Best regards,
Abhishek Suryawanshi Chair of the Elections Committee
On behalf of the Elections Committee and Governance Committee
A vision of relevant, accessible, and impactful free knowledge has always guided the Wikimedia Movement. As the ecosystem of Wikimedia projects continues to evolve, it is crucial that we periodically review existing projects to ensure they still align with our goals and community capacity.
Despite their noble intent, some projects may no longer effectively serve their original purpose.Reviewing such projects is not about giving up – it's about responsible stewardship of shared resources. Volunteer time, staff support, infrastructure, and community attention are finite, and the non-technical costs tend to grow significantly as our ecosystem has entered a different age of the internet than the one we were founded in. Supporting inactive projects or projects that didn't meet our ambitions can unintentionally divert these resources from areas with more potential impact.
Moreover, maintaining projects that no longer reflect the quality and reliability of the Wikimedia name stands for, involves a reputational risk. An abandoned or less reliable project affects trust in the Wikimedia movement.
Lastly,failing to sunset or reimagine projects that are no longer working can make it much harder to start new ones. When the community feels bound to every past decision – no matter how outdated – we risk stagnation. A healthy ecosystem must allow for evolution, adaptation, and, when necessary, letting go. If we create the expectation that every project must exist indefinitely, we limit our ability to experiment and innovate.
Because of this, SPTF reviewed two requests concerning the lifecycle of the Sister Projects to work through and demonstrate the review process. We chose Wikispore as a case study for a possible new Sister Project opening and Wikinews as a case study for a review of an existing project. Preliminary findings were discussed with the CAC, and a community consultation on both proposals was recommended.
Wikispore
Theapplication to consider Wikispore was submitted in 2019. SPTF decided to review this request in more depth because rather than being concentrated on a specific topic, as most of the proposals for the new Sister Projects are, Wikispore has the potential to nurture multiple start-up Sister Projects.
After careful consideration, the SPTF has decidednot to recommend Wikispore as a Wikimedia Sister Project. Considering the current activity level, the current arrangement allowsbetter flexibility and experimentation while WMF provides core infrastructural support.
We acknowledge the initiative's potential and seek community input on what would constitute a sufficient level of activity and engagement to reconsider its status in the future.
As part of the process, we shared the decision with the Wikispore community and invited one of its leaders, Pharos, to an SPTF meeting.
Currently, we especially invite feedback on measurable criteria indicating the project's readiness, such as contributor numbers, content volume, and sustained community support. This would clarify the criteria sufficient for opening a new Sister Project, including possible future Wikispore re-application. However, the numbers will always be a guide because any number can be gamed.
Wikinews
We chose to review Wikinews among existing Sister Projects because it is the one for which we have observed the highest level of concern in multiple ways.
Since the SPTF was convened in 2023, its members have asked for the community's opinions during conferences and community calls about Sister Projects that did not fulfil their promise in the Wikimedia movement.[1][2][3] Wikinews was the leading candidate for an evaluation because people from multiple language communities proposed it. Additionally, by most measures, it is the least active Sister Project, with the greatest drop in activity over the years.
While the Language Committee routinely opens and closes language versions of the Sister Projects in small languages, there has never been a valid proposal to close Wikipedia in major languages or any project in English. This is not true for Wikinews, where there was a proposal to close English Wikinews, which gained some traction but did not result in any action[4][5], see section 5 as well as a draft proposal to close all languages of Wikinews[6].
Initial metrics compiled by WMF staff also support the community's concerns about Wikinews.
Based on this report, SPTF recommends a community reevaluation of Wikinews. We conclude that its current structure and activity levels are the lowest among the existing sister projects. SPTF also recommends pausing the opening of new language editions while the consultation runs.
SPTF brings this analysis to a discussion and welcomes discussions of alternative outcomes, including potential restructuring efforts or integration with other Wikimedia initiatives.
Options mentioned so far (which might be applied to just low-activity languages or all languages) include but are not limited to:
Restructure how Wikinews works and is linked to other current events efforts on the projects,
Merge the content of Wikinews into the relevant language Wikipedias, possibly in a new namespace,
Merge content into compatibly licensed external projects,
Archive Wikinews projects.
Your insights and perspectives are invaluable in shaping the future of these projects. We encourage all interested community members to share their thoughts on the relevant discussion pages or through other designated feedback channels.
Feedback and next steps
We'd be grateful if you want to take part in a conversation on the future of these projects and the review process. We are setting up two different project pages:Public consultation about Wikispore andPublic consultation about Wikinews. Please participate between 27 June 2025 and 27 July 2025, after which we will summarize the discussion to move forward. You can write in your own language.
I will also host a community conversation 16th July Wednesday 11.00 UTC and 17th July Thursday 17.00 UTC (call links to follow shortly) and will be around at Wikimania for more discussions.
Help us decide the name of the new Abstract Wikipedia project
你好. Please help pick a name for the new Abstract Wikipedia wiki project. This project will be a wiki that will enable users to combine functions fromWikifunctions and data from Wikidata in order to generate natural language sentences in any supported languages. These sentences can then be used by any Wikipedia (or elsewhere).
There will be two rounds of voting, each followed by legal review of candidates, with votes beginning on 20 October and 17 November 2025. Our goal is to have a final project name selected on mid-December 2025. If you would like to participate, thenplease learn more and vote now at meta-wiki.多謝！
Applications for the committees open on October 30, 2025. Applications for the Affiliations Committee, Ombuds commission and the Case Review Committee close on December 11, 2025. Learn how to apply byvisiting the appointment page on Meta-wiki. Post to the talk page or email cstwikimedia.org with any questions you may have.
Reminder: Help us decide the name of the new Abstract Wikipedia project
你好. Reminder: Please help to choose name for the new Abstract Wikipedia wiki project. The finalist vote starts today. The finalists for the name are:Abstract Wikipedia, Multilingual Wikipedia, Wikiabstracts, Wikigenerator, Proto-Wiki. If you would like to participate, thenplease learn more and vote now at meta-wiki.多謝！
.png)
