Re: [onap-tsc] Logging Enhancements repository creation - OK

Team, Logging repo is now up - we are good to go. https://git.onap.org/logging-analytics https://gerrit.onap.org/r/#/admin/projects/logging-analytics Thank you Gildas and LF helpdesk. Original Message From:

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

Dear All, Excellent comments from Lusheng and Dan. I concur. To further expand on Dan’s comments, consider this use case. Company is using ONAP, but needs specific functionality but can’t wait on ONAP release cycle to get it, does the work internally and offers it to ONAP to be picked up for

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

Hi, Kenny, Could you please add a topic for next Monday’s (8/7/2017) “PTL & Coordinators Meeting”: · “ONAP development enforcement for R1 and forward” proposal I would like to get feedback from PTLs and Coordinators first. And then have another three days to get feedback from the

[onap-tsc] Meetings and Bridges

Community Members! Over the weekend I will be making some meeting bridge changes to better meet the needs of everyone involved in ONAP. We’ve had a few situations this week where teams were unable to start their meetings because another team had neglected to end a meeting. In at least one

Re: [onap-tsc] ONAP VoLTE SDC call

Can we use the SDC call on Monday 8am PDT to discuss the WAN service descriptor? Thanks, David From: yuan@zte.com.cn [mailto:yuan@zte.com.cn] Sent: Thursday, August 03, 2017 10:49 PM To: SHADMI, DAVID ; huang.zhuo...@zte.com.cn Cc: denghu...@huawei.com;

Re: [onap-tsc] Migration to *.onap.org

Also not sure if it is entirely black and white. There might be some projects we can move in the R1 timeframe if we allow for one project at a time migration. Then the PTL can make that choice based on there workload and project complexity. Oliver > On Aug 4, 2017, at 2:44 AM EDT, LEFEVRE,

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

All, I wanted to second Lusheng’s excellent comments below, and add perhaps a bit more. I think it’s important to bear in mind that some of the code that is contributed might not be entirely new. For example, much of the seed code that we submitted for openecomp was existing code that we had

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

Hi, Thanks David for sharing your analysis +1. Big chunk of code should not happen (whatever big mean). That is why when TSC reviewed and approved the “Development Best Practices” earlier in July, I

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

Thanks for sharing your perspective Lusheng, I think its important to get the perspectives of the projects into these discussions. BR, Steve. From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of JI, LUSHENG (LUSHENG) Sent: 04 August 2017 07:43 To:

Re: [onap-tsc] Migration to *.onap.org

Good morning Stephen, Thank you for your feedback. I will definitively finalize the high level plan as requested and will organize a call accordingly in the coming days. I will also consider Gildas' feedback based on the discussions we had with the LF Council. Best regards Catherine From: