From 6ff42c5544349202ba067aa5fc7caebf4eae38d5 Mon Sep 17 00:00:00 2001 From: Pierre-Yves Chibon Date: Dec 16 2020 14:56:12 +0000 Subject: Document the different maintenance status and level This way we can ask people what the maintenance status and level of an application is with a clear understanding of what each means. Signed-off-by: Pierre-Yves Chibon --- diff --git a/modules/ROOT/pages/glossary.adoc b/modules/ROOT/pages/glossary.adoc index 2e8df89..ffa7fa4 100644 --- a/modules/ROOT/pages/glossary.adoc +++ b/modules/ROOT/pages/glossary.adoc @@ -66,3 +66,45 @@ Waiting on Reporter:: This marks tickets in which a question was asked to Waiting on External:: This marks tickets that are blocked waiting on something or someone outside of the team. + + +== Application categories + +The Fedora Infrastructure runs a fairly larged number of applications. CPE runs +most of them and maintain (as in maintain the code base, writing code and patches) +quite a few of them. +However, not all applications will get the same level of attention from CPE. So +they have been categorized into two maintenance status and two maintenance level. + +Each appliction can then be categorized using these, for example: + +- bodhi is: CPE run and maintain - Critical path +- koji is: CPE run and don't maintain (type a) - Critical path +- waiverdb is: CPE run and don't maintain (type b) - Critical path +- simple-koji-ci is: CPE run and don't maintain (type b) - Not critical path + +=== Maintenance status + +CPE run and maintain:: these are the applications that we run and for which the + team is responsible for the code base. We lead the project upstream and run it + in the infrastructure. If something break, we will look at it and if that + requires patching we will do it. + +CPE run and don't maintain:: these are applications that are running in the + infrastructure but for which we do not write the code base. There are two + types of applications in this sections: + - a) applications that for which we look after the deployment + - b) applications for which other people look after the + deployment, in which case our work can be described as providing "power and pings", + in other words, providing power and network. If something goes wrong, we will + try to restart the service and if the service doesn't recove, we will contact + the maintainers of the application. + +=== Maintenance level + +Critical path:: these are applications that are needed to build or ship one + of our deliverables to our users. + +Not critical path:: these are applications that while important for the + community will not impact the production or delivery of the project's + artifacts.