User:Waldyrious

Waldir@meta.wikimedia

Projects

 * Mediawiki documentation (especially reference, index-like ones)
 * Potential bugs for hacking sessions
 * Plans/notes of my participation in Wikimedia Hackatons
 * tools:~waldir
 * Moving mediawiki documentation from meta to mediawiki.org

Installation

 * ,, (Manual:install.php), Manual:Installation guide,
 * Using maintenance/install.php (todo: test and make sure of the parameters; add some documentation to the file and its Manual entry):
 * note: for now the  parameter needs to be explicitly set for this to work out of the box. 133222 addresses this.
 * todo: allow password not to be set in the command line, and get a prompt instead
 * todo: fix timezone issue w/ installer.php. In both cases the default time zone of the wiki is not correct (it either is set to UTC or doesn't take DST into account), but in the installer.php-generated wiki trying to edit the main page gets an edit conflict because the new edit uses the actual local timezone and the history uses the server timezone (one hour later, in my case). Both LocalSettings.php are identical, however...
 * See also: MediaWiki-Vagrant
 * https://bitnami.com/stack/mediawiki
 * See also: MediaWiki-Vagrant
 * https://bitnami.com/stack/mediawiki

Skins

 * Overview of existing documentation
 * Collect all skin-related links from mediawiki.org, meta, en.wikipedia, the source code, etc.
 * Summarize each link
 * Complete the first draft of the proposed manual in the "proposed overview" section
 * Request review of the overview, for correctness. Potential people to contact for this:
 * Matma Rex restored one of the old skins (Cologne Blue) to make it conform to the modern system based on templates
 * Ryan Lane has fixed up the strapping-mediawiki skin
 * Daniel Friesen has written quite a bit about the skin system
 * Trevor Parscal was, I believe, one of the main people involved in creating Vector
 * Krinkle seems to be quite knowledgeable about how skins work, judging from some of his comments to Gerrit patches I've seen
 * Jack Phoenix (see here)
 * Liangent (suggested by Sumana)
 * My CSS tweaks: notes at meta:User talk:Waldir/global.css, code at meta:User:Waldir/vector.css
 * Wouldn't it be great if mediawiki was like the CSS Zen Garden? Then skins would be only a CSS file. Why isn't this possible? Maybe when there's support for recent CSS features for layout manipulation, such as flex, grid (note: grid is still a long way to come), move-to (browser compat)), order (see also)?
 * Skeuomorph styles:
 * http://css2less.cc (archive)
 * New skins system
 * Requests for comment/Redo skin framework
 * Bug 27292 - Skinning system improvement (tracking)
 * Bug 27292 - Skinning system improvement (tracking)

Useful stuff

 * Writing an extension for deployment
 * http://shorturls.redwerks.org (see Manual:Short URL)
 * Manual:JS/API/UI Extension Developer Library
 * Git/TLDR and PHPunit/TLDR
 * investigate withJS url param (possibly only enabled in commons, i.e. not a mediawiki feature)
 * Lua: slideshow, tutorial
 * Check commons:MediaWiki:Gadget-Hotcatcheck.js (also Cat-a-lot) for direct, non-refresh, no-edit-view editing
 * patch that enabled direct linking to diffs: 63395
 * Help:CirrusSearch for documentation on search operators/prefixes.

API + Javascript

 * API:Client code (JsMwApi looks interesting)
 * API:Data formats and Manual:Ajax
 * Bug 20814 (fixed) - Enable $wgCrossSiteAJAXdomains for wikimedia sites (only WMF wikis allowed to make AJAX requests to each other)
 * 19907 -- "For non-credentialed requests, we can send Allow-Origin: *" -- i.e., for actions that don't require login, allow third-party apps
 * Could Cross-document messaging help here?
 * Thread:Talk:Requests for comment/API Future/CORS and third-party web apps
 * bug 62807 - Create TODO list for best MediaWiki API client library in JavaScript

Developers

 * Developers/Accounts
 * Special:Code/MediaWiki/author
 * http://toolserver.org/~krinkle/TSUsers.php
 * http://toolserver.org/~krinkle/wikimedia-svn-users.php
 * http://korma.wmflabs.org/browser/contributors.html

Misc.

 * WikiOverflow (abandoned), Wikis@StackExchange & MediaWiki IdeaTorrent
 * Pitch wysihtml5 (also check for similar stuff?) against VisualEditor and suggest improvements to both
 * It could be interesting to make diffs flattrable. See Extension:Flattr.
 * For code review in gerrit, it would be nice to have a query url that shows only changes that haven't been reviewed before (in the "my changes" view, the CR column is often empty but there's already been a lot of discussion before, but a new patch reset the CR scores). Something like https://gerrit.wikimedia.org/r/#/q/reviewer:self+status:open+-is:reviewed,n,z should work, but according to the docs it covers both Code-Review and Verified scores, and the latter is pretty much always there as it's added by Jenkins, so the query shows nothing. One can build a query to show specifically patchsets with no Code-Review score, but that still doesn't fix the "previous discussion" issue above, which would enable one to find patchsets that haven't received any external feedback since being submitted. As an alternative to find unloved patches, one can amend that search query to show patchsets whithout CR that are over a year old (there are four such ones at the time of writing). Another approach is to limit to those who don't have a +2'er in the reviwers, by using -reviewerin:mediawiki in the query (the docs say reviewerin matches changes that have been, or need to be, reviewed by a user in the specified group).
 * Update: Krinkle on IRC says: the gerrit query command line API over ssh might have a way to filter for such things. Ask hashar or Reedy maybe next time they're on.
 * History of MediaWiki version control (see also MediaWiki history and Git/Conversion). Commits graph @ Ohloh. Commits graph @ GitHub (empty before 2009-11-14 although the graph does go all the way back to 2003-04-13, how come?).
 * It would be nice to remove the site subtitle (by default) from the html page title, as well as use use  to enclose the site name, e.g. "Foo [Wikipedia]" instead of "Foo - Wikipedia, the free encyclopedia". This would make titles shorter, and would indicate the site name more intuitively. The fact that the square brackets aren't allowed in page titles also helps ensure no ambiguity is present.