> Let's put that number at 95% :-) I don't want to commit the group to
> anything; it's at the top of the short list, but you never know where
> people will want to take the conversation.
> Legoktm, the thing you could do to push it over the top is to write up
> a summary as you see it of the various positions, and post it to this
> list. Ideally, you would also publish it as a subpage of the
> Architecture Summit 2014 page, similar to how some of the others are
> (e.g. HTML templating) Even if we don't get to it at the summit,
> it still will be a very useful backgrounder to have. Is that
> something you'd be willing to chip in with?
MediaWiki is currently configured via a series of global variables
that must be set in a PHP file by a user with file system access. This
cluster of RfCs intends to allow the wiki to be configured using an
on-wiki mechanism. Some of the motivations behind this can be found in
the first RfC.
The first two RfCs, "Configuration database", and "Configuration
database 2" discuss storing configuration parameters in a database
table, while "Json Config pages in wiki" discusses using a JSON
ContentHandler to store configuration options in a wiki page.
Some of these features have already been implemented in extensions:
Configure provides basic on-wiki configuration functionality, and
CentralAuth allows custom global user groups to be created on-wiki.
The EventLogging, UploadWizard, and ZeroRatedMobileAccess extensions
all currently store configuration options in JSON formatted pages.
See also: bug 26992, "Implement configuration database aka
configuration management aka no shell excuse (tracking)"