Wikifunctions:Status updates/2025-04-05

As with the previous Quarters, we are publishing our plan for the upcoming Quarter to make our work more transparent.

• (T390543) If we establish and meet performance standards, we can have confidence that rolling out Wikifunctions access to more wikis will not disrupt those wikis' experiences or colleagues' work
  • (T390548) Establish an SLO for the Wikifunctions integration into Wikimedia projects' wikitext pages, to assure reader experience quality is maintained during roll-out
  • (T390549) Implement Object and Wikidata entity caching mechanisms in the function-orchestrator to drive up user experienced performance when making function calls
  • (T390550) Implement Object and Wikidata entity batching mechanisms in the function-orchestrator to drive up user experienced performance when making function calls and reduce load on production wikis
• (T390544) If we roll out Wikifunctions access to more Wikimedia wikis, we will see wider use to deliver content and learn how well it works with different languages and communities to address content gaps
  • (T390551) Make embedded Wikifunctions available in at least five more Wikimedia projects, to learn from other languages and communities
  • (T390552) Listen to feedback from the pilot Dagbani Wikipedia community and adapt features, so that we can identify blockers  to further rollout, and increase value to editors and readers, and so help the community
• (T390545) Improve features related to the Wikifunctions integration, so that wiki editors can use Wikifunctions in articles with more confidence.
  • (T390553) Support default values when fields are left blank for date inputs in the Wikifunctions integration so that editors can use it more simply
  • (T390554) Show read-mode errors from the Wikifunctions integration inline rather than in a box, so that editors can be less disrupted when something is wrong
  • (T390555) Show a preview of the function call result in the Wikifunctions integration dialog, so that editors can adjust their uses more swiftly
  • (T390557) Display the local and cross-wiki pages on which a Function is used, so that Wikifunctions users can see the impact of their changes
• (T390546) Extend features to use Wikidata items more fluently, so that Wikifunctions editors can do more things and so address content gaps more readily.
  • (T390558) Support a light-weight enum Type alternative in the Wikifunctions front-end and in the Wikifunctions integration so that editors can use them more easily
  • (T390559) Extend support for Wikidata items to cover unitful values and other types, so that function creators can take advantage of more of the content features of Wikidata
  • (T390560) Improve the performance in the Wikifunctions front-end, so that function creators and users can use complex and large Objects such as those from Wikidata without difficulty
• (T390547) Build plans in the Abstract Wikipedia team on how to address common concerns and proposed feature expansions, so that we can be prepared for taking this on in future.
  • (T390561) Experiment with how we might support rich content as output, including in the Wikifunctions integration, so that we can see how to support future use cases. Develop a plan based on this.
  • (T390563) Develop a plan for how we might support macro-languages like Chinese, so that we can see how to support them as groups in future
  • (T390564) Discuss with the Wikifunctions community and others where we might host Abstract Content in the future, so that we can prepare for that work

On top of the above planned work, we'll also have some "essential work", where we respond to bug fixes and emergency situations following our standard protocols, aimed at reducing disruption for the Wikifunctions community and its users.

We previously set out our plan for the "Q3" Quarter, January–March 2025, at the start, and we'll report on how that went next week.

The Abstract Wikipedia team is looking for a Senior Product Manager to work with us. The Senior Product Manager is accountable for turning the vision of Abstract Wikipedia into a tangible impact. This is a one-of-a-kind opportunity to build the future of the Internet and radically expand access to free knowledge. You will be working on an international team. More information, such as the countries we are hiring in and a list of requirements, can be found on Greenhouse.

As stated above, last week was our last of Q3. The biggest of those pieces of work was the Wikipedia integration, to make it possible to embed Wikifunctions calls in Wikipedia articles (and other Wikimedia wikis). (T383106).

We're getting close with our work on this, and have been making some near-final changes whilst waiting for system support work to land upstream, lots of which landed for release this week. We added not-yet-enabled support for a new DOM syntax for how Wikifunctions calls will appear in the page HTML (T373253). In the search system, we tweaked the display of results from Wikifunctions when the descriptions are too long (T387362). We've added support for Type inputs that have read functions, like natural numbers (T387371). We've provided a special icon to represent Function calls for use in the editing tools (T388563), and a colourful version of the Wikifunctions logo for the editing dialog, as it's so more readable (T387372). We aligned the display of labels, aliases, and short descriptions with the expectations from, and the design shown to, various community members (T387361). Finally, we added some unit tests for all this new code (T387560).

Outside of the Quarterly work, we fixed a bunch of bugs and minor irritations. We switched our localisation code to use the translatable message for ':' rather than hard-coding it, as it's over-ridden in some languages (T385710). We fixed a bug that meant that sometimes we passed an incomplete value as an argument into a Function call (T360580). We now remove the trailing ?success=true entry in the page URL when you publish an edit (T389076). We adjusted the styling of labels in the list of Test cases associated with an Implementation so they don't over-flow the box (T388794). We fixed the styling for the collapsible chevron which wrongly expanded size when you clicked into a Type selector (T387204). We fixed a bug in the pre-publishing transformation code to avoid saving empty booleans in Z3K4s, which we think might be causing wider issues (T390149).

Next week, on Monday, 7 April 2025, at 17:30 UTC, we will have our monthly Volunteers’ Corner. Unless you have many questions, we will follow our usual agenda, of giving updates on the upcoming plans and recent activities, having plenty of time and space for your questions, and building a Function together. Looking forward to seeing you online on Monday!

This week we had 33 new functions. Here is a list of functions with implementations and passing tests to get a taste of what functions have been created. Thanks everybody for contributing!

• statement has value type string? (Z23513)
• value type of statement (Z23516)
• is undulating number (Z23523)
• statement has value type QID? (Z23528)
• statement has value type Lexeme ID? (Z23531)
• statement has value type LFID? (Z23534)
• statement has value type LSID? (Z23537)
• predicate is P31 (Z23540)
• item is instance of these items (references) (Z23543)
• identity value of Kleenean object (Z23558)
• is ISBN-13 (Z23561)
• not in (Z23568)
• object inequality (Z23578)
• identity of Floating point special value (Z23588)
• is Wikidata reference to Roman day? (Z23592)
• is Wikidata day of the week within a given month (Z23596)
• is Wikidata reference of day relative to Easter (Z23600)
• plural Lexeme forms for a Wikidata Item (Z23604)
• flatten Typed list (Z23606)
• lexeme forms representing item (Z23610)
• Lexemes from Wikidata item reference (Z23616)

A complete list of all functions sorted by when they were created is available.