Dear all,

I hope this topic finds you all well. My name is Gorana Gomirac and I am a part of the Let’s Connect working group. We are a team of 8 who represent: Latina America, MENA, South Asia, East, South East Asia, Pacific, Sub-Saharan Africa, Central & Eastern Europe, Northern & Western region. If you are interested in participating in learning clinics , I welcome you to fill out this registration form. You will gain access to our monthly newsletter, our monthly learning clinics and even become a sharer where you and your community can give a workshop/learning clinic to our fellow Let’s Connectors. We look forward to include more topics about Wikivoyage so please feel free to reach out to us!

If you have any questions please email us at [email protected] Gorana Gomirac (VMRS) (talk) 12:59, 9 December 2024 (UTC)[reply]

First, thanks to everyone who has helped over the past few years. The class will return, as usual, in the Fall. In the meantime, I intend to collect feedback I got and revise it into a more formatted guide (at User:Hanyangprofessor2, to be moved to structured subpages), as well as into an academic paper similar to ones I've written in the past (GS). Feel free to offer any additional feedback, thoughts or comments (when the paper is mostly finished, I'll post a draft here for you to check it out). In the meantime, a question - are you familiar with any other educators running some activities on Wikivoyage? Piotrus (talk) 07:17, 6 January 2025 (UTC)[reply]

I recall we had Indian students on this site a number of years ago. I think you're the only one now. Ikan Kekek (talk) 08:23, 6 January 2025 (UTC)[reply]

If I'm not mistaken, the Nigeria + broader African expeditions we had were coordinated through WM Nigeria (or some equivalent group), though I'm not entirely sure how that worked. A few years back we also had an English teacher in France use Wikivoyage as a teaching tool. --SHB (t | c | m) 10:47, 6 January 2025 (UTC)[reply]

I used to be a teacher, and I organized a couple of Wikivoyage editing projects for students in 2017. —Granger (talk · contribs) 14:44, 6 January 2025 (UTC)[reply]

@Mx. Granger You stopped using Wikivoyage because job change or because it wasn't working out? Piotrus (talk) 01:12, 7 January 2025 (UTC)[reply]

Right, those were French high school students, as I recall. I didn't remember your educational project, Granger. Ikan Kekek (talk) 16:07, 6 January 2025 (UTC)[reply]

