Page MenuHomePhabricator

[Hackathon doc sprint] Lua for Wikimedians
Closed, DeclinedPublic


This is one of the main topics of the Wikidata documentation Sprint during the Wikimedia Hackathon 2017.

Feel free to add in subtasks your ideas of tasks to improve the documentation for Wikimedians who want to use and create Lua modules.

The tasks should be:

  • Simple (you can split complex tasks in several tasks)
  • Clear (please add details, links, explain what's wrong or missing in the existing doc)
  • Ideally, feasible by a team in maximum 1 day

Links to Lua doc (feel free to add more):

Inspirations (nice doc from other projects):

  • ...

Event Timeline

Possibly related to Task T76229 (and, where we would still need some more examples of pure Lua infoboxes. But the page (and talk) page already have gathered a lot of expertise and would be worth expanding.

Just for ideas

Frwiki have pretty cool Lua-infobox system

In fiwiki we have some infoboxes which are using Frwiki's wikidata modules for fetching data and Lua for input validation

Also one use case for wikidata is that we are comparing some infobox and wikidata values and if they matches then then infobox adds a link that "test number N OK" and if they don't then add a link "test number N Failed" and some notification category. There is also abuse filter rule which tracks the changes and if the test results (=links) changes from OK to FAILED and editor is not logged in or just created then it will tag or disallow the change. Most commonly we are testing things like infobox titles, game age limits etc.

Hello! Just letting you know that you can schedule this session now for the hackathon. Instructions and scheduling can be done here:

Is there active work done right now where I could participate as a novice?

Hello @MrSteff, I'm afraid no one is working on this topic right now.
Still, if you want to go through the existing documentation pages, and point out where you find some incoherences, outdated information, or just things you don't understand, it would be very helpful.

Thanks for your reply, I will consider doing so then.

Aklapper added a subscriber: johl.

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)