Unlike in the case of mediawiki extensions, where the extension code is packaged as a tarball to be installed in end user's environment, there is no immediate idea of how to package the Query Service (in particular as it actually involves a number of software components).
Components included Query Service backend (including the WMF Blazegraph fork), and Query Service UI.
Should those be bundled as separate tarballs? Or as a single one?
Acceptance criteria
- Decision on how tarball release artifact for Query Service components will be composed has been documented as an ADR in https://github.com/wmde/wikibase-release-prototype