Versions Compared

Key

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

...

Contribution TypeMethod(s)
General questions, feedback, or support requestsLeverage the ONAP mailing lists. Send an email to onap-discuss@lists.onap.org and use the project hashtag #vnfrqts in the subject line of your email.
Staying apprised of progress or collaborating on new work

Attend the weekly VNF Requirements project meetings.

Review prior meeting minutes

Additionally you can register for a Linux Foundation ID, and sign into Gerrit and/or JIRA to repository commits and JIRA issues.

Submitting Bugs

If you find an issue in the VNF Requirements project in either the ONAP Developer Guide or the ONAP Wiki, please submit a JIRA ticket under the VNF Requirements project

Project: VNF Requirements

Issue Type: Bug

Please include the link to the page in question and if applicable the requirement(s) IDs that are impacted.

Contributing Updates to VNF Provider Guidelines and Requirements

We welcome both new requirements and revisions to existing requirements and content. Before contributing the content, please familiarize yourself with the VNFRQTS Requirement and Documentation Standards.

Our preferred form of contribution is to submit changes as Gerrit Reviews against the target VNF Requirements repository (see Submitting Gerritt Reviews below for more details)

If you are proposing substantial changes to the project or the change requires discussion, then we encourage you to create a Proposal on the ONAP VNF Requirements Project Wiki to introduce the topic first. Please refer to the VNF Requirements Proposals page for more details.

If you do not feel comfortable with the tool chain required to submit changes directly to the reStructuredText via Gerrit reviews, then we would still like to support your contributions and encourage you to put the details of your changes into JIRA.

Project: VNF Requirements

Issue Type: Task

Summary: Short summary of the change

In the Description field please include the following details:

  • The full content you are proposing (NOTE - you do not need to provide the requirement IDs, those will be assigned by the VNF Requirements team when the content is addedcan be added generated using the VNFRQTS Requirement Generation Tool)
  • Where the content should appear (please include the section and link to the page)
  • The rationale for adding this to the requirements
  • If adding requirements, please provide the applicable metadata per the Requirement Metadata section of the VNFRQTS Requirement and Documentation Standards

If you are submitting a ticket, then you are encouraged to attend the VNF Requirements weekly meeting if your schedule permits.

...