Jason The coordinator we use to interact with SDO may need to be different than that for other open source projects. There are short term impacts of our first release on other open source projects like OPNFV, FD.io and Open Stack, etc.
Let’s discuss tomorrow in our TSC meeting. As of now, we have not approved any coordinators except security. I also need to check with the governance board whether we need any direction when interacting with SDO. Mazin On May 10, 2017, at 1:00 PM, Jason Hunt <djh...@us.ibm.com<mailto:djh...@us.ibm.com>> wrote: Good proposal. Would this coordinator also work with other open source projects? I'm thinking, in particular, of OPNFV where I think we could have a tight collaboration. Regards, Jason Hunt Executive Software Architect, IBM Phone: +1-314-749-7422 Email: djh...@us.ibm.com<mailto:djh...@us.ibm.com> Twitter: @DJHunt ----- Original message ----- From: 邓灵莉 <denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>> Sent by: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> To: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Cc: Subject: [onap-tsc] Creation Request for Coordination Area Standard/SDO Date: Wed, May 10, 2017 10:18 AM Coordination Area Description: Open source and standard are compliementing each other. Opensource is playing an increasing important role in SDO practice, which could help to gain industry concensus and adoption. The potential standard bodies and topics include: • IETF YANG/NETMOD/NFVRG • TMF OSS/API/ZOOM • MEF LSO • ETSI NFV/MEC • OASIS TOSCA • 3GPP • BBF Coordinator Responsibilities Description: • External Responsibilities: • Identify members of the ONAP community with existing relationships to external SDOs, and work with them to identify and follow the overlap in interest or practice from standard bodies related to ONAP’s implementation and report to TSC regularly or on demand. • Develop ONAP collaboration strategy with, coordinate ONAP presence, delegation and participation to identified SDO practices and report to TSC regularly or on demand. • Internal Responsibilities: • Work with individual projects in soliciting and identification of related SDO practices. • Coordinate between implementation project in ONAP and identified SDO practice and report to TSC regularly or on demand. • Coordinate among multiple implementation projects in ONAP which fall into scope of a given SDO spec and report to TSC regularly or on demand. Report Cadence: • Regularly each TSC F2F meeting. • On-demand report based on urgency of the event. Area Coordinator: Hui Deng denghu...@huawei.com<mailto:denghu...@huawei.com> Lingli/邓灵莉 中国移动通信研究院 denglin...@chinamobile.com<mailto:denglin...@chinamobile.com> _______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=XKUn57AaVgxzq3DD1RTnV7afF26cgZR5_nI143MWmGM&s=bWL0RMcjKp6RDJ1PBIpJOZ6p_uVFkinvFqtdPhcTkwU&e=> _______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=XKUn57AaVgxzq3DD1RTnV7afF26cgZR5_nI143MWmGM&s=bWL0RMcjKp6RDJ1PBIpJOZ6p_uVFkinvFqtdPhcTkwU&e=
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
