Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tableenhancer
numberOfFixedRows1
numberOfFixedColumns1


SequenceActionRACIArtifactTool/process
1Final call to the ONAP Community raised by the PTL or by the TSC. (Negative Result for volunteer for succession)TSCTSCPTLs

ArcSubComm

SECCOM

JIRA EPIC(new) Ticket ( highest priority/severity)

JIRA Ticket
2Review what is used by the Community and the dependencies to other components and maintain the repositories that are necessary for the ONAP ComponentsArcSubCommTSCPTLs, SECCOMPTLsJIRA EPIC-Tasks per project-New (Projects Dependency List)JIRA, Nexus, PTL Assigned task updates, Weekly status on TSC Meeting
3Verify what (if any) impact the change has on OOM/Integration (CIST)/DOC projects and ensure that is communicatedArcSubCommTSCPTLs, SECCOM, DOCPTLsJIRA Task update, impact assessment reportJIRA, Weekly status on TSC Meeting
34Identify an alternative path (if any)ArcSubCommTSCPTLsArcSubComm, SECCOMJIRA Task update,Weekly status on TSC Meeting
45Identify potential remaining committers to maintain the remaining repositoriesTSCTSCPTLsArcSubComm, SECCOMInfo.yaml to look up, JIRATSC delgation, JIRA, Gerrit Repo.
56Decision to retire functionality madeTSCTSC
Arc, Sec, PTLsJIRA updateJIRA
67Update INFO.yaml LFN IT


JIRA taskPTL, Commiter, Super Committer, Pam, LF-IT 
78In gerrit set the appropriate repositories that are no longer in use  to 'Read Only' accessLF-IT?




89Update the Architecture diagrams and references  (Need role assignment)





910Remove Jenkins jobs (I think Code scanning and report generation needs to continue until closed and archived)LF-IT?




1011Inform Steven Winslow ( we should create alias as functions may be served by new staff) (LFN IP Legal) and disable all the scans (Sonar, FOSSology, NexusIQ) on the unmaintained repos (I think Code scanning and report generation needs to continue until closed and archived)PgmTSCPTLsArcSubComm, SECCOM

1112Move the project to Unmaintained State Projects including Clean-up of other wiki pages, RDT, JIRA, mailing lists, calendars, etc.(Need role assignment, tis may be multiple actions executed by multiple entities)





1213Indicate in the release note that the project is in Unmaintained state i.e.  add a hint in the header.DOC




1314The project information for this component will no more be branched (i.e. master) and will be linked to the latest maintained release. (how would it impact CI tools?)LF-IT, Integration, Release Mgt




1415Any 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.  Can this be mentioned in the Release notes?  if yes, who owns the risk?  TSC?, SECCOM?)






...