Extension management 2018 feedback/Upgrading

Identify outdated extensions from a web interface
I would like to be able to identify extensions that have updates available from a web interface. Extensions that have known security issues would be highlighted in some way. Legoktm (talk) 06:00, 16 May 2018 (UTC)

Endorsements

 * Legoktm (talk) 05:21, 16 May 2018 (UTC)
 * Osnard (talk) 15:16, 19 May 2018 (UTC)
 * F.trott (talk) 17:48, 19 May 2018 (UTC)
 * Info-Screen (talk) 13:09, 20 May 2018 (UTC)
 * Smalyshev (WMF) (talk) 00:13, 24 May 2018 (UTC)
 * Cindy.cicalese (talk) 20:50, 3 June 2018 (UTC)

Comments
One concern that was mentioned at the Wikimedia hackathon session on this rfc was that this may end up being a security concern as Special:Version is a public page that would be broadcasting that a particular installation is using out-of-date-extensions.TCipriani (WMF) (talk) 17:52, 19 May 2018 (UTC)
 * I don't think there's any requirement to use Special:Version to provide this interface, or even make it public. It's just that I, as a wiki sysadmin, want some web interface that shows me the status of my extensions. Whether it requires a specific user right or some other access control is an issue for implementation IMO. Legoktm (talk) 18:07, 19 May 2018 (UTC)

Channels to subscribe
There should be channels like,  ,   and. This way the consumer does not have to care about versions. He is just choosing the desired channel and the catalogue provides the appropriate versions. The channel could also be set implicitly, based on the actual version of MW the consumer is using. Osnard (talk) 07:54, 20 May 2018 (UTC)

Endorsements

 * Osnard (talk) 07:54, 20 May 2018 (UTC)
 * Cindy.cicalese (talk) 20:51, 3 June 2018 (UTC)

Comments
...