If you want to start discussing some of these before I get there, go for it!

If you want to start discussing some of these before I get there, go for it!

+

#Delete [[User talk:Kynikos/Dm-crypt with LUKS]] when the restructuring is done

#Ask Pierre to publish LocalSettings.php and include/require there the database connection data from another file, or vice versa publish a LocalSettings2.php that will be required in LocalSettings.php, where only the db connection data are stored (this can help hide the real location of the file with the connection data)

#Ask Pierre to publish LocalSettings.php and include/require there the database connection data from another file, or vice versa publish a LocalSettings2.php that will be required in LocalSettings.php, where only the db connection data are stored (this can help hide the real location of the file with the connection data)

Liberalize the naming of the articles (and categories? but absolutely not templates), and at the same time require that all localized (non-English) articles have the language suffix added to their title, be it translated or not, including redirects

Ideas

Ask Pierre to publish LocalSettings.php and include/require there the database connection data from another file, or vice versa publish a LocalSettings2.php that will be required in LocalSettings.php, where only the db connection data are stored (this can help hide the real location of the file with the connection data)

Templates should be coded so that they are language-neutral, with all their messages coded as {{{msg1|default English message}}}: non-English articles should use meta-templates that simply call the basic template localizing its messages: {{Template|msg1=localized message}}

Template:Pkg and Template:AUR: add a 2nd optional argument for specifying package version (thus keeping link style)? e.g. pacman<=3.5 Maybe just allow to specify an alternative anchor, like it works for normal links: this would even allow bots to replace all direct links with those templates, also when they don't use the package name as the anchor text. Consider creating Template:Pkg search and Template:AUR search for linking to generic searches instead of package pages

Rename code formatting templates to "mi", "mb", "mh"? This would emphasize the fact that they are to be used in general when monospace ("m") is required, possibly not only strictly for code. This would also put them in analogy with <b> and <i> (but would reduce the analogy with <code>)