On 16/02/13 07:55, Steven Walling wrote:
I didn't see it in the docs above, so thought
I'd ask... Is this going
to include rollout of the CodeEditor extension, or will that be done
separately?
CodeEditor will be enabled, but with $wgCodeEditorEnableCore = false,
i.e. in the Module namespace only, not in the MediaWiki namespace.
This is the same way we deployed it to
mediawiki.org
As I said to Ori when he asked me about this: I'm fine with it being
deployed with $wgCodeEditorEnableCore = true, I just don't want to
have to project manage it, since large JS apps are not the sort of
thing I usually do. With $wgCodeEditorEnableCore = true, it's a fairly
disruptive extension, so it would be good to have someone handling
community notifications and bug reports.
This is exciting! Do we have plans for further
measurement when it
comes to Lua's impact on page load times/publishing any results so
far? In addition to the general benefit of not having to program using
wikitext/parser functions, I seem to remember the performance
improvements being the big selling point of Scribunto.
It will be possible to gather some retrospective data from slow-parse.log.
-- Tim Starling