These projects are developed according to the processes described on Development subpage.
Each project has a current maintenance status assigned to it, which doesn't include the maintenance work we do in our volunteering capacity. We review the status at least annually, when the stability of a project changes or interest to refocus on projects has been expressed by the community. We looked at standards for maintenance across other teams to come up with this approach and introduced these 4 maintenance status. To achieve an approach for deciding on the maintenance status of each project, we tried to focus on usage metrics, but also number of contributions to a project in terms of tickets or patches, which we visualised in this dashboard. The idea behind this table is to be fully transparent about our decision making, considering our head count and product focus.
See also the UptimeRobot status of all of our tools.
|Status||Bug triaging||Development||Code review||Further Notes|
|Active Development||Yes with prioritization||Lead by PM with UX resources||Per statement||This is a wish we are currently implementing.|
|Active Maintenance||Yes with prioritization||Bug fixing and small improvements, no new feature requests.||Per statement||We worked on this recently and we will make sure it stays stable.|
|Passive Maintenance||No||Only fixing "Unbreak Now" bugs||Yes but not prioritized||We worked on this a while ago, it is complete work, but we want to make sure it stays running.|
|Unmaintained by CommTech||No||No||No||This means we are still available for advice on talk pages and people can rewish to refocus on this project. When assigning this status it means that the work is complete and there is very little maintenance required. We would like to help you deploy things if you need us. This means we would be happy to assign a maintainer to it, if someone is interested, otherwise we'll try our best to keep it alive.|