Hi Guys,
Thanks for helping me compile the list. Now we need to go to the second step 
which is coming up with the flow and integrating it with Sonar.
I have the intent recorded in wiki.  
https://wiki.onap.org/display/DW/Languages+supported+for+code+coverage
But I am also adding it to this chain
Since no one person will have the knowledge of tools and techniques in all the 
languages the plan we have is.
1.    Choose a pilot project for every language
2.    Work out a generic plan for that language which can be ported to all the 
projects under the same language
3.    Communicate the plan through ONAP discuss and the seccoom mailing list so 
that other projects with the same language can be sure that they can support it.
4.    Then the pilot project will implement the setup locally and then work 
with the PTL for the pilot project and LF to get the tools installed.
Responsibilities of the pilot project
1.    Come with a generic proposal to get the reports generated in SONAR.
2.    Come up with the tools and techniques that are required.
3.    Get the tools installed in LF.
We need to find a pilot project for all the languages if we need code coverage 
for that particular language. And having code coverage is a requirement for CII 
badging.
Benefits of being the pilot
The pilot project's recommendation and setup will be the one that is officially 
supported. So lead the way to get your preferred way of setup in.

Also we will need 2 contacts per project preferably so that we can reach out to 
one if one is on vacation.
Also I thought PHP will come up, but no one added a entry for PHP. So if your 
project is using PHP and need code coverage support please add it in the page
Next Step
For the ones where is no pilot project, please volunteer to get the setup in 
because we need this for CII badging. The security team will help you out if  
needed, but like I said we need expertise and a pilot project.
Regards
Arul

From: Arash Hekmat
Sent: Friday, July 13, 2018 9:47 AM
To: onap-discuss@lists.onap.org; kiran.k.kamin...@intel.com; Addepalli, 
Srinivasa R <srinivasa.r.addepa...@intel.com>; shankarp...@gmail.com
Cc: Arul Nambi <arul.na...@amdocs.com>; onap-sec...@lists.onap.org
Subject: RE: [Onap-seccom] [onap-discuss] Att: PTL - Languages supported in ONAP

Erlang may also being used in some projects (DCAE?) but it's for the PTLs to 
confirm.

Thanks,
Arash

From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> On Behalf Of 
Kiran Kamineni
Sent: Wednesday, July 11, 2018 11:41 AM
To: Addepalli, Srinivasa R 
<srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
shankarp...@gmail.com<mailto:shankarp...@gmail.com>
Cc: Arul Nambi <arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>>; 
onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>
Subject: Re: [Onap-seccom] [onap-discuss] Att: PTL - Languages supported in ONAP

We use golang in Secret Management project.
Regarding tools, golang has some built in tools for coverage (we already use 
this to report coverage numbers for each build) and static analysis.

-- K i r a n

From: onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org> 
[mailto:onap-sec...@lists.onap.org] On Behalf Of Srini
Sent: Wednesday, July 11, 2018 7:38 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
shankarp...@gmail.com<mailto:shankarp...@gmail.com>
Cc: arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>; 
onap-sec...@lists.onap.org<mailto:onap-sec...@lists.onap.org>
Subject: Re: [Onap-seccom] [onap-discuss] Att: PTL - Languages supported in ONAP

Keep golang also in mind

Thanks
Srini

On Jul 11, 2018, at 19:59, Shankar Narayanan 
<shankarp...@gmail.com<mailto:shankarp...@gmail.com>> wrote:
Hi Arul,

Please do include Python as well to the list. There are quite a few projects 
that have significant Python code bases. OOF, for instance, is a pure python 
project, and would need python support from the tools used for code 
coverage/analysis.

Thanks,
Shankar.

On Wed, Jul 11, 2018 at 10:07 AM Arul Nambi 
<arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>> wrote:
Hi PTL's/Community,
In the security committee we are looking for the list of languages that needs 
to be supported when we come up with new tools for code coverage and static 
analysis.
Currently we know of

  1.  Java(ofcourse)
  2.  Javascript
We think that we will need PHP and Phyton, but need confirmation from the 
projects(preferably PTLs) about the language support that is needed and the 
name of the project.
There is a query in gerrit which can be used to find projects with certain file 
extensions, but it hard think of all the languauges.
Once we have a complete list I can update the wiki page so that in future we 
will know the languages that we support.
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 
<https://www.amdocs.com/about/email-disclaimer>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11238): https://lists.onap.org/g/onap-discuss/message/11238
Mute This Topic: https://lists.onap.org/mt/23246357/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to