Probably – I can't exactly remember, and don't remember who the user was to check :(. SHB (t | c | m) 01:50, 7 January 2025 (UTC)[reply]

@Piotrus: Job change. I think the project was fairly successful. In addition to letting the students practice using English in an authentic context, it led to improved coverage of a few destinations in Uruguay. I monitored the students' edits and cleaned up the articles a little afterwards. @Ikan Kekek: It was discussed briefly here: Talk:Uruguay#Workshop tomorrow. —Granger (talk · contribs) 04:29, 7 January 2025 (UTC)[reply]

Dear All,

We’re happy to announce the launch of Wiki Loves Ramadan 2025, an annual international campaign dedicated to celebrating and preserving Islamic cultures and history through the power of Wikipedia. As an active contributor to the Local Wikipedia, you are specially invited to participate in the launch.

This year’s campaign will be launched for you to join us write, edit, and improve articles that showcase the richness and diversity of Islamic traditions, history, and culture.

• Topic: Wiki Loves Ramadan 2025 Campaign Launch
• When: Jan 19, 2025
• Time: 16:00 Universal Time UTC and runs throughout Ramadan (starting February 25, 2025).
• Join Zoom Meeting: https://us02web.zoom.us/j/88420056597?pwd=NdrpqIhrwAVPeWB8FNb258n7qngqqo.1
• Zoom meeting hosted by Wikimedia Bangladesh

To get started, visit the campaign page for details, resources, and guidelines: Wiki Loves Ramadan 2025.

Add your community here, and organized Wiki Loves Ramadan 2025 in your local language.

Whether you’re a first-time editor or an experienced Wikipedian, your contributions matter. Together, we can ensure Islamic cultures and traditions are well-represented and accessible to all.

Feel free to invite your community and friends too. Kindly reach out if you have any questions or need support as you prepare to participate.

Let’s make Wiki Loves Ramadan 2025 a success! → me. For the International Team 12:08, 16 January 2025 (UTC)

Hello everyone!

We’re excited to announce that the next Language Community Meeting is happening soon, February 28th at 14:00 UTC! If you’d like to join, simply sign up on the wiki page.

This is a participant-driven meeting where we share updates on language-related projects, discuss technical challenges in language wikis, and collaborate on solutions. In our last meeting, we covered topics like developing language keyboards, creating the Moore Wikipedia, and updates from the language support track at Wiki Indaba.

Got a topic to share? Whether it’s a technical update from your project, a challenge you need help with, or a request for interpretation support, we’d love to hear from you! Feel free to reply to this message or add agenda items to the document here.

Also, we wanted to highlight that the sixth edition of the Language & Internationalization newsletter (January 2025) is available here: Wikimedia Language and Product Localization/Newsletter/2025/January. This newsletter provides updates from the October–December 2024 quarter on new feature development, improvements in various language-related technical projects and support efforts, details about community meetings, and ideas for contributing to projects. To stay updated, you can subscribe to the newsletter on its wiki page: Wikimedia Language and Product Localization/Newsletter.

We look forward to your ideas and participation at the language community meeting, see you there!

MediaWiki message delivery 08:30, 22 February 2025 (UTC)[reply]

MediaWiki message delivery 23:14, 14 March 2025 (UTC)[reply]

Just a reminder that these events are "for up to an hour", but in recent years, it's usually been "for less than five minutes". Most people won't notice this at all, but if you do, just wait a couple of minutes and try your edit again. WhatamIdoing (talk) 21:50, 15 March 2025 (UTC)[reply]

(Apologies for posting in English)

Hello everyone, I am excited to share news of an upcoming online event called Wikidata and Sister Projects celebrating the different ways Wikidata can be used to support or enhance with another Wikimedia project. The event takes place over 4 days between May 29 - June 1st, 2025.

We would like to invite speakers to present at this community event, to hear success stories, challenges, showcase tools or projects you may be working on, where Wikidata has been involved in Wikipedia, Commons, WikiSource and all other WM projects.

If you are interested in attending, please register here. If you would like to speak at the event, please fill out this Session Proposal template on the event talk page, where you can also ask any questions you may have.

I hope to see you at the event, in the audience or as a speaker, - MediaWiki message delivery (talk) 09:18, 11 April 2025 (UTC)[reply]

The voting period for the revisions to the Universal Code of Conduct Enforcement Guidelines and U4C Charter closes on 1 May 2025 at 23:59 UTC (find in your time zone). Read the information on how to participate and read over the proposal before voting on the UCoC page on Meta-wiki.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review was planned and implemented by the U4C. For more information and the responsibilities of the U4C, you may review the U4C Charter.

Please share this message with members of your community in your language, as appropriate, so they can participate as well.

In cooperation with the U4C --

I am pleased announce, thanks to the rockstar that is @Taavi, the Commons Notification Deletion bot is finally back up and running! You should start seeing new talk page notifications soon (for eligible deletion discussions that are started after roughly 15 minutes ago).

Pinging @Ikan Kekek @SHB2000 @WhatamIdoing and @LPfi who have been asking for this for a very long time. I apologize for the two years of downtime. I am making efforts to ensure the bot stays running and something like this won't happen again.

Cheers and happy editing! — MusikAnimal ^talk 09:07, 4 May 2025 (UTC)[reply]

Awesome – I've been looking forward to this for a very long time and I'm very glad you and Taavi have made it possible! Thanks again. :) //shb (t | c | m) 09:09, 4 May 2025 (UTC)[reply]

I'm really relieved to hear this and look forward to decreasing my participation at c:Commons:Deletion requests. Thank you, and many thanks to Taavi! Ikan Kekek (talk) 16:06, 4 May 2025 (UTC)[reply]

This is great news. Thanks for letting us know. Taavi, you're awesome. WhatamIdoing (talk) 17:43, 6 May 2025 (UTC)[reply]

