Thanks, Arul!










Original Mail



Sender:  <arul.na...@amdocs.com>;
To: zhaohuabing10201488; <t...@att.com>; <stephen.terr...@ericsson.com>;
CC:  <onap-sec...@lists.onap.org>; <rajee...@amdocs.com>; 
<onap-discuss@lists.onap.org>; <onap-...@lists.onap.org>;
Date: 2018/01/26 22:34
Subject: RE: [onap-discuss]     [onap-tsc] CII Badging Attention PTL 




Hi Huabing,


In your case the report will be for msb project.


So your project home page URL will be


https://wiki.onap.org/display/DW/Microservices+Bus+Project


 


And your gerrit repo URL will be


https://gerrit.onap.org/r/msb/


 


Currently in my testing linux foundation does not allow us to clone under 
project level. We will have to talk to CII badging to see if the URL needs to 
be useable  or is it only for reference. If it has to be usable link then we 
will have to ask Linux foundation to let us clone a full project instead of a 
repo.


Hope this helps.


Regards


Arul


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
 Sent: Thursday, January 25, 2018 8:32 PM
 To: t...@att.com; stephen.terr...@ericsson.com
 Cc: onap-sec...@lists.onap.org; Rajeev Mehta <rajee...@amdocs.com>; 
onap-discuss@lists.onap.org; onap-...@lists.onap.org
 Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL 


 

Hi Tony, Steve,

Thanks for the explanation, it really helped. 

One more question, do you happend to know how could I submit all the repos 
together if I want to apply at project level? 

The below screenshot show that only one repo can be submitted per project. I 
tried to contact Core Infrastructure Initiative directly to get the answer, but 
I can't find their contact information.



 

Thanks,

Huabing

 

 


Original Mail



Sender:  <t...@att.com>;



To: zhaohuabing10201488;



CC:  <onap-sec...@lists.onap.org>; <rajee...@amdocs.com>; 
<onap-discuss@lists.onap.org>;  <onap-...@lists.onap.org>; 
<stephen.terr...@ericsson.com>;



Date: 2018/01/25 22:54



Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL




As PTL, it’s your choice. You can do a single report for your entire project, 
or you can file a separate report for each repo. If your repos use different 
languages or different  testing procedures, you probably would find it easier 
to do  it per-repo.


 


If you do file one report for the entire project, 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. (Use the text box 
 to keep track of your reasons for picking any particular answer.)


 


                Tony Hansen


 



From: <onap-discuss-boun...@lists.onap.org> on behalf of 
"zhao.huab...@zte.com.cn" <zhao.huab...@zte.com.cn>
 Date: Thursday, January 25, 2018 at 2:16 AM
 To: "stephen.terr...@ericsson.com" <stephen.terr...@ericsson.com>
 Cc: "onap-sec...@lists.onap.org" <onap-sec...@lists.onap.org>, 
"rajee...@amdocs.com" <rajee...@amdocs.com>,  "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>, "onap-...@lists.onap.org" 
<onap-...@lists.onap.org>
 Subject: Re: [onap-discuss] [onap-tsc] CII Badging Attention PTL



 

Hi Arul and Seve,

 

It's a common situation that an ONAP project has multiple repos. Is it possible 
to submit the rpos as a whole as one project when applying for CII  Badging? Or 
I have to submit one by one?

 



 

Thanks,

Huabing


Original Mail



Sender:  <stephen.terr...@ericsson.com>;



To:  <arul.na...@amdocs.com>;  <onap-discuss@lists.onap.org>;  
<onap-...@lists.onap.org>; <onap-sec...@lists.onap.org>;



CC:  <rajee...@amdocs.com>;



Date: 2018/01/25 00:27



Subject: Re: [onap-tsc] CII Badging Attention PTL




_______________________________________________
 ONAP-TSC mailing list
 onap-...@lists.onap.org
 https://lists.onap.org/mailman/listinfo/onap-tsc
 
  


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:arul.na...@amdocs.com] 
 Sent: 19 January 2018 20:23
 To: onap-discuss@lists.onap.org; onap-...@lists.onap.org; 
onap-sec...@lists.onap.org
 Cc: Stephen Terrill <stephen.terr...@ericsson.com>; HANSEN, TONY L 
<t...@att.com>; Rajeev Mehta <rajee...@amdocs.com>
 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










 









 



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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to