Jump to content

Wikimedia Café/Reports/Meeting notes for 2026 05

From Meta, a Wikimedia project coordination wiki

May 2026 meetings with a focus on Wikimedia Foundation Annual Plan/2026-2027

[edit]

Date and time for the Americas, Africa, and Europe-friendly time slot

[edit]
Table of local times. See also this Zonestamp link, and this external website.
Time zone Day of week Date Local start time UTC offset Daylight savings notes
Hawaii Standard Time Saturday 30 May 05:00 -10 Used year-round in Hawaii
Pacific Time Zone in United States and Mexico Saturday 30 May 08:00 -7 Observes DST changes
Pacific Time in Canada Saturday 30 May 08:00 -7 Year-round
Eastern Time Saturday 30 May 11:00 -4 Observes DST changes
UTC Saturday 30 May 15:00 0 Year-round
Indian Standard Time Saturday 30 May 20:30 +5.5 Year-round
Indonesian Western Standard Time, Indochina Time Saturday 30 May 22:00 +7 Year-round
Chamorro Time and Vladivostok Time Sunday 31 May 01:00 AM +10 Year-round
Australian Eastern Standard Time Sunday 31 May 01:00 AM +10 Year-round in Queensland, and partial year for other regions

Date and time for the Asia and Pacific-friendly time slot

Table of local times. See also this Zonestamp link, and this external website.
Time zone Day of week Date Local start time UTC offset Daylight savings notes
Hawaii Standard Time Saturday 30 May 19:00 -10 Used year-round in Hawaii
Pacific Time Zone in United States and Mexico Saturday 30 May 22:00 -7 Observes DST changes
Pacific Time in Canada Saturday 30 May 22:00 -7 Year-round
Eastern Time Sunday 31 May 01:00 -4 Observes DST changes
UTC Sunday 31 May 05:00 0 Year-round
Indian Standard Time Sunday 31 May 10:30 +5.5 Year-round
Indonesian Western Standard Time, Indochina Time Sunday 31 May 12:00 +7 Year-round
Chamorro Time and Vladivostok Time Sunday 31 May 15:00 +10 Year-round
Australian Eastern Standard Time Sunday 31 May 15:00 +10 Year-round in Queensland, and partial year for other regions
[edit]

None for this session.

Agenda. This will be an approximately 1 hour Café session, and is extendible for an additional 30 minutes if needed.

[edit]
  • Next steps & closure ← Pine (5 minutes)

How to attend the session

[edit]