(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, the old Graph extension was disabled in 2023 due 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 the Charts extension, which will be replacing the old Graph extension and potentially also the EasyTimeline 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 from May 6. Please, consult our page on MediaWiki.org to discover when the new Charts extension will be deployed on your wiki. You can also consult 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 the project’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 the talk page or at Phabricator.

Thank you in advance! -- User:Sannita (WMF) (talk) 15:07, 6 May 2025 (UTC)[reply]

Does anyone remember whether we're using any of these? WhatamIdoing (talk) 17:44, 6 May 2025 (UTC)[reply]

I don't think we've ever used charts on this site – like, ever. //shb (t | c | m) 22:23, 6 May 2025 (UTC)[reply]

@WhatamIdoing, SHB2000: We do have {{Climate}}, but it probably never used the Graph extension. Sbb1413 (he) (talk • contribs) 03:35, 7 May 2025 (UTC)[reply]

Thanks.

@Sannita (WMF), I notice that mw:Extension:Chart/Project#Deployment Timeline only list mw.org and Wikipedias. What's the schedule for the non-Wikipedias? WhatamIdoing (talk) 05:04, 7 May 2025 (UTC)[reply]

Hi @WhatamIdoing, thanks for the question. The deployment for non-Wikipedia wikis will happen this week, along with most of the Wikipedias that are not scheduled for the next two weeks. It is up to you if the extension will be useful for your work or not. Sannita (WMF) (talk) 11:19, 7 May 2025 (UTC)[reply]

I believe it is useful for making a remastered version of the existing {{Climate}} template. Sbb1413 (he) (talk • contribs) 11:38, 7 May 2025 (UTC)[reply]

@WhatamIdoing and the others: there's a correction to my last message. There's been a change in the schedule yesterday for scaling purposes, so all non-Wikipedia wikis will be addressed after the deployment will be completed on all Wikipedias. This means that all non-Wikipedia wikis will have to wait until the end of the month at least. Sorry for the delay. Sannita (WMF) (talk) 11:06, 8 May 2025 (UTC)[reply]

Yeah I think that just uses some very complex css but never the formal MW extension. //shb (t | c | m) 09:39, 7 May 2025 (UTC)[reply]

The results of voting on the Universal Code of Conduct Enforcement Guidelines and Universal Code of Conduct Coordinating Committee (U4C) Charter is available on Meta-wiki.

You may now submit your candidacy to serve on the U4C through 29 May 2025 at 12:00 UTC. Information about eligibility, process, and the timeline are on Meta-wiki. Voting on candidates will open on 1 June 2025 and run for two weeks, closing on 15 June 2025 at 12:00 UTC.

If you have any questions, you can ask on the discussion page for the election. -- in cooperation with the U4C,

Keegan (WMF) (talk) 22:08, 15 May 2025 (UTC)[reply]

In some mildly optimistic news, we've finally reached 33,333 articles with the creation of Nassarawa. Thanks to everyone who has made this happen! //shb (t | c | m) 08:35, 16 May 2025 (UTC)[reply]

That's a good achievement, but it also tells us about our obsession with arbitrary patterns, like round figures (30,000), strings of the same digits (33,333), and so on. These are meaningless to many other number systems, like 30,000 and 33,333 are 7,530 and 8,235 in hexadecimal, respectively. Sbb1413 (he) (talk • contribs) 09:36, 16 May 2025 (UTC)[reply]

Haha definitely true – but I also think the fact that article count milestones on this project tend to be several years apart has something to do with this too. I expect 40k articles by 2034 and there's not a whole lot apart from 35k in between. //shb (t | c | m) 09:54, 16 May 2025 (UTC)[reply]

We have 36,000₁₀ = 𒐞 * 𒐕^𒐖 (10*100₆₀) – that's quite a round figure (and in an important base) – or 2⁵·3²·5³, the first prime numbers (in any base) raised to the previous of the numbers (with overflow rotation).

:-)

–LPfi (talk) 22:33, 16 May 2025 (UTC)[reply]

True, that's another worthy milestone for a project of this size. //shb (t | c | m) 02:19, 19 May 2025 (UTC)[reply]

This milestone makes me happy. WhatamIdoing (talk) 19:17, 17 May 2025 (UTC)[reply]

@Sannita (WMF): may I ask how this affects Wikivoyage when you say "some of the hypothesis involve your project"? TIA, //shb (t | c | m) 02:28, 26 May 2025 (UTC)[reply]

The proposed solutions mention the Wikivoyages in several places. The main issue is that an abstract article about Someplace shouldn't be rendered the same in Wikipedia and Wikivoyage. This affects also the technical solutions, such as where to store statements and functions. –LPfi (talk) 07:21, 26 May 2025 (UTC)[reply]

