Last modified: 2014-11-20 09:17:29 UTC
At brion's suggestion, a lot of site requests should not require the "shell" keyword. For example, logo change requests. This bug tracks bugs that would help get reduce the number of bugs that require the "shell" keyword.
http://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database
From talking to JeLuF, he says he sees these requests most of * Change logo * Change namespace * Add groups * Enable extensions and install initial config * Change config settings for extensions that people forgot to put into the initial config I'll see if I can't come up with separate, reasonable requests for each of these.
(In reply to comment #1) > http://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database > This. We don't need 5 separate solutions to solve this. We need one configuration solution done right.
What's the status of this?
I would still like it, but I haven't had time to spend any time on it. I think Chad's work is probably the best way to go, but I don't think he has much time to work on it.
I'll be tackling this after the git migration, it's on the roadmap for May-ish.
If the configuration were in git as the site itself, it could be handled with gerrit.
(In reply to comment #7) > If the configuration were in git as the site itself, it could be handled with > gerrit. That could also be an option, but I'd still like to see us overhaul how we handle config management in MW.
*** Bug 29863 has been marked as a duplicate of this bug. ***
*** Bug 16595 has been marked as a duplicate of this bug. ***
Changing summary: I got sick of not finding this bug.
(In reply to comment #6) > I'll be tackling this after the git migration, it's on the roadmap for May-ish. What's the status?
(In reply to comment #12) > (In reply to comment #6) > > I'll be tackling this after the git migration, it's on the roadmap for May-ish. > > What's the status? Right now I'm planning to get underway sometime in August. Git/Gerrit has taken much more time than I ever anticipated.
pushing to future since release is imminent.
(In reply to comment #13) > Right now I'm planning to get underway sometime in August. Git/Gerrit has taken > much more time than I ever anticipated. What's the status?
I assume that Chad is too busy with other stuff currently, but it's true that "It has the power to resolve dozens (maybe hundreds?) of bugs." (as MZMcBride said on IRC), and we do have a huge backlog here.
*** Bug 36370 has been marked as a duplicate of this bug. ***
Setting as Normal just to reflect the reality. Feel free to prioritizy as High if/when work starts. PS: found during https://www.mediawiki.org/wiki/Bug_management/Triage/20130307
*** Bug 36857 has been marked as a duplicate of this bug. ***
This will hopefully be discussed at the Architecture Summit: [[mw:Architecture Summit 2014/Configuration]].
The first step of this was merged to core: https://gerrit.wikimedia.org/r/#/c/109266/ The idea is that by using a Config class rather than directly calling globals, it will be easier to later swap the backend to a database/HipHop/whatever . For this to fully work, everything eventually has to use that Config class.
(In reply to comment #22) > For this to fully work, everything eventually has to use that Config class. The API already has a migration patchset :D
