On Sat, Jul 28, 2012 at 9:29 PM, Daniel Friesen lists@nadir-seen-fire.com wrote:
Speaking of Chad. He's been dying to work on his project trying to create a configuration database for MediaWiki. He's been busy with Gerrit stuff but hoping to work on configuration after that's done.
I think that extension management is the second step. We can't have a good system for installing extensions in a UI when we don't even have a good system for configuring MediaWiki in a UI.
Yes. Let's please please please not try to tackle this until config mgmt is in core.
"Extension pages can ONLY exist (excluding subpages) if an extension has been defined in the database, a path to the repo given, and author(s) defined" I see no reason to lock in an Extension: page = part of the repository setup like this. We can provide parser functions and whatnot to display extension information on Extension: pages on MW.org. And we can use some method to use information on the extension base itself to define some information for extensions, etc... but Extension pages and extension management will be two separate things.
This was a silly idea I had when writing this up originally. The main goal was to prevent extensions pasted into wiki pages.
Unless you just mean that new versions of MediaWiki should keep working with old require_once based extensions until they migrate to the extension installer setup.
This.
-Chad