Thread:Talk:Requests for comment/Configuration database/Notes from Architecture meetings/Wikimania 2013/reply

Based on my current ideas, I think the answers to your questions are as follows:


 * I think we should use something like JSON. Then it's human readable, easily parsed in PHP, and not something scary like serialized PHP.
 * I think we'll need a back-compat mode for awhile that allows importing/exporting of globals. We've got over 10 years of extension history that we don't want to gratuitously break.
 * Agreed. I think breaking it into concrete steps/phases make it way more likely for this to succeed. For example, here I went ahead and started making configuration more portable.
 * I think it should be opt in, as some config is going to be easier to migrate than others. This is easier with back-compat I mentioned above
 * Once the initial framework is in place, it'll be very easy for any person with commit access to migrate other settings--99% of them will just be copy+replace usages.
 * Agree with this
 * Yeah.
 * I'm paranoid and always figured we'd do whitelisting.
 * especially on backend being pre-req for UI. In theory, once the backend is stable the UI a separate project to start building.
 * I think it makes the most sense to be in Contexts, see my gerrit change linked above