+N where N is the number of people in Cisco that keep asking me where the last approved version of the documentation can be found and what is the process in the ONAP documentation (submission - discussion - approval - implementation in the code / documentation?). They don't understand why ONAP is not working (even does not have timeline) on delivery of specifications to reach the level of the Linux Standard Base (ISO/IEC 23360-1) or ODL. I understand difficulties of starting a new organization and appreciate people that worked hard to deliver the R1. The question is whether for R2 some level of maturity can be reached. To make it happen, we need to work on it. Besides, clear procedure is absolutely necessary element of transparency.
Thanks Vladimir From: [email protected] [mailto:[email protected]] On Behalf Of Sabater, Susana, Vodafone Spain Sent: Tuesday, November 21, 2017 11:47 PM To: Alla Goldner <[email protected]>; Pasi Vaananen <[email protected]>; Stephen Terrill <[email protected]>; [email protected]; [email protected] Subject: Re: [Onap-arc] ONAP Architecture presentation +1 Regards /Susana From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alla Goldner Sent: Tuesday, November 21, 2017 6:32 PM To: Pasi Vaananen <[email protected]<mailto:[email protected]>>; Stephen Terrill <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [onap-tsc] [Onap-arc] ONAP Architecture presentation +1 and including TSC list for a broader discussion of this issue. One of the problems we face is that there are multiple locations where presentations are uploaded (f uploaded), e.g. under Usecase or Architecture subcommittee, in a dedicated project area etc. In my view, the best way to support visibility of all submitted documents is to have a single placeholder as done by a different SDO e.g. 3GPP, ETSI NFV - and then it may be further distinguished there by subject, submitter, targeted subcommittee/project etc. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Pasi Vaananen Sent: Tuesday, November 21, 2017 7:06 PM To: Stephen Terrill <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [Onap-arc] ONAP Architecture presentation +1 ... but this should not be limited only to architecture team presentations. Pasi On 11/21/2017 12:00 PM, Stephen Terrill wrote: Hi Chris, Can I make a suggestion regarding the presentations in the ONAP Architecture team. Sometimes the presentation cannot be found afterwards. I think it's a common practice in a few foras that the documentation has to be uploaded before being presented, can we assume the same practice here ? BR, Steve [Ericsson]<http://www.ericsson.com/> STEPHEN TERRILL Technology Specialist DUIC, Systems and Technology Development Unit IP & Cloud Business Unit, IT & Cloud Products Ericsson Ericsson R&D Center, via de los Poblados 13 28033, Madrid, Spain Phone +34 339 3005 Mobile +34 609 168 515 [email protected]<mailto:[email protected]> www.ericsson.com<http://www.ericsson.com> [http://www.ericsson.com/current_campaign]<http://www.ericsson.com/current_campaign> Legal entity: Ericsson España S.A, compay registration number ESA288568603. This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer> _______________________________________________ Onap-arc mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-arc 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-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
