Extension management 2018 feedback/Finding

Extensions that have passed a security review should be searchable
I typically browse through mediawiki.org to find extensions to install. I'd like to be able to narrow my search results to extensions that have passed a security review. Legoktm (talk) 06:04, 16 May 2018 (UTC)

Endorsements

 * Legoktm (talk) 05:21, 16 May 2018 (UTC)

Central catalogue to enable automatic installation
There should be a central catalogue accessible by tools (API) to enable automatic installation. Entries should (besides name and description of extension) comprise installation mechanism (tar ball, git, composer, ...) and download location (gerrit, github, packagist, ...). The catalogue to be used should be configurable in MW to enable other organisations to curate their own catalogues. F.trott (talk) 08:12, 17 May 2018 (UTC)

Endorsements

 * F.trott (talk) 08:12, 17 May 2018 (UTC)
 * +1 Jonas Kress (WMDE) (talk) 09:29, 17 May 2018 (UTC)

Comments

 * Are you're asking for is something similar to the ExtensionDistributor API? But that it would automatically download and install it? Legoktm (talk) 17:33, 18 May 2018 (UTC)
 * Not really. I don't need a service to download stuff. I'd just like a catalogue that an external tool (e.g. an Extension Manager) could access. Also ExtensionDistributor has several shortcomings: It only supports one source (gerrit), it only supports git dumps, it requires from extensions to maintain versions per MW REL branch. (As far as I remember, which may be outdated. It's off topic, but if there is an easy approach to teach ExtensionDistributor to do any of the following I would be happy for links: load versions according to semver; load something else than git-dumps from gerrit; at least run build scripts before tar-balling.)