Versions Compared

Key

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

...

  • The term MUST is an absolute requirement, and MUST NOT is an absolute prohibition.
  • The term SHOULD indicates a criterion that is normally required, but there may exist valid reasons in particular circumstances to ignore it. However, the full implications must be understood and carefully weighed before choosing a different course.
  • The term SUGGESTED is used instead of SHOULD when the criterion must be considered, but valid reasons to not do so are even more common than for SHOULD.
  • Often a criterion is stated as something that SHOULD be done, or is SUGGESTED, because it may be difficult to implement or the costs to do so may be high.
  • The term MAY provides one way something can be done, e.g., to make it clear that the described implementation is acceptable.
  • To obtain a badge, all MUST and MUST NOT criteria must be met, all SHOULD criteria must be met OR the rationale for not implementing the criterion must be documented, and all SUGGESTED criteria have to be considered (rated as met or unmet). In some cases a URL may be required as part of the criterion's justification.

R2 Beijing Requirements

For the Beijing release, the compliance requirement is ONAP Level 1 (at least 70% of the project are on passing level, and all non-passing projects at >80% towards passing).

R2 Beijing Current Status Dashboard

The dashboard gives a list of all onap projects that are undergoing the process and their % of completion.

<TODO insert a link to the dashboard table here>


Do I Report For the Entire Project or Separately For Every Single Repo? Can I Group Repos Together?

...

  • If your repositories use different languages or different testing procedures, you probably would find it easier to do it per-repository.
  • You may also group multiple repositories together, if that would help. For example, you might group all of the repositories together that use Java, or all of the repos together that use Erlang.
  • The key to grouping repositories together is to list all of the repo URLs in the response to the question "What is the URL for the version control repository?" question.

It's your choice as to what makes it easiest for you to manage your project.

If you do file one report for the entire project, or group multiple repos together then you need to answer each Met/Not Met question based on the lowest-common denominator answer: if ANY of the repos don’t meet the requirement, you cannot select Met. You can use the text response for each question to keep track of your reasons for picking any particular answer.

R2 Beijing Requirements

For the Beijing release, the compliance requirement is ONAP Level 1 (at least 70% of the project are on passing level, and all non-passing projects at >80% towards passing).

R2 Beijing Current Status Dashboard

The dashboard gives a list of all onap projects that are undergoing the process and their % of completion.

<TODO insert a link to the dashboard table here>

Procedure to Fill Out the BestPractices.CoreInfrastructure.Org Form

...