Hi Alla, I fully understand there are other important meetings in parallel. As we had to make it this week, we have offered choices by offering 2 sessions for "Lessons Learned" and 2 sessions for "Process Improvements" to accommodate the largest audience possible. We also suggested people to share their feedback directly within the wiki at https://wiki.onap.org/display/DW/ONAP+Beijing+Retrospective+and+Lesson+Learned
Hope this helps. See you next week in Beijing. Best Regards, Gildas ONAP Release Manager 1 415 238 6287 From: Alla Goldner [mailto:[email protected]] Sent: Sunday, June 10, 2018 7:41 AM To: Gildas Lanilis <[email protected]>; [email protected]; onap-tsc <[email protected]>; [email protected] Subject: RE: Beijing Lessons Learned Gildas, This is scheduled in parallel to Usecase subcommittee meeting. Many of the people attending Usecase subcommittee are also interested in this topic. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] -----Original Appointment----- From: Gildas Lanilis [mailto:[email protected]] Sent: Friday, June 08, 2018 2:52 AM To: Gildas Lanilis; [email protected]<mailto:[email protected]>; onap-tsc; [email protected]<mailto:[email protected]> Subject: [Onap-release] Beijing Lessons Learned When: Monday, June 11, 2018 7:00 AM-8:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/2229355644 Dear ONAP Community, We are organizing several brainstorming sessions next week in order to determine any improvement plan for the ONAP Casablanca Release. The first step will be to collect your feedback concerning the ONAP Beijing Release from a retrospective and lesson learned perspectives. Based on what we have learned, we will prioritize on what can be addressed as "Process Improvement" in short in longer term. Planning: Monday-Tuesday: Lesson Learned Wednesday-Thursday: Process Improvement It is important to understand that during Lesson Learned session, the goal is to collect feedback, not to fix things. During the "Process Improvement" sessions, we will dive on the "how" to fix it. Being realistic, we may need more time to discuss while we meet at Beijing. Ideally, we would like to get the low hanging fruits approved by TSC while at Beijing. Feel free to submit already your feedback on the ONAP wiki page: https://wiki.onap.org/display/DW/ONAP+Beijing+Retrospective+and+Lesson+Learned We are suggesting to classify your inputs under the following categories * Communication - Wiki, Mailing Lists, IRC * Labs & Test Environment * Release Management * JIRA Management * Code Review * Development Infrastructure * PTL Role * Architecture * Open Source Values * Others Many thanks & regards Catherine & Gildas [https://d24cgw3uvb9a9h.cloudfront.net/static/90981/image/new/ZoomLogo_110_25.png]<http://zoom.us/> Hi there, Gildas Lanilis is inviting you to a scheduled Zoom meeting. Join Zoom Meeting<https://zoom.us/j/2229355644> Phone one-tap: US: +16465588656,,2229355644#<tel:+16465588656,,2229355644> or +16699006833,,2229355644#<tel:+16699006833,,2229355644> Meeting URL: https://zoom.us/j/2229355644 Join by Telephone For higher quality, dial a number based on your current location. Dial: US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free) Meeting ID: 222 935 5644 International numbers<https://zoom.us/u/TU2f6> << File: ATT00001.txt >> 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
