Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: Wednesday, August 02, 2017 2:49 PM To: onap-tsc Subject: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face Hello ONAP TSC Members: As

Re: [onap-tsc] ONAP VoLTE SDC call

Team, I posted to the VoLTE Use Case wiki (Drafts for discussion sub-page) an updated version of the PPT file that I quickly covered in today's call. It contains a proposal on how to support this near term need that we face together. Here is the link:

[onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

Hello ONAP TSC Members: As was mentioned at the last TSC meeting, Nokia and Orange have offered to host the next ONAP Developer Face to Face meeting the week of September 25th, 2017 at the Nokia Paris-Saclay facility approximately 25 Kilometers south west of the Paris Orly airport. We will have

Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face ToFace

[VOTE] +1 Original Mail Sender: To: Date: 2017/08/03 05:49 Subject: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face ToFace Hello ONAP TSC Members: As was mentioned at the last TSC meeting, Nokia and

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

I think getting something like statckalytics going is goodness, but I don't think it gets to the upstream first issue. Look at David's original complaint about 10k LOC patches coming in, and it *hinting* at code being developed behind closed doors and being pushed up in batch. 2 10k LOC patches

Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 On Aug 2, 2017, at 2:49 PM, Phil Robb > wrote: Hello ONAP TSC Members: As was mentioned at the last TSC meeting, Nokia and Orange have offered to host the next ONAP Developer Face to Face meeting the week of September 25th, 2017

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

With all respect, I think this might be better characterized. I don't think the alternative to the current practices is "upstream first". Likewise, I don't think it makes any sense to develop something that doesn't yet exist by first forming a project elsewhere, like on Github, just so we can then

Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 Sent from my iPhone On Aug 2, 2017, at 8:04 PM, Lingli Deng > wrote: [VOTE] +1 Lingli From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil

Re: [onap-tsc] Leadership Diversity Language

TSC Members, Seeing no other feedback beyond Chris and Steve’s comments I believe that this is also a topic that should be moved to next week’s TSC meeting. If anyone disagrees, please let me know. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org

Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

[VOTE] +1 Lingli From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: 2017年8月3日 5:49 To: onap-tsc Subject: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face Hello ONAP TSC Members:

[onap-tsc] FW: FW: Apply for the Committer Privilege for Holmes

Hi there, Could anyone help to solve this? It's been a while. Thanks! Regards, Guangrong 原始邮件 发件人：付光荣10144542 收件人： 抄送人： 日 期 ：2017年08月02日 21:57 主 题 ：FW: Apply for the Committer

Re: [onap-tsc] TSC Charter Proposed section 5.4.1.4

TSC Members, I have not seen any traffic around this topic. Unless anyone disagrees it would probably be best to push this to next week’s TSC meeting and remove it from tomorrow’s agenda. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org 510.766.5945 >

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

David You are raising a valid point and it relates to my previous note to the TSC about monitoring and evaluating code quality. I suggested forming a subcommittee to make a recommendation. This is vital for the success of ONAP. Our first release includes a merger of open ecomp and open-o

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

Suggestion for encouraging proper behavior – Can the LF implement a code contribution statistics tool (something like OpenStack stackalytics) on the ONAP repos? That way we can easily track things like average LOC per commit for each project/repo, find anomalies and

Re: [onap-tsc] [VoLTE][Control Loop] VoLTE Use Case Control Loop Automation followup discussion

BEGIN:VCALENDAR METHOD:REQUEST PRODID:-//Tencent Corporation//Foxmail VERSION:2.0 CALSCALE:GREGORIAN BEGIN:VEVENT UID:806F72B2-2018-465E-AD8A-7B5D79EBDBBF CLASS:PUBLIC DTEND:20170801T13Z STATUS:TENTATIVE TRANSP:OPAQUE CREATED:20170731T040233Z DTSTAMP:20170731T040233Z DTSTART:20170801T12Z

Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com Platinum Member. Visit : http://www.onap.org From:

Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 Original Message Subject: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face From: Phil Robb Date: Aug 3, 2017, 12:49 AM To: onap-tsc Hello ONAP TSC Members: As was mentioned at the last TSC meeting,

Re: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 Ranny. From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: Wednesday, August 2, 2017 2:49 PM To: onap-tsc Subject: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face Hello ONAP TSC Members:

[onap-tsc] SDC VoLTE - Recommendation to focus on Plan A

ONAP TSC, After reviewing the feedback on the TOSCA support for VoLTE Use Case there is a path, with help from the community, to implement Plan A. Plan A is a single SDC application that would support both HEAT and TOSCA artifact imports which is the fundamental vision of merging the two

Re: [onap-tsc] M2 Amsterdam Functionality Freeze is coming

Dear PTLs, As a kindly reminder, it is expected you fill out in the project space with the M2 Functionality Freeze Checklist. We will review the artifacts during TSC meeting on Thursday, August 3. Let me know if you have any questions. Thanks, Gildas ONAP Release Manager 1 415 238 6287 From:

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

Thank you. All of these requests have been approved. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org 510.766.5945 > On Jul 22, 2017, at 11:49 AM, Kenny Paul wrote: > > As mentioned we have several repository requests queued up.

[onap-tsc] TR: TSC VOTE on Repos for AAI, AAF, Modeling & MSB

Hello +1 All I replace Jamil. Best Regards Eric De : CHAWKI Jamil IMT/OLN Envoyé : mercredi 2 août 2017 14:13 À : DEBEAU Eric IMT/OLN Objet : Fwd: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB Cordialement Jamil Début du message transféré : Expéditeur: Kenny Paul

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

+1 on Upstream first. Some views on ONAP’s adoption in production environments: 1. Regular Code Quality Analysis to be done. 2. Arrive at #TECHDEBT and have it tracked through Jira backlog 3. Every release plan MUST cover as to what % of #TECHDEBT would be addressed in that

[onap-tsc] Enforcing an "Upstream first" approach to ONAP

Hi TSC members, I would like to bring to our attention one major opportunity for improvement in the behaviour currently adopted by some of our community members. I am observing a big number of very large commits (10’s of thousands of lines of code in a single commit) which to me is a symptom

Re: [onap-tsc] SDC VoLTE - Recommendation to focus on Plan A

Hi Brian, All, It sounds like the correct approach to me. Is there a description of the Plan A solution and related project gaps? Sounds like it would be good to have this on the TSC agenda on Thursday (Kenny??). BR, Steve From: onap-tsc-boun...@lists.onap.org

Re: [onap-tsc] SDC VoLTE - Recommendation to focus on Plan A

+1, both on the architecture approach and the need to discuss and decide ASAP. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D30BC2.565AAB60] From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

+1 Upstream first . thanks to bring this . murat On Wed, Aug 2, 2017 at 10:27 AM, Dhananjay Pavgi < dp00476...@techmahindra.com> wrote: > +1 on Upstream first. Some views on ONAP’s adoption in production > environments: > > > > 1. Regular Code Quality Analysis to be done. > > 2.