User:SamanthaNguyen/Todo


 * Big things to consider possibly doing in the future. (of course these would probably need some discussion beforehand)
 * Some are also small and I just need to get around doing

Today is August 27, 2024

Modules to create

 * Module for Template:Compatibility browser
 * Module for Template:Compatibility PHP
 * Module for on Template:Compatibility DB
 * Module for table on Version lifecycle
 * Module for data on Bundled extensions and skins, this would also help auto-populate the data in Template:Bundled
 * Module for data on Extension default namespaces, for extensions that have migrated to using extension.json

Modules to update

 * Update Module:Extension to do the following:
 * Auto-generate list of authors (possibly have another module that could map author name to wiki page so it'd auto-link)
 * Auto-generate MediaWiki version required
 * (possibly, for maintenance) Auto-add categories to extension pages based on which information is auto-generated:
 * etc.
 * etc.
 * etc.

Templates to create

 * The following warning templates for software support should be created, since this information is important, and also since the same is used across many articles
 * Warning template for dropped support of HHVM
 * Warning template for dropped support of Oracle and MSSQL (see Dropped Oracle MSSQL)
 * Warning template that MediaWiki is currently incompatibile with PHP between 7.4.0 and 7.4.2 (see MediaWiki PHP 7.4.0 to 7.4.2)

Hook template

 * Consolidation
 * Would be great to consolidate Template:ExtensionHook, Template:MediaWikiHook, and a skin hook template (doesn't exist yet, however skins provide their own hooks too).
 * Could be consolidated with a, and "extension", "skin", or "core" could be used.
 * If  equals "extension" or "skin", provide a   parameter to use. Links would automatically work based on the value of.


 * Auto-generated categories
 * These hook templates should have auto-generated categories for maintenance purposes for when certain parameters aren't filled. Such as when the  or   isn't filled, there should be a   (that could also probably be better named). This information is historical info and thus it's important to find which ones need filling their historical info out.


 * More template parameters for version data
 * There should be a  and   parameter to pair with the already existing   and   respectively, to link to those patches based on when they were deprecated/removed.