...
Transition from Maintenance to Archived: A maintenance project can be moved to “Archived" if the project is no more critical for the ONAP Platform (Deployment, Onboarding, Instanstiation, Run-Time) or has any dependecy dependency to any ONAP component.
The following "Termination" steps will be re-initiatied
#1 Ensure that there is
1.1 No more dependency from the 'retired' project candidate to any component
or 1.
...
2 An alternative architecture is identified to replace the 'retired' project candidate by the Architecture Subcommittee or by a dedicated TSC Task Force
PTL to review and to have an integration plan proposal
PTL integration plan to be part of the ONAP roadmap
#2 Update the Architecture diagrams and references
#3 TSC to inform the ONAP Community that the project will no more be maintained and Termination process will be kicked off, promoting the alternative (if any)
#4 In gerrit set the remaining repositories to 'Read Only' access
#5 Verify what (if any) remaining impact the change has on OOM/Integration (CIST)/DOC projects and ensure that is communicated
#6 Remove INFO.yaml
#7 Remove the remaining Jenkins jobs (if any)
#8 Inform Steven Winslow (LFN IP Legal) and disable all the remaining scans (Sonar, FOSSology, NexusIQ) on the remaining repos (if any)
#9 Move project to Project State: Terminated including Clean-up of other wiki pages, RDT, JIRA.
#10 Indicate in the release note that the project is in 'Terminated" state i.e. update the hint in the header.
...
Transition from “Incubation/Mature/Core” to Maintenance
...
#9 Inform Steven Winslow (LFN IP Legal) and disable all the scans (Sonar, FOSSology, NexusIQ) on the unmaintained logging repos
#10 Identify an alternative path (if any)
#11 Move Logging the project to Project State: Archived following the Termination Review process (incl. Maintainance including Clean-up of other wiki pages, RDT, JIRA, mailing lists, calendars, etc.)
#12 Indicate in the release note that the project is in maintenance state i.e. add a hint in the header.
...