Wikimedia Developer Summit/2017/Building on Wikimedia services: APIs and Developer Resources

This a main topic discussed at the Wikimedia Developer Summit 2017, facilitated by FIXME (main contact) and ...

The problem
FIXME: problem statement and background information useful for new participants.

This is a collection of ideas related to this topic mentioned in the discussion that led to it. Edits welcome.

How can we better distribute the information on our websites? What data should we make available? How should we offer it? What APIs should we offer to manipulate our content?

How to improve moving data into and out of the wikis (distribution)?

(...) Ensuring that all new business logic is available via the Action API or other externally automatable means. If we could make a collective decision that a SpecialPage must just be a user interface over an API that can be manipulated programmatically both inside and outside of MediaWiki+extensions then we would be turning a corner towards the possibility of radical new user interfaces (single page app, service workers, rich desktop/mobile apps).

This is related to the Developer Experience (DX). The requirements for useful, consistent and well documented web APIs is largely the same as for useful, consistent and well documented PHP service interfaces or useful, consistent and well documented puppet roles for Labs (although the way these requirements will be implemented will of course be completely separate).

Gathering feedback about the usability of the action API. What pain points are there.

Proposals welcome
FIXME: what kind of proposals are you encouraging for the Summit?

Learn more
FIXME: useful links.