It sounds like lots of the previous discussion around this idea has been to do with how to decide which version of an extension to install. But are there details about how the actual installation process will work? That feels like the harder thing, security-wise. There are plenty of other PHP applications that do it (WordPress, Dokuwiki, Matomo…), I'd imagine some ideas could be gained from them.

That sounds fine for third parties, at Wikimedia I think traditional update methods should continue to be used due to the great SysAdmin team that exists, but for novice people or those with little knowledge of complex technical topics it is better to have a Package Manager style on the frontend like Wordpress as @Samwilson mentions and the person receives notifications of stable or unstable updates as is done in other CMS.

I don't think this proposed extension is intended to be used for Wikimedia sites, or probably in any wiki farm situation. It does seem like small simple wikis would benefit from a web-based upgrader.

I would love something like this for Wikibase Suite.

This appears in the MediaWiki master code

[09397088972a30085328fe3b] /wiki/Special:Springboard Error: Class "Html" not found

Backtrace:

from /mediawiki/w/extensions/Springboard/includes/SpecialSpringboard.php(58)
#0 /mediawiki/w/includes/specialpage/SpecialPage.php(734): MediaWiki\Extension\Springboard\SpecialSpringboard->execute()
#1 /mediawiki/w/includes/specialpage/SpecialPageFactory.php(1738): MediaWiki\SpecialPage\SpecialPage->run()
#2 /mediawiki/w/includes/actions/ActionEntryPoint.php(499): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
#3 /mediawiki/w/includes/actions/ActionEntryPoint.php(143): MediaWiki\Actions\ActionEntryPoint->performRequest()
#4 /mediawiki/w/includes/MediaWikiEntryPoint.php(202): MediaWiki\Actions\ActionEntryPoint->execute()
#5 /mediawiki/w/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#6 {main}

Used installed version:
MW core (a8c56cc9ff109698f15a7af3ebaac35f1f586356)
PHP 8.4.6
MariaDB 10.11.11

In T382565#10790137, @Danielyepezgarces wrote:

This appears in the MediaWiki master code

[09397088972a30085328fe3b] /wiki/Special:Springboard Error: Class "Html" not found

Backtrace:

from /mediawiki/w/extensions/Springboard/includes/SpecialSpringboard.php(58)
#0 /mediawiki/w/includes/specialpage/SpecialPage.php(734): MediaWiki\Extension\Springboard\SpecialSpringboard->execute()
#1 /mediawiki/w/includes/specialpage/SpecialPageFactory.php(1738): MediaWiki\SpecialPage\SpecialPage->run()
#2 /mediawiki/w/includes/actions/ActionEntryPoint.php(499): MediaWiki\SpecialPage\SpecialPageFactory->executePath()
#3 /mediawiki/w/includes/actions/ActionEntryPoint.php(143): MediaWiki\Actions\ActionEntryPoint->performRequest()
#4 /mediawiki/w/includes/MediaWikiEntryPoint.php(202): MediaWiki\Actions\ActionEntryPoint->execute()
#5 /mediawiki/w/index.php(58): MediaWiki\MediaWikiEntryPoint->run()
#6 {main}

Used installed version:
MW core (a8c56cc9ff109698f15a7af3ebaac35f1f586356)
PHP 8.4.6
MariaDB 10.11.11

Thank you for pointing it out! It seems we needed a full namespace import for recent versions of MW. We have updated the code and feel free to try out already

I have made a PR on Github correcting said error and it currently works now

We can model an automatic distribution using the Wikimedia Gerrit API to update frequently

@Danielyepezgarces - do you mean, in order to update the revision of each extension/skin automatically? If so, I disagree: part of the promise of this extension is predictability, which is tied in with security - so the revisions used should change (a) infrequently and (b) with some amount of oversight.

El T382565#10797941, @Yaron_Koren escribió:

@Danielyepezgarces - do you mean, in order to update the revision of each extension/skin automatically? If so, I disagree: part of the promise of this extension is predictability, which is tied in with security - so the revisions used should change (a) infrequently and (b) with some amount of oversight.

Well, I'm not saying that it updates automatically every time a commit comes out, but rather that there is an update period, for example, once or twice a month, or if the user prefers to exist when only the branch is changed, for example, between 1_43 and 1_44.

Well, regardless of the update frequency, I still think human review is required for any update - and that's doubly true for a new MediaWiki version, since some extensions take time to support a new version (if they ever do).

Well, for the extensions included in MediaWiki or any made by the WMF staff, this manual review is not required. I'll give you the ones made by third parties.

Leaving the topic aside, I think we need to expand on the topic of localization, regarding buttons and other texts.

I certainly agree with that! There's still a lot of room for improvement.

@Techwizzie: Thanks for participating in the Hackathon! We hope you had a great time.

• If this task was being worked on and resolved at the Hackathon: Please change the task status to resolved via the Add Action... → Change Status dropdown, and make sure that this task has a link to the public codebase.
• If this task is still valid and should stay open: Please add another active project tag to this task, so others can find this task (as likely nobody in the future will look back at the Hackathon workboard when trying to find something they are interested in).
• In case there is nothing else to do for this task, or nobody plans to work on this task anymore: Please set the task status to declined.

Thank you,
Phabricator housekeeping service