Can you explain further how we have abstract (vs. concrete?) articles on Wikivoyage? Ikan Kekek (talk) 07:27, 26 May 2025 (UTC)[reply]

We don't have any abstract articles at the time being, and I assume Wikivoyage in English may choose never to have them. For smaller languages, though, it is unrealistic to cover all interesting places with proper articles. The mission of Abstract Wikipedia is to provide a framework for creating articles in a way that allows automatic translation into something at least half-way decent. It's like having listings fetch key information from Wikidata, but scaled up to complete articles (or less complete – at least lively language on personal impressions will certainly be missing for the foreseeable future). –LPfi (talk) 07:43, 26 May 2025 (UTC)[reply]

I see – I still don't understand how this will fully get (even after reading the hypothesis), but I suppose it's something for smaller language projects. //shb (t | c | m) 09:47, 26 May 2025 (UTC)[reply]

Hi @SHB2000, it seems that @LPfi covered most of my arguments here already, so I would just repeat them at this point. The part that interests your project refers to the hypothesis that abstract content might (but it's still not sure at the moment) be stored in a dedicated namespace of your project. But again, this might happen, and you're free to refuse to store/use abstract content to further your development. This is entirely in your right, and we do not want to force any adoption of the project without consensus. Sannita (WMF) (talk) 10:01, 26 May 2025 (UTC)[reply]

And yes, Abstract Wikipedia is primarily intended for projects that have so far developed a small number of articles, in order to help them accelerate their growth and hopefully provide more knowledge to their communities and recruit a higher number of volunteers. Sannita (WMF) (talk) 10:03, 26 May 2025 (UTC)[reply]

Sounds perfect. Thanks to both of you for explaining! //shb (t | c | m) 10:10, 26 May 2025 (UTC)[reply]

Seconded. I understand. We should discuss in a separate thread whether it would be better to encourage, allow perhaps without comment, or disallow abstract listings on this site. I think we probably don't want abstract articles, but we should discuss that, too. Ikan Kekek (talk) 12:22, 26 May 2025 (UTC)[reply]

I can see abstract listings being useful for more obscure parts of the world for English speakers for this site at least, but overall sounds like it's something to help smaller language Wikivoyages benefit from us rather than the other way around (which is also great). //shb (t | c | m) 13:30, 26 May 2025 (UTC)[reply]

I mentioned listings as we already use Wikidata for them (coordinates) and have discussed e.g. opening hours (too complicated to be workable). I don't think "abstract listings" are an option at this point – somebody needs to decide a listing is wanted and would include some manual language when adding it. We still might have some valuable insights in how – and how not – to design abstract Wikivoyage articles for them to be useful. –LPfi (talk) 14:04, 26 May 2025 (UTC)[reply]

I have two thoughts about this:

• We need some way of separating a block of text that works for Wikipedia from a block of text that works for Wikivoyage (or another sister project). That suggests not using the English Wikipedia as the storage place for everything. The Wikipedias might all want "Jupiter is the largest planet in the Solar System. It is the fifth planet from the Sun", but if Wikivoyage were to have an article on the planet, it would probably sound a lot more like "Jupiter isn't a viable destination, but travelers interested in astronomy and navigationby the stars may be interested in the Big Museum of Jupiter and the Annual Jupiter Festival".
• I think that the English Wikivoyage could benefit from Abstract content. It's obvious that we could 'translate' our Star articles into Abstract, and thus other Wikivoyages would benefit. However, imagine how much we could benefit if @Sannita (WMF) brought it:Roma up to Star status, and then translated it for us to copy whatever bits we wanted in Rome. Keep in mind that while Abstract is set up to do dynamic autotranslation (e.g., always giving the latest population estimate, if the sentence says "the population of Rome is ___"), you can actually copy and paste the results as plain old text into an article.

WhatamIdoing (talk) 17:07, 26 May 2025 (UTC)[reply]

If I understand correctly, Abstract Wikipedia works with programming that could have been done in the 1980s, more or less like Lsjbot's articles, although not confined to info found in already existing datasets. "Not a viable destination" would need to be an item to insert and translate. That article on Jupiter would have very little in common with the Wikipedia one.

For Rome, population statistics etc. would be easy to write in abstract form, but an abstract star article would need a lot of article-specific functions, which need to be translated to get a version in another language – and lively language is hard to translate automatically (think "blind and therefore insane"). Copying over listings would work, and a good abstract article should have a good selection of those.

I think an abstract Wikivoyage article should focus on being reasonably complete by having information: roads and trains for getting in, listings with coords, contact details and Wikidata link, and suggestions in Go next, but quite little running text, mostly identical across articles except data values (…is a village/town/city in X…), and likewise a dry list of facts in the listing "content", not like the lively writing in Wikivoyage:Listings.

–LPfi (talk) 17:47, 26 May 2025 (UTC)[reply]

As Wikivoyage has generally has more structured articles than Wikipedia, I think that we could make use of an Abstract Wikivoyage. Two areas look like possible starting points: listings and the phrases in phrasebooks.

If a tool could create an abstract version of a listing that exists in another language, then the listing could be offered when editing the same section of an article here - "Would you like to add a listing for the Lawnmower Museum?". Some parts of listing could be updated in all languages when edited in one - we would show the last updated entry price for the museum whatever language it was edited in. A difficult part is identifying when listing elements are language specific - we may use a different url from another WV to point to a page in English, and we don't care that the museum has labels translated into Spanish.

In English WV we have a standard set of phrases for phrasebooks, and most phrasebooks keep fairly closely to this list. This list is also the basis for phrasebooks in some other language WVs. It would appear to be reasonably straightforward to scan the existing phrases to create an abstract phrasebook, but inconsistencies would need to be reviewed. There are about 300 phrasebooks in English, 50 in German and 20 in Polish. Maybe we can use this to offer over 200 phrasebooks in Polish. AlasdairW (talk) 22:44, 26 May 2025 (UTC)[reply]

For listings, yes, the abstract versions would be easy to create. For the name, we only need to identify the native name, its romanisation, and the language of translated names. There are already structures for all this in Wikidata; also "official URL" has a language attribute. Amenities of hotels can likewise easily be described. Nothing will be automatically fetched, so no worries about info irrelevant for English speakers. What is hard to do is the lively language of the examples I linked above.

For phrasebooks, I am not sure it is that easy, or rather whether creating an abstract phrasebook helps compared to just translating the template and using a dictionary (or whatever way you otherwise use for getting translations). Grammar and pronunciation sections needs to be written with the audience's language knowledge in mind, and translations of phrases need to be done with some understanding of the context, thus mostly manually. For a good phrasebook, you also need to note peculiarities in the relation with the target language, such as the liberty/liberté etc. now added to the French and Italian phrasebook and warnings for specific false friends.

–LPfi (talk) 04:57, 27 May 2025 (UTC)[reply]

I think phrasebooks is one of those things (along with travel topics) where it's more or less impossible to create an abstract version of. //shb (t | c | m) 05:23, 27 May 2025 (UTC)[reply]

Why do you think that?

We can already write things like "hello, a cup of coffee, please" by invoking Wikidata. It would require expansion (e.g., to add "a" and "an"), but it doesn't seem impossible in principle, at least for simpler sentences. WhatamIdoing (talk) 17:24, 27 May 2025 (UTC)[reply]

The question is whether there is any point of doing that. If every phrase has to be purpose-translated, then why not just write the non-abstract phrasebook? The point with the abstract articles is that there are standard phrases that can be used across articles, such as words for amenities you will find in many hotels. For the phrasebook phrases, the question is whether the same Sámi phrase would suite the phrasebook in English and the one in Latvian (or whatever).

When the English phrase is translated differently depending on context, some commentary needs to be added (formal/informal, feminine/masculine). This commentary is redundant or awkward in languages that make the same distinction, possibly treating the two (or more) forms as totally unrelated (the person is deceased, the cow is dead).

For the cup of tea, you may need to word that differently depending on whether you are a man or woman, and whether the one you are asking for the cup is a waiter, the café owner, your host or your host's young child.

–LPfi (talk) 20:59, 27 May 2025 (UTC)[reply]

Perhaps an example would show what I was thinking of:

In French phrasebook, we have:

How much is a ticket to _____?

Combien coûte le billet pour _____ ? (kom-BYAN koot luh bee-YEH poor)

One ticket to _____, please.

Un billet pour _____, s'il vous plaît. (ung bee-YEH poor ____ seel voo pleh)

On Polish WV there is pl:Rozmówki francuskie, their French Phrasebook.

Ile kosztuje bilet do...?

Combien coûte le billet pour...?

Poproszę jeden bilet do...

Un billet pour..., je vous prie.

We also have Finnish phrasebook, which has:

How much is a ticket to _____?

Paljonko maksaa lippu _____in? (PAHL-yonk-aw MAHK-sah LEEP-poo _____?)

So I think that a Finnish phrasebook on the Polish WV, could have

Ile kosztuje bilet do...?

Paljonko maksaa lippu _____in? (PAHL-yonk-aw MAHK-sah LEEP-poo _____?)

"One ticket to" is not exactly the same (translating the French used in Polish, it is saying "I beg you" rather than "please"), so this phase would require some manual adjustments when it was abstracted. AlasdairW (talk) 22:24, 27 May 2025 (UTC)[reply]

I don't think that the idea with Abstract is to program in "please", but rather to swap in whichever word or phrase is used in that language to indicate politeness and respect while making a request.

We already have a software switch for gender, so this is not some miraculous future tech; this is an expansion of what has been possible for years. WhatamIdoing (talk) 01:39, 28 May 2025 (UTC)[reply]

For Finnish, there is no word or phrase that indicates politeness, but one often uses the conditional (?) verb form instead. In some cases one would just use that word form in the phrase (in the Finnish phrasebooks and in phrasebooks for Finnish) – but here the question is instead with no sign of politeness, which is common in that language. Something like "could you" is problematic as most languages make a distinction between thou and you. I think the common cases can be handled decently, but for less well-known language families – those that benefit most from the abstract articles – the edge cases will be more common. It is likely that abstract phrasebook have to be tweaked for specific languages to avoid the odd case of very problematic renderings. –LPfi (talk) 06:02, 28 May 2025 (UTC)[reply]

In Malay, there are two words for "please" that have different meanings and are used in different contexts. There are also two words for "we" that have different meanings. Etc. Ikan Kekek (talk) 09:34, 30 May 2025 (UTC)[reply]

I would expect all the foreign phrases to be reproduced exactly as they were in the existing phrasebook(s) that they were taken from. Ideally the left side phrases would also be exact reproductions, unless they were used to create a phrasebook to be part of a WV that doesn't currently have any phrasebooks; but it is less of an issue if the left side doesn't read perfectly. I am assuming that an Abstract Wikivoyage would have some mechanism for handling quoted text, as this is essential for reproducing the exact words used in famous speeches etc, and will be required for abstract Wikipedia and Wikiquote etc. AlasdairW (talk) 14:06, 30 May 2025 (UTC)[reply]

@WhatamIdoing: LPfi's basically explained why I don't think abstract phrasebooks will work. //shb (t | c | m) 23:25, 27 May 2025 (UTC)[reply]

More languages • Please help translate to your language

Dear all,

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

Thank you!

[1] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Results

[2] https://foundation.wikimedia.org/wiki/Committee:Elections_Committee_Charter

[3] https://foundation.wikimedia.org/wiki/Resolution:Committee_Membership,_December_2024

[4] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_committee/Roles

[5] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2025/FAQ

[6] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2025/Questions_for_candidates

Best regards,

Victoria Doronina

Board Liaison to the Elections Committee

Governance Committee

MediaWiki message delivery (talk) 03:08, 28 May 2025 (UTC)[reply]

https://www.thrillist.com/travel/nation/ai-travel-apps —Justin (koavf)❤T☮C☺M☯ 07:04, 1 June 2025 (UTC)[reply]

I wonder whether we can design an AI tool that can fetch info from Wikivoyage and make a summary for you. That can replace the burden of manual summary writing by Wikivoyagers. Of course, Wikivoyage articles should be curated by humans, with AI summarizing them. I want to suggest this to Wikipedians as well, but I have been blocked there since 2021, and I mostly work on the Bengali Wikipedia. Sbb1413 (he) (talk • contribs) 07:11, 1 June 2025 (UTC)[reply]

Surprised this was sent very late. I made a guide on all the candidates on Meta at m:User:SHB2000/U4C guide 2025, for those interested. //shb (t | c | m) 03:13, 14 June 2025 (UTC)[reply]