Extension:Scribunto/Deployment priorities

This list is completely unofficial, but it reflects my current thoughts about what the priorities are prior to widespread deployment of Scribunto/Lua to Wikimedia wikis.

Must have

 * Support for Lua in mwlib (Collection extension)
 * (39610) Scribunto should support global module invocations

Should have

 * (39605) Auto-categorize Scribunto module pages that contain errors
 * (39606) Auto-categorize pages containing script errors from Scribunto module invocations
 * (39646) Scribunto needs sane Unicode string support
 * Can use a pure-Lua UTF-8 decoder, like the one in require('luabit/utf8.lua')
 * with support for at least  and   formats; and
 * 280 thousand pages on the English Wikipedia use its w:en:Template:Birth date and age template, and they all expect to be able to obtain the current date in a broken down form so that they can do calendar arithmetic.
 * Other templates also use the current date and time. See w:en:Template:Indian population clock for example.
 * A Lua program should be able to obtain everything that non-Scribunto templates can obtain through.
 * Lots of English Wikipedia templates have default title to name of current page semantics.
 * and
 * Lots of English Wikipedia maintenance templates effectively do the  trick.
 * Of course, these can be done in Lua. But these encoders are used frequently.  The English Wikipedia's citation templates need to URL encode COinS data, for example.  A C implementation would be faster than a Lua one.
 * Same as the encoders above. This is used a lot.
 * and
 * Navigation boxes on the English Wikipedia need these for their "v&middot;d&middot;e" links.
 * and
 * An  equivalent.
 * The English Wikipedia uses this in templates as diverse as w:en:Template:infobox country and w:en:Template:article for deletion/dated.
 * and
 * An  equivalent.
 * The English Wikipedia uses this in templates as diverse as w:en:Template:infobox country and w:en:Template:article for deletion/dated.

Can have

 * (39609) Limit scope of title-based syntax highlighting

Won't have

 * Speed problems!

Deployment following
These dates can be later than the true ones, because they are followed by final users.