Difference between revisions of "Software maturity"

From Wiki.OSArch
Line 1: Line 1:
 
[[:Category:Software|Software pages]] in the wiki should include an [[Template:Infobox_software|InfoBox]] with information on an applications maturity. The suggested maturity levels are as follows:
 
[[:Category:Software|Software pages]] in the wiki should include an [[Template:Infobox_software|InfoBox]] with information on an applications maturity. The suggested maturity levels are as follows:
  
[[Category:Mature]]: Software ready for production use. Stable, feature rich and dependable
+
* [[:Category:Mature]]: Software ready for production use. Stable, feature rich and dependable
  
[[Category:Functional]]: Software that works and is unlikely to ruin your workflow. Can be a non-critical part of a production workflow
+
* [[:Category:Functional]]: Software that works and is unlikely to ruin your workflow. Can be a non-critical part of a production workflow
  
[[Category:Promising]]: Software on the way but lacking key functionality or stability. Can supplement a production workflow for testing purposes and gathering feedback for the developers
+
* [[:Category:Promising]]: Software on the way but lacking key functionality or stability. Can supplement a production workflow for testing purposes and gathering feedback for the developers
  
[[Category:Immature]]: Promising software under active development that needs feedback and testing
+
* [[:Category:Immature]]: Promising software under active development that needs feedback and testing
  
[[Category:Concept]]: A proof of concept ready to see more development
+
* [[:Category:Concept]]: A proof of concept ready to see more development

Revision as of 06:25, 25 July 2022

Software pages in the wiki should include an InfoBox with information on an applications maturity. The suggested maturity levels are as follows:

  • Category:Mature: Software ready for production use. Stable, feature rich and dependable
  • Category:Functional: Software that works and is unlikely to ruin your workflow. Can be a non-critical part of a production workflow
  • Category:Promising: Software on the way but lacking key functionality or stability. Can supplement a production workflow for testing purposes and gathering feedback for the developers
  • Category:Immature: Promising software under active development that needs feedback and testing