OpenWetWare:Software/Extensions: Difference between revisions
No edit summary |
|||
Line 19: | Line 19: | ||
**'''[[User:Jasonk|Jasonk]] 22:44, 12 March 2006 (EST)''': I think this extension may end up being critical in order to manage discussions. It will enable each [[OpenWetWare talk:Community Portal|discussion area]] to have recent changes listed. It also enables users to better manage recent changes in areas important to them, something which will be increasingly important as the site scales up. This may be possible via the watchlist, which is the only reason I wouldn't designate this immediately as critical, but I certainly wouldn't call it non-critical yet. | **'''[[User:Jasonk|Jasonk]] 22:44, 12 March 2006 (EST)''': I think this extension may end up being critical in order to manage discussions. It will enable each [[OpenWetWare talk:Community Portal|discussion area]] to have recent changes listed. It also enables users to better manage recent changes in areas important to them, something which will be increasingly important as the site scales up. This may be possible via the watchlist, which is the only reason I wouldn't designate this immediately as critical, but I certainly wouldn't call it non-critical yet. | ||
**'''[[User:Austin|Austin]] 13:27, 13 March 2006 (EST)''': Good point, I actually hadn't thought about using this as an includable page rather than just for each user using it to filter their own recent changes. | **'''[[User:Austin|Austin]] 13:27, 13 March 2006 (EST)''': Good point, I actually hadn't thought about using this as an includable page rather than just for each user using it to filter their own recent changes. | ||
**'''[[User:Bill Flanagan|Bill Flanagan]] 13:27, 11 August 2007 (EST)''': I'm going to look into the extension. If we can create a map that exists as a wiki page that controls the behavior of the filtering, we can isolate at least some of the problems associated with upgrading. Content can be managed independent of the structure. Development can be done by more than one person: the technical details of modifying the code can be separated from the way the site is categorized. This may be more of a meta-goal than a specific outcome but I'll look into it and find out. | |||
* [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] and [http://meta.wikimedia.org/wiki/StringFunctions StringFunctions]: useful for simplifying templates greatly. | * [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] and [http://meta.wikimedia.org/wiki/StringFunctions StringFunctions]: useful for simplifying templates greatly. | ||
Revision as of 05:34, 11 August 2007
Back to Community Portal |
Installed ExtensionsGo to Special:Version to see the definitive list of installed extensions and their versions. See OpenWetWare:Feature test to check that the extensions are working. If you wish to discuss extensions on openwetware, sign up for the mailing list. The following extensions are installed on OpenWetware: Critical ExtensionsCritical extensions are either those which if they break would cause many pages to "break" and as such, these extensions should be considered as important to support (for upgrades, etc). Another way to look at this: if we aren't willing to support these, then we shouldn't encourage people to use these. The known dependencies of these are listed to help in smooth upgrades.
Unknown criticality
Non-critical extensionsNon-critical extensions are defined as those which don't significantly change pages or remove important functionality. Users may use these as they wish and they should be able to easily adapt if we turn them off suddenly.
Deprecated extensionsDo not use these extensions. They may be removed at some point in the future. Desirable or pending extensionsList extensions you would like to install here and vote or de-vote for ones you'd like.
See http://meta.wikimedia.org/wiki/Category:Mediawiki_Extensions for some extensions.
Will not be installed
Writing new extensions or special pages
|