MediaWiki Stakeholders' Group/Tasks/Feature wishlist/2015 assessment

This is a list of features commonly and widely requested by non-WMF users.

Release policy

 * Stable releases that don't break anything during/after upgrading.
 * That the distribution and extensions etc. take into account that small wikis using economical hosting might have only restricted access to the shell, e.g. they can't use git, nor make.
 * MediaWiki as framework: Standardized interfaces in MediaWiki for different solutions or distributions (documentation, translation, public wikis … SMW)

Rights management

 * Access Control List, compare Grants:IdeaLab/A place to work together
 * HaloACL testing, documentation and avoiding patching in future. How to get MediaWiki.org to keep things in core that we need for HaloACL. New HaloACL GitRepository
 * Include a way to moderate/sandbox new users as an anti-spam measure, or have a way to approve genuine new users. For example a slimmed down mw:Extension:ConfirmAccount, where it only asks "Hello, please tell us briefly about yourself and why you'd like to edit this wiki?". Currently any new non-WMF wiki is unexpectedly left open to spambots.

Template management
Templates provide a lot to a wiki. However most non-WMF wikis make very little if any use of templates. The user wants a wiki they can install and then just get on with using. Templates are unwanted extra work. Having to learn how to write and debug templates, Lua, etc. to make use of them is too much to ask for – that's not what the end user wants to be doing. Templates transcluding templates is confusing. Sometimes to get around this non-WMF wikis export templates from Wikipedia and then their users wonder why bits of Wikipedia (redlinks, context, logos etc.) are appearing in the other wiki. Also the imported pages may be without attribution, especially if the export included all the other transcluded pages.
 * A repository for templates and dependencies, e.g. Scribunto modules, Lua modules, JavaScript, CSS, etc. Otherwise non-WMF wikis have to export/import and debug, these from wikipedia. Making a mess of the wiki with unwanted Wikipedia specific bits. See bug 64475
 * Templates on WMF sites themselves differ between sites

Extension management

 * SMW documentation, power it by an SMW instance: show showcase of updated smw.referata.com
 * Installing extension as easy as in wordpress
 * SMW: Extension repository: Drupal/Wordpress: browse for plugins/extension, click on “install” or “upgrade”
 * precondition: extensions moved to composer? requires detailed analysis
 * what about “uninstall” - solved with 1)
 * deactivate vs. uninstall
 * where to put code/documentation: clear guidelines for developers: github used by many) or gerrit (official, with translatewiki support). mirroring how to do this, needs to be documented, ask Jeroen). move from gerrit to phabricator?
 * directions on how to update existing extensions
 * Easy extension maintenance/updating, not having to check the status of each extension at every upgrade

Specific ideas for extensions

 * A calender management system to use different calender systems.
 * An improved pdf handler.
 * Upload of Office documents (docx etc.). Security issue. Needs changes in MW core. (see |talk page discussion)
 * A way to automatically archive any new external link to e.g. WebCite or archive.today. For citations with link rot to be repointed to the archived copy.
 * A way to scan through all external links and to offer repointing any failed ones to a new URL, e.g. if necessary to Archive.org. (see Extension:ExternalLinks)
 * Install extension VisualEditor along with Parsoid easily.
 * Interwiki links to other wikis.
 * Trackbacks to other wikis and sources
 * Support and maintain the obsolete Extension:WikiTeX or something more user friendly. So that users can illustrate articles, in a consistent style, without having to make much more effort than regular editing. For example: graphs, plots, flowcharts, venn diagrams, structural formula for chemical compounds, circuit diagrams, musical scores, etc.
 * Widgets as in Wordpress: More functionalities in menus (left, header, footer or in another menubars) like integration images, Facebook, iCal etc.
 * Creating an article with an infobox. Lists wherever about the subject should automatically update with the data from the infobox. The page itself should be automatically inserted into the relevent navboxes.

Gadgets management

 * A repository for JavaScript gadgets, (and other bits and pieces?) but separate from templates and extensions

Skin management

 * [//semantic-mediawiki.org/wiki/Help:Skins Skins known to work well with Semantic MediaWiki].
 * Skinning is a MW topic, but it is a mess, MW:[//www.mediawiki.org/wiki/Category:Skinning Category:Skinning]
 * Standardized interfaces in MediaWiki skins for the integration of new functions without customizing the skin.

Marketing tools and user support

 * Places for brochures, promotion videos and screencasts and project descriptions
 * Navigable user support, i.e. easy to find solutions. Currently there are multiple routes to use, Bugzilla, MediaWiki-l mailing list, talk pages, Project:Support desk, etc. Compare Wikimedia technical search.
 * Ways to encourage users to register and contribute to the wiki, e.g. wysiwyg editing, social networking, rewarding user contributions by keeping a score/rank, etc.
 * Talent pool, central resource for technical writers, illustrators, coders, etc. to offer their services, free or paid, to work on wikis. MediaWiki vendors?

Admin tools
Tools like, for example:
 * AutoWikiBrowser, already available
 * WPCleaner
 * Check Wikipedia
 * autoFormatter

Metawiki

 * MediaWiki Feature Request (Archive)

MediaWiki.org

 * Enterprise hub, wikis for corporate (or organizational) context
 * Academic hub, wikis for academia
 * Bundling, for some users it's preferable to get MediaWiki up and running with a software bundle. E.g. MediaWiki4Intranet

Semantic-mediawiki.org

 * SMWCon Fall 2014/Create camp
 * Planned Features for SMW (2012)