Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Purpose of the Activity

  • Identify which security documentation already exists and where
  • Put everything in one place at least as a reference
  • Identify gaps and fill those
  • Make everything of general relevance available from RTD

Timeline

Initial output for the Guilin release:

  • Central document content version 1
  • Project template version 1 used by x projects


Activity Register

Activity NameDescriptionOwnerCreatedStatus (open, closed)















Proposed structure of security documentation and development

The proposed structure for the security documentation splits responsibilities and sources.

  • SECCOM team to provide principles and guidelines to be followed and a template for the projects to provide the security essentials.
  • Each project can provide more specific information as they see fit
  • Non-documentation sources of ONAP security relevance are referenced/linked

The aim is to make information accessible as easy as possible. All released information will be available from readthedocs (https://docs.onap.org).

The development of content is done in the wiki as collaboration platform. At release time the content is transferred to the readthedocs by means of the scripts provided by the documentation project.

Existing security documentation (02. April 2020)

Meeting Notes and Current State of the Discussion:

  • Meeting from 02. April 2020

  • Meeting from 19. March 2020

  • Meeting from 05. March 2020:



Meeting from 19. March 2020



Open Source Project Documentation Examples:

  • No labels