T30856 removes the 2006 wikitext editor from the MediaWiki Core. That would mean that users would get no toolbar at all without the WikiEditor extension. We propose that the WikiEditor extension be merged into the MediaWiki Core.
|Open||None||T209217 Enable WikiEditor by default in new installs of the MediaWiki bundle|
|Open||Feature||None||T55983 Select checkboxes for bundled extensions by default|
Do you want ‘install it by default’, maybe? Merging a specific extension into core would just bring the same problems with regards to old toolbar.
IIRC, it already goes in standard MediaWiki bundle, but not sure if it’s installed with it.
If you want to do is having it included in core I don't think it would be a good idea. To be honest, I rather have MediaWiki core without specific editors (only the text area) and have the possibility to install whatever editor I want just installing it as a extension. That's the simplest way to customize a wiki to the needs of most of the people.
Proposing to decline this task: Users would get no toolbar at all without the WikiEditor extension, but if users don't have the WikIEditor extension then it is because their administrators actively removed/disabled WikiEditor.
Is that actually true? I think you still have to specifically enable it in the installer, and if you click fast install, the option is skipped.
I'd support having some of the bundled extensions (like this one) installed by default, where admins have to specifically unclick it, instead of opting out. (But I definitely do not support doing that for all extensions)
I think declining this is pretty premature. This has been proposed in other places like https://www.mediawiki.org/wiki/Suggestions_for_extensions_to_be_integrated#WikiEditor (no opposition, though no additional support either), and there have been comments like T30856#339558 suggesting it be moved into core as well.
More importantly, are there any legitimate arguments for MediaWiki to ship without a default enabled toolbar? Extensions are well, extensions. They should not implement what we consider to be core functionality.
I don't find arguments like T209217#4737133 convincing because customization is still possible, even if WikiEditor is in core.
What problems exactly? My understanding is that the "classic toolbar" was removed for maintenance reasons. Given that we have to maintain WikiEditor one way or another, where it lives is less consequential.
I was mainly thinking about over-reliance on one editor’s APIs that sprung up in multiple Wikimedia projects after removing classic edit toolbar from the core. I don’t really have an opinion about extension vs core and I’d support having WikiEditor enabled by default, but after tensions arising from Wikimedia projects using very old code that was attached to the specific editor, it seems strange to merge another editor into the core only to deprecate and remove its APIs once again after 2017 wikitext editor or 2020 voice command editor etc. come along.
The situation is very similar to skins. Actually, while you can use MediaWiki without any toolbar, you can't use it without any skin. And yet MediaWiki core comes without any skin, you have to install at least one (skin-) extension to get a functional wiki.
So obviously having vital components in extensions included in the default bundle instead of core has been working for years without any apparent problems, so why should it be problematic to do the same with the toolbar?
I also agree with stjn's previous comment: If you insist on having the "standard" toolbar to be included in core, sooner or later you will have to merge VisualEditor into core, or some other more advanced successor (though in my nor completely serious predictions from 5 years ago I scheduled the voice input editor only for 2026, not for 2020).
Lego, don't you think that the same lifecycle problems that affect the 2006WTE will also apply to – well, every single editing environment? Does anyone really think that WikiEditor will actually be used forever?
I think that "where it lives" has consequences for some MediaWiki users. IMO editing environments should be "plug and play". They should not be "core". You should pick out the ones that you want for your wikis, and not be required to install the ones that you don't want. As I was reminded today, there are third-party wikis that use MediaWiki, but that don't use WikiEditor (e.g., Shoutwiki). Is there any good reason to force them to install WikiEditor?
Also – I'm not actually going to say that you MediaWiki devs are anything less than perfect ;-) but at least some devs do seem to be human. If it's in core, then some humans may be tempted to write sloppy code that assumes that the editing environment will be there forever. Those "but it's in core, so I don't need to bother with..." bits were why it took so long to disentangle the 2006WTE from core. Let's not set ourselves up for that mess again.
We intentionally removed the toolbar from core with the plan to let core work by default as plainly as possible (basic, but functional). The idea of merging WikiEditor has come up in the past more than once, and as far as I know, nothing has changed since with regards to factors that led us to the decision to not merge. As such, I think we should re-affirm that here as well.
having said that, I very much agree that the usability of the web installer needs work. In particular with regards to bundled extensions being enabled by default.
I believe fixing this UI aspect from the web-based installer would solve the underlying use case for which @GeoffreyT2000 opened the task.
We could repurpose this task for that issue, or re-close and track separately.