Extension inventory: Difference between revisions
From Freephile Wiki
clarify roles |
Add intro |
||
| Line 1: | Line 1: | ||
This page serves to inventory and assess the mix of extensions that are in use for the DCS wiki | This page serves to inventory and assess the mix of extensions that are in use for the DCS wiki: | ||
#;Regular: | |||
: Code for "regular" extensions are hosted on Gerrit at the WMF (which is also mirrored to GitHub) with documentation at https://www.mediawiki.org/wiki. | |||
#;DCS Custom: | |||
:Code for the DCS extensions is in the [https://github.com/debtcompliance/mediawiki/tree/master/extensions private Debt Compliance GitHub repo] | |||
#;Organic Design: | |||
: Organic Design extensions are in the [https://github.com/OrganicDesign/extensions/tree/master/MediaWiki 'MediaWiki' tree of the Organic Design GitHub repo]. | |||
{{Highlight| | |||
|Please review with the goal of adding info to the What does it do? column. That would be helpful to understand the function or utility of the extension -- especially as seen from the user perspective. Please note whichever role is involved: '''regular-user''', '''talk-editor''', '''client-admin''', or '''sysop'''.}} | |||
The ultimate goal is two-fold: not only understand 'What does it do?', but also understand related questions like: | |||
* "How critical is it? (Used all the time / occasionally, but still essential / never)" | |||
* "Does it need work? (known bugs or missing functionality)" | |||
* "Can or should this extension be replaced (with a more widely supported "regular" extension) to improve maintainability, features, security and lower cost? | |||
Of course some features or functions are not really "user-centric" but might provide security or other features important to stakeholders like "Owner" or "Developer". For example: The DcsSkin provides a look and feel that is consistent with the company brand and makes the user experience more seamless while navigating between Website / Rails App / Wiki. | |||
I'm going to consolidate the inventory into one table, and probably separate out the lines of code info, but you can add/edit comments at any time. | |||
== File Types == | == File Types == | ||
