User:Annew/AkademyNotes

Notes from Akademy:

• Oxygen skin makes too little use of wider screens
• Languages using more space for translations, will mess up the tabs (solving former, will solve this in some cases). Try Dutch compared to English. The last tab will be displayed just below the tab before that.
• Right to left languages, alignments, etc. There are open issues for this in MediaWiki's bugzilla. Ask Siebrand for more details if relevant.
• For documentation we need to work towards notification of 'more recent version than last exported to distro'. Means that revisions should be taggable with definable tags and trigger a certain (localisable) message to be displayed for page translation pages. (lower prio)
• Have a look at http://translatewiki.net/wiki/Issues_and_features
• Consider activating the Usability toolbar. Consider using the same features as in translatewiki.net, or possible be a little more conservative because this wiki's functionality should be rock solid wherever possible.
• LiquidThreads uses a little older version; trunk is much better, but often unstable revs are put in there. Might want to check with translatewiki.net if there's a stable version, and then update to a particular rev. The version used on UserBase at the moment is a little old and messy particularly in display.
• Siebrand recommends enabling InstantCommons and then you instantly have the 7 million freely licensed media files of Wikimedia Commons at your disposal.
• MediaWiki allows sending out RecentChanges to IRC. Ask Niklas for details if you want this at some point in time. Requires a relay agent.
• Search needs to be better. Consider using Sphinx or MWSearch/Lucene.
• Analyse current content, find out what is English, and needs to be translated
  • Better categorisation
  • Tag outdated content (or move to a different namespace) - create a process for this - or at least document it?
• How to improve they way in/how to allow users to find what they need as soon as possible.
• Add suppressredirect rights for sysops.
• Make search results language dependent (is new to be developed functionality - should probably be its own extension before giving it to the search engine)
• Don't put each language in its own namespace. It'll be a nightmare, because there are too many languages. In the beginning it'll look like a solution. Imagine having 150 namespaces when supporting 67 languages (2x67 because of talk and the 16 or so default ones).