	Action	Responsible	Accountable	Consulted	Informed	Artifact	Tool/process
1	Final call to the ONAP Community raised by the PTL or by the TSC or TSC-Delegate. (Negative Result for volunteer for succession results in following steps).	PTL	TSC	PTLs	ArcSubComm SECCOM	JIRA EPIC(new) Ticket ( highest priority/severity)	ONAP TSC JIRA Ticket (TSC on update CC)
2	Review what is used by the Community and the dependencies to other components and maintain the repositories that are necessary for the ONAP Components	ArcSubComm	TSC	PTLs, SECCOM	PTLs	JIRA EPIC-Tasks per project-New (Projects Dependency List)	ONAP JIRA, Nexus, PTL Assigned task updates, Weekly status on TSC Meeting
3	Verify what (if any) impact the change has on OOM/Integration (CIST)/DOC projects and ensure that is communicated	ArcSubComm	TSC	PTLs, SECCOM, DOC	PTLs	JIRA Task update, impact assessment report	ONAP JIRA, Weekly status on TSC Meeting
4	If the repo(s) are still required, then Identify an alternative path (if any)	ArcSubComm	TSC	PTLs	ArcSubComm, SECCOM	JIRA Task update,	Weekly status on TSC Meeting
5	Identify potential remaining committers to maintain the remaining repositories.	TSC	TSC	PTLs	ArcSubComm, SECCOM	Info.yaml to look up, JIRA	TSC delgation, ONAP JIRA, Gerrit Repo.
6	Make functionality retirement decision	TSC	TSC	ArchSubComm, SECCOM	Arc, Sec, PTLs	JIRA update LFN IT Jira issue for updating INFO.yaml	ONAP JIRA LF IT JIRA
7	Update INFO.yaml with TBD (define fields, etc.)	PTL, Contributor (if available), LF IT	TSC	None	ArcSubComm, SECCOM, PTLs	JIRA task	PTL, Committer, Super Committer, LF-IT, LF IT JIRA
8	In gerrit set the appropriate repositories that are no longer in use to 'Read Only' access	PTL (make request if available), LF-IT	PTL TSC (if no PTL)	None	ArcSubComm, SECCOM, PTL (if available) TSC	ONAP JIRA, LF IT JIRA	ONAP JIRA, LF IT JIRA, gerrit, github
9	Update the Architecture diagrams and references (Confluence)	ArchSubComm	TSC	None	Doc, ArcSubComm, SECCOM, PTL (if available)	ONAP JIRA, wiki	ONAP JIRA, confluence
10	Update the Architecture diagrams and references (readthedocs)	Doc	TSC	ArcSubComm	None	readthedocs	readthedocs
11	Indicate in the release note that the project is in Unmaintained state i.e. add a hint in the header.	PTL	TSC	None	None	User Docs, Release Notes	ONAP JIRA Updates, WIKI, ONAP.read the docs
12	Remove Jenkins jobs (I think Code scanning and report generation needs to continue until closed and archived)	PTL (make request if available), LF-IT	TSC	None	PTL (if available)	JJBs	Jenkins
13	Move the project to Unmaintained State Projects including Clean-up of other wiki pages, RDT, JIRA, mailing lists, calendars, etc.	Project Management & its delegate	TSC	None	None	JIRA Tickets Updates	JIRA ONAP, JIRA LF-IT
14	The project information for this component will no longer be branched (i.e. master) and will be linked to final maintained release_XXX. (LF-IT to adjudicate changes to CI tools)	LF-IT, Integration, Release Mgt	TSC	ArchSubComm	SECCOM	email	ONPA JIRA, LF-IT JIRA Updates
15	Note: the following applies only if the project or component is reintroduced to a release after being archived. Any critical, severe or high vulnerability found in the code written by the project team MUST be fixed within 60 days or prior to the inclusion of the project in a new release, whichever occurs first. (This can not be done due to lack of resources. 1) If committers are still around, provide a fix 2) If the fix is not possible, open CVE, and Update release notes	TSC, SECCOM, Documentation	TSC	PTLs, Committers (volunteer PTLs)	ArchSubCom, Documentation	Conf Calls, email	CVE, Documentation, ONAP JIRA, LF-IT JIRA.

Browser not supported