In order to facilitate the creation of high quality, secure and compliant open source projects, the Symphony Software Foundation has adopted a 4 stage project lifecycle, shown in the following diagram:
All contributed projects start by going through the contribution process, which ensures the necessary legal requirements are met, while also making contribution as easy as possible.
All newly contributed projects initially land in incubating state, which allows an open project team to form, figure out their collaborative processes, and start to focus on improving the quality of the code towards activation. During this phase, Foundation-hosted projects must use version numbers less than 1.0.0.
Once a project has met the required quality thresholds, the project team can submit it for activation. This involves the Foundation (represented by the Engineering Steering Committee) evaluating the project against a variety of quality & security requirements. Once in this state, the project is able to deploy releases v1.0.0 and beyond.
This is the state where most projects are expected to spend most of their time. It is where the project has achieved a level of maturity and adoption that makes it suitable for widespread production use. The project is actively maintained and enhanced, with new functionality and versions being released at an appropriate cadence. During this phase, Foundation-hosted projects are allowed to start releasing version 1.0.0+ releases.
Projects that are actively maintained, but have achieved a high degree of functional comprehensiveness enter long term maintenance. In this state bugs are still being addressed, but new feature development is not expected.
Projects that are no longer actively maintained may be archived by the Foundation. In this state, issues may not be triaged in a timely fashion (or at all), and almost certainly won't be addressed. The project team may also have disbanded.