If you would like to attend then please sign below at least 1 hour before the start of the session. A Google Meet link will be emailed to you before the start of the session, using Special:EmailUser.

  • If you sign up near or after the start time of the session then the hosts might not have time to send a meeting link to you for the session.
  • Before the scheduled start time of the Café, please verify that you can successfully use Google Meet.
  • Attending the Café requires that the participating Wikimedia account has 500 or more edits on a single wiki with an account that is 30 or more days old (consistent with English Wikipedia's policy for extendedconfirmed group membership), and no active blocks visible in Special:CentralAuth. If your account does not currently meet these requirements then please fulfill these first. After your account meets these requirements, you may sign up for a Café session. Thanks.

Signups for the May 2026 Americas, Africa, and Europe-friendly time slot

[edit]
  1. ↠Pine () 05:32, 21 May 2026 (UTC)[reply]
  2. Chaotic Enby (talk) 20:27, 21 May 2026 (UTC)[reply]
  3. GrimRob 21:08, 24 May 2026 (UTC)[reply]
  4. Not entirely sure I'll be able to make it, but I'll try. —Femke 🐦 (talk) 06:26, 26 May 2026 (UTC)[reply]
  5. Exec8 (talk) 08:17, 26 May 2026 (UTC)[reply]
  6. SCP-2000 09:30, 26 May 2026 (UTC)[reply]
  7. I'm not sure if I'll be free, but signing up. Soni (talk) 19:17, 27 May 2026 (UTC)[reply]
  8. Chlod (say hi!) 03:29, 28 May 2026 (UTC)[reply]
  9. --GPSLeo (talk) 19:42, 29 May 2026 (UTC)[reply]
Ineligible to attend this time
[edit]
  1. Iam-py-test (talk) 22:09, 25 May 2026 (UTC)[reply]
  • Hi @Iam-py-test: thanks for signing up. However, your account is ineligible to attend because it does not have a minimum of 500 edits on a single wiki. You can remedy this before the June session(s) of the Café by meeting the activity minimum and remaining unblocked on all projects. I hope to see you then. ↠Pine () 03:22, 30 May 2026 (UTC)[reply]

Signups for the May 2026 Asia and Pacific-friendly time slot

[edit]
  1. ↠Pine () 05:32, 21 May 2026 (UTC)[reply]
  2. -- Aanchal Patel 🌟 (Archies2804) (🗨️ talk) 19:23, 21 May 2026 (UTC)[reply]
  3. --Johannnes89 (talk) 21:03, 21 May 2026 (UTC)[reply]
  4. Uday Dongre [decodeme] 06:23, 24 May 2026 (UTC)[reply]
  5. I'm not sure if I'll be free, but signing up. Soni (talk) 19:17, 27 May 2026 (UTC)[reply]
  6. I'm not sure if I'll be able to join either but signing up -- Kaartic [talk] 14:25, 28 May 2026 (UTC)[reply]
  7. In theory, I should be around! -- Sohom (talk) 23:17, 30 May 2026 (UTC)[reply]
[edit]

A ping will be created here when links are sent. Hi, links to join the Google Meet sessions have been sent to everyone in the below list. ↠Pine () 03:47, 30 May 2026 (UTC)[reply]

  1. Chaotic Enby
  2. GrimRob
  3. Femke 🐦
  4. Exec8
  5. SCP
  6. Soni
  7. Chlod
  8. GPSLeo
  9. Aanchal Patel 🌟 (Archies2804)
  10. Johannnes89
  11. Uday Dongre
  12. Kaartic
  13. Late addition: sent a link to Sohom Datta before the start of the second meetup. ↠Pine () 06:42, 31 May 2026 (UTC)[reply]

Slide deck & notes

[edit]

Information shared with participants

  • Wikidata: the 2026-2027 plan includes work on replacing SPARQL, which is the query engine for getting Wikidata results in bulk
  • Commons: protection against scrapers: very hard hit on infrastructure downloading media in bulk. Recent change: severe limitation on different image sizes.

Feedback regarding the draft Annual Plan

[edit]
  • How to rank priorities
  • Page weight on comments != how important something is. People may be more vocal about topics which are the subjects of excitement, doubts, complaints, or disagreements. For example, a shortage of comments about a proposal to improve mobile usage experience shouldn't be taken as implying that improving mobile usage experience is a low priority.
  • More emphasis desired in the Annual Plan
  1. Commons rarely mentioned - main concern about reusers not mentioned
  2. Wikidata rarely mentioned - main concern about reusers not mentioned
  3. What happened to the concept of developing a strategic plan specifically for Commons? One possibility: make Commons more Flickr-like.
  1. This relates to the questions about support for rich media/multimedia
  • Mobile
  • Communications
  • Regarding WMF people / teams not listening to / not responding to incoming communications in a timely manner: WMF Movement Comms people possibly stretched across too many teams. Some WMF teams don't have a Movement Comms person. Product managers who don't have sufficient support from WMF Movement Comms sometimes do a good a job with public comms on their own as product managers, and sometimes don't.
  • Deepening engagement
  • Education program - deepening engagement this way? long-term engagement post education-program? What could be done to get students to stay around after completing classes and become long-term contributors?
  • Support for users with extended rights
  1. Comment: Activities in 2025-2026 are making a positive difference.
  • Code review
  1. The issues of patch reviews and code rot were discussed. One possible idea: have a developer advocate (external link to role description) whose job it is to connect un-reviewed patches with the responsible teams. Additionally, work is happening in WMF to align software with teams so that it's clear at least at the team level which WMF team should handle which collections of software.
  • Artificial Intelligence
  1. Reference Check; potential to integrate with the community-specified reliable sources list; see also Cite Unseen
  2. Edit Check
  3. Structured Tasks
  4. See mw:Talk:Contributors/Strategy#Follow-ups on "LLMs in Wikipedia: Investigating How LLMs Impact Participation in Knowledge Communities"
  5. Articles for Creation backlog in English Wikipedia: AFC reviewers are demoralized by the problem of AI-generated low-effort articles. Idea: make visible to AFC reviewers a measure of probability whether AI was used in creating an article, and then people can decide if they want to spend their time reviewing it. Related: the Edit Check feature, and checks for copyright violations. We should considering using even closed-source commercial tools for detecting AI generated text, similar to how WMF has external relationships for wikitech:hCaptcha and mw:Extension:IPInfo.