User:Leucosticte/Sandbox


 * Isn't the ability to make configuration changes already assigned by fiat? The communities currently don't elect anyone to make changes to InitialiseSettings.php or CommonSettings.php. Also, don't sysops already have power to mess up technical stuff, e.g. by editing MediaWiki:Common.css or one of the high-risk templates? If they don't have enough restraint to refrain from changing what they don't understand, especially when it's clearly marked as a potential source of disruption if changed, then they can be de-sysopped. Leucosticte (talk) 05:34, 22 November 2013 (UTC)

The extension should also have a configuration setting that, when enabled, will cause redirects to automatically be created when they are created on Wikipedia. So, suppose there is a John Maynard Keynes article on both Wikipedia and the local wiki. If someone creates a new redirect of John Keynes to John Maynard Keynes on Wikipedia, that same redirect should also be automatically created on the local wiki.

11402: I'm developing the prototype to illustrate the queries for Delete, Undelete, SpecialContributions and SpecialDeletedContributions, as was discussed at the 2013-11-20 RFC review. This prototype uses a new table rather than a new field in the revision table. But maybe we would want to combine the two ideas. There are a few options I'm considering: 1) On undelete, only update the revision rows that need to have rev_page changed (e.g. if the deleted revisions are being added into the page history of a page that's been recreated and therefore has a new page_id). SpecialDeletedContributions would then need to ... 2) On undelete, update rev_deleted in the revision rows being undeleted. One of the bits in the bitfield would need to be reserved to hold this value. Otherwise we would need a new field.