[onap-tsc] [R2] Prioritization

Hello Following discussions in use-case & architecture subcommittees and the TSC, I think we should not only focus on use-case definition to drive the R2. The R1 release will not be perfect and there will be a lot of efforts to improve it. We should first prioritize the major topics not solved

Re: [onap-tsc] More Help For Adding Committers

Hi Ed, From the template: Link(s) demonstrating the Contributor's established history of meritocratic contributions to the project: (Typically this would be in the form of a gerrit query) So assuming that the template is followed then, yes, that information should be provided :-) Best Regar

Re: [onap-tsc] More Help For Adding Committers

Could we add the history of meritocratic contribution via a link to a gerrit query for the proposed committers contributions to the repos of the project? Ed On Thu, Aug 17, 2017 at 6:40 PM, Kenny Paul wrote: > In a further effort to both ease frustration of the PTLs and address > general scalab

[onap-tsc] More Help For Adding Committers

In a further effort to both ease frustration of the PTLs and address general scalability concerns, I have created a template for adding new Committers to an ONAP project. This template can be found by going to the Adding/Removing Committers to a Project

Re: [onap-tsc] Upcoming ONAP Nexus3 outage 2017-08-17 @ 16:00 - 17:00 PDT (23:00 - 00:00 UTC)

This work has now been completed. -Andy- On 08/17/2017 03:55 PM, Andrew Grimberg wrote: > This work will be starting shortly. > > -Andy- > > On 08/15/2017 12:40 PM, Andrew Grimberg wrote: >> What: The Linux Foundation will be performing a maintenance update on >> the ONAP Nexus3 server located

Re: [onap-tsc] Upcoming ONAP Nexus3 outage 2017-08-17 @ 16:00 - 17:00 PDT (23:00 - 00:00 UTC)

This work will be starting shortly. -Andy- On 08/15/2017 12:40 PM, Andrew Grimberg wrote: > What: The Linux Foundation will be performing a maintenance update on > the ONAP Nexus3 server located at https://nexus3.onap.org > > When: Thursday August 17, 2017 @ 16:00 - 17:00 PDT (23:00 - 00:00 UTC,

Re: [onap-tsc] R2 use cases planning

Alla – Thanks for bringing it up for discussion. Before making decisions on the use case content of R2, I believe we should have a better definition of the purpose of the use cases, and their selection criteria. I believe that once we have that nailed down, it will be easy to decide what goes i

Re: [onap-tsc] R2 use cases planning

Hi Alla: Thanks for sharing your views. This is a good discussion to be had – Focus on base ONAP capabilities or put some emphasis on new use cases. My opinion is the following: 1) I see these two things as somewhat linked and not disjointed from each other. As we look at missing ONAP pl

Re: [onap-tsc] R2 use cases planning

Hi Alla, IMHO, the use case helps us drive focus on a set of capabilities that we want to highlight in a release (be they features, architecture, models, interfaces, demos, etc.). I think it's helpful to identify that set up front and select a use case that can expose it. Ideally, the use case

Re: [onap-tsc] R2 use cases planning

Alla, Thank you for your leadership here and for the work of the use case committee on this topic. ONAP should be able to run any VNF or network service, even ones that aren't known today. And, just as importantly, ONAP needs to manage those VNFs and network services well, in a number of vari

[onap-tsc] R2 use cases planning

Hi again, And in order to start the actual discussion... :) My own view is: 1. We should concentrate on missing ONAP Platform capabilities 2. New functional use cases can only be considered if a. They have big level of similarity/harmonization with R1 use case b. They

Re: [onap-tsc] Leadership Diversity Language  // my slice for further discussion

Thanks Yuan! Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org 510.766.5945 > On Aug 17, 2017, at 8:08 AM, > wrote: > > > Attachement is my slice presented in the TSC meeting about this policy. > > Please have a look. > > > > > > > > 袁越 yuanyue >