Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 54

Project Review Recordings

...

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

Verify 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
3Identify an alternative path (if any)ArcSubCommTSCPTLsArcSubComm, SECCOMJIRA Task update,Weekly status on TSC Meeting
4Identify potential remaining committers to maintain the remaining repositoriesTSCTSCPTLsArcSubComm, SECCOMInfo.yaml to look up, JIRATSC delegationdelgation, JIRA, Gerrit Garret Repo.
5Decision to retire functionality madeTSCTSC
Arc, Sec, PTLsJIRA updateJIRA
6Update INFO.yaml LFN IT


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




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





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




10Inform 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

11Move 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)





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




13The 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




14Any 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?)





...

Transition from "Unmaintained" to "Archived": A Unmaintained project can be moved to “Archived" if the project is no more critical for the ONAP Platform (Deployment, Onboarding, Instantiation, Run-Time) or has any dependency to any ONAP component.

The following "Termination" steps will be performed:

...

  • AAF, APPC, AAI/ESR GUI and AAI/ESR Server, MUSIC (OOF has a dependency on it), Logging incl. Pomba, PORTAL, VID, ExtAPI
  • Repositiories currently in 'Read Only access':  DCAE-D SDC plugin, AAI/Sparky, OOF/FGPS, DCAE/PNDA, OOF-CMSO, Policy-engine
    and
    • sdc/dcae-d/ci
    • sdc/dcae-d/dt
    • sdc/dcae-d/dt-be-main
    • sdc/dcae-d/dt-be-property
    • sdc/dcae-d/fe
    • sdc/dcae-d/rule-engine
    • sdc/dcae-d/tosca-lab

...