TABLE OF CONTENTS

...

DeveloperWiki and ReadTheDocs Usage Policy

The TSC Vote (2020, Feb. 19) approved the folowing Wiki/RTD usage policy:

DEVELOPER WIKI: for ONAP release, project, subcommitee and development related content, e.g.

• project management (meetings, plans, milestones, members, ...)
• project specific development guides
• ongoing activities and discussions
• ONAP community event documentation

READ THE DOCS: for all formal ONAP E2E and component documentation, e.g.

• ONAP overview, architecture, API
• ONAP developer guides (e.g. Documentation guide)
• ONAP user guides (E2E)
• ONAP component guides, release notes
• ONAP administration/operations guides
• ONAP use-case description and usage
• ONAP tutorials
• ONAP release notes

...

Follow the described steps if you need to migrate DeveloperWiki content to ReadTheDocs:

Read the "DeveloperWiki and ReadTheDocs Usage Policy"

• To understand the reason behind this migration task and to know what DeveloperWiki content we are targeting it is essential to read and understand the TSC approved policy.

Identify formal ONAP documentation content in the DeveloperWiki

• Identify formal ONAP documentation content in the DeveloperWiki which has to be migrated to ReadTheDocs in accordance to the above policy.
• Ensure that the content is valid for the latest release of ONAP. If not, please update documentation accordingly.
• In case of deprecated content, continue with the step Label the DeveloperWiki page(s) as "Migrated to ReadTheDocs" or "Deprecated Content"

Label the DeveloperWiki page(s) to show the "Migration to ReadTheDocs in Progress"

• Example: Migration in Progress

...

• Add/change information about what content is currently migrated (page title) and who does it (your name). Edit this page at section "DeveloperWiki Content - To be evaluated / Currently under evaluation".
• Create a Jira ticket for this activity and add it to the list of "Related Jira Entries" on this page.

Export DeveloperWiki page(s)

• Depending on the used Confluence macros (which contains the content of the page) the export will be a manual or semi-automated task. The result for "simple" Confluence pages like this page (using headers, subheaders, text, graphics, tables) is much better than for pages which are using e.g. the "Deck of Cards" macro (see example). As a workaround, copy content to a new, "plain" page without using problematic macros and export it instead of the original page.
• See Doc Tools page for a description of available tools, capabilities and limitations.

Prepare Content for usage in ReadTheDocs

• tbd 

Contribute to the ONAP Master Branch

• For details on how to contribute to the formal ONAP documentation, refer to the ONAP Documentation Guide.

Label the DeveloperWiki page(s) as "Migrated to ReadTheDocs" or "Deprecated Content"

• Example: Migrated Content

...

Archive the DeveloperWiki page(s)

• Migrated (or deprecated) content must be moved from the Confluence space "DW" to the Confluence space "Deprecated".
• To archive the migrated/deprecated DeveloperWiki page, go to the top of page, open the page menu "[...]" on the right side and choose the "Move" command. Move the page below "Migrated or Deprecated Documentation". 

...