Hi,
Thanks to Arul and team for putting this together.
We had one clarification today in the security subcommittee due to that it is
discussed whether to do the badging at the project level of the program level.
* In general it is fine (expected) to do this at the project level.
* However, a project may decide for different reasons to perform the
badging per repo or set of repos; if this made sense.
* This would imply from a S3P tracking perspective
* A project has passed if it and it its dependencies has passed.
* Note: sub-projects are responsible for doing their own badging process.
* For %complete the least complete value is the %complete of the project
BR,
Steve
From: Arul Nambi [mailto:[email protected]]
Sent: 19 January 2018 20:23
To: [email protected]; [email protected];
[email protected]
Cc: Stephen Terrill <[email protected]>; HANSEN, TONY L
<[email protected]>; Rajeev Mehta <[email protected]>
Subject: CII Badging Attention PTL
Hi Everyone,
If you have seen an email with almost the same subject ignore that, I had some
issues posting the first email so I am re-sending it again. Both emails have
the same content
For getting ONAP carrier ready one of the requirements is that 70% of its
projects needs to undergo a process called CII badging.
CII badging is a simple process(and takes less than a week normally) of
answering some questions about the project. And it is better if you start it
sooner than later.
And the security subcommittee has come up with a wiki page with
1. More information about the CII
2. Sample tools
3. Sample answers to all the questions that you will need to answer to get
your app badged.
The current ask is that 70% of the project should be in passing level, if you
want to go higher than that you can find the sample answers for the Silver and
gold level as well, they are not complete yet but if you find answers then add
them to the page.
Link: https://wiki.onap.org/display/DW/CII+Badging+Program
Let us know if you have any more questions or suggestions.
Regards
Arul
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
