Chris, Thank you for more information.
Regarding the committees you referred to in OPNFV, actually: - Strategic Planning Committee and Certification & Compliance Committee are all Board committees, NOT TSC committee. - Polestar WG, MANO WG, and Test WG are all community-driven working groups. They were proposed by community, and organized by community. There is NO formal structure of those working groups in TSC Charter. In fact o Polestar only lived for about 3 months, and no more activity now. o MANO WG was formed only because MANO Project proposal was not approved by TSC. And TSC suggested to have a MANO WG instead of MANO project to coordinate several orchestration related projects. o Test WG was formed to coordinate testing projects and activities You can see, from TSC Charter perspective, there is no formal structural components. When an interesting topic and/or coordination is needed, WGs were formed by the need of work, and driven by community. A WG may disappear if there is lack of interest (e.g. Polestar) from community. For the specific need of merge of ECOMP and Open-O, an Architecture WG may be formed to enable the need. Once the mission is achieved and we have a successful first release, this Architecture WG may not be needed. One example in industry is that basically no participation or interest of Architecture WG in OpenStack so it disappeared in OpenStack. In summary, an Architecture WG is needed to achieve this mission of merging ECOMP and Open-O, which is short-term of the first a couple of releases. But it may not be appropriate as a permanent, structural component in TSC Charter. Just my 2 cents Thanks Bin From: Christopher Donley (Chris) [mailto:[email protected]] Sent: Thursday, April 13, 2017 9:40 AM To: HU, BIN <bh526r at att.com>; Ed Warnicke <hagbard at gmail.com> Cc: onap-tsc at lists.onap.org Subject: RE: [onap-tsc] Charter Bin, A correction ? OPEN-O does have a Vice Chair and an architecture committee. Because we started by merging SDN and NFV orchestration, we needed a holistic view of the architecture. For example, we identified four different SDN Controller roles in the network, and needed to work out which module was talking to which controller to avoid a multi-writer problem. We also had to work through how the various components talked to one another. Since this discussion was larger in scope than a single project, we found it helpful to have a group identified to do the work (in practice, it was anyone who wanted to participate). Given the scope of ONAP and the complexity of merging OpenECOMP and OPEN-O, I think it would be useful to have a formal committee defined here, as well. Also, it?s not that far off from OPNFV, which has had several committees (both formal and informal) such as Polestar, strategic planning committee, certification & compliance committee, mano working group, cross-project testing community meetings, etc. Chris From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of HU, BIN Sent: Thursday, April 13, 2017 6:48 AM To: Ed Warnicke Cc: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: Re: [onap-tsc] Charter Ed, Thank you for confirming that there is no precedent of such structural components in other communities. And thank you everyone for great volunteer work ? Thanks Bin From: Ed Warnicke [mailto:[email protected]] Sent: Thursday, April 13, 2017 6:20 AM To: HU, BIN <bh526r at att.com<mailto:bh526r at att.com>> Cc: Ning.So at ril.com<mailto:Ning.So at ril.com>; stephen.terrill at ericsson.com<mailto:stephen.terrill at ericsson.com>; onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: Re: [onap-tsc] Charter Bin, fd.io<https://urldefense.proofpoint.com/v2/url?u=http-3A__fd.io&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6qPcDOqMgwf1K_r6YIIHhw&m=oSTVwWDVUzrnY8bUMMEEiULrmy_0QxwvShbSWsoyi8I&s=f2k9eD1nx1FB1uBPzmVaHkXAnQfHU5jsaxGFIzoz1Tw&e=> and ODL do not have either sub-committee or coordinators defined in their charters. Neither do they have Architecture Committees nor Vice Chairs. In practice, both fd.io<https://urldefense.proofpoint.com/v2/url?u=http-3A__fd.io&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6qPcDOqMgwf1K_r6YIIHhw&m=oSTVwWDVUzrnY8bUMMEEiULrmy_0QxwvShbSWsoyi8I&s=f2k9eD1nx1FB1uBPzmVaHkXAnQfHU5jsaxGFIzoz1Tw&e=> and ODL have from time to time asked for volunteers to go prepare a proposal for the TSC for various purposes, similar to what is happening here with volunteer subgroup of the TSC working on this proposal. Ed On Mon, Apr 10, 2017 at 12:42 PM, HU, BIN <bh526r at att.com<mailto:bh526r at att.com>> wrote: +1 for the name of ?Technical Steering Committee Charter?. In addition, because we put the emphasis on the community, a simple and lean structure will help TSC achieve the goal of serving the technical community better. Thus I suggest that: - Remove the role of Vice Chair and Coordinators o Those roles are really redundant, and I never see it in e.g. OpenStack, ODL, FD.io, OPNFV etc. Correct me if I am wrong if you do see Vice Chair, Coordinator roles in the Charter of those TSCs. o Cross-project coordination are usually done by PTLs of those projects. They work very well. - Sub-committees are also redundant structure o Correct me if such structure is defined in OpenStack, ODL, FD.io, OPNFV etc. Just my 2 cents Thanks Bin From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org>] On Behalf Of Ning.So at ril.com<mailto:[email protected]> Sent: Monday, April 10, 2017 12:11 PM To: stephen.terrill at ericsson.com<mailto:stephen.terrill at ericsson.com>; onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: Re: [onap-tsc] Charter My preference is ?Technical Steering Committee Charter? to be consistent with the TSC name. ?Technical Community Charter? can lead to confusions, as the charter itself is really about TSC?s structures and roles. Ning From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-bounces at lists.onap.org<mailto:[email protected]>] On Behalf Of Stephen Terrill Sent: Monday, April 10, 2017 1:36 PM To: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: [onap-tsc] Charter Hi All, In the F2F TSC regarding the charter, there as an item that we should take to the mailing list. Charter name: Should we call the charter ?Technical Steering Committee Charter? or ?Technical Community Charter?. Note: The second option puts the emphasis on the community and the TSC is helping to ensure the operations for the community. Please, opinions welcome as we are drafting the updates during this week. Best Regards, Steve. [Image removed by sender. Ericsson]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6qPcDOqMgwf1K_r6YIIHhw&m=r3pgCHr5hs-WgnwILuBxkZ6Zh6LeqKwJLfR0NovNhM4&s=sCVlq4goG80rg44j45K2Kf11fJ_Nl2v7vpanZzqG0Jg&e=> 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<tel:+34%20609%2016%2085%2015> Stephen.Terrill at ericsson.com<mailto:Stephen.Terrill at ericsson.com> www.ericsson.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6qPcDOqMgwf1K_r6YIIHhw&m=r3pgCHr5hs-WgnwILuBxkZ6Zh6LeqKwJLfR0NovNhM4&s=HR4y_CA6Qt99uPnJ_nchFeRqgVrxEvgGRqVhWBUf8cU&e=> [Image removed by sender. http://www.ericsson.com/current_campaign]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_current-5Fcampaign&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6qPcDOqMgwf1K_r6YIIHhw&m=r3pgCHr5hs-WgnwILuBxkZ6Zh6LeqKwJLfR0NovNhM4&s=pR-w0LvCWFoFyVVzRx0m3W8kgk-Tec4X1eo7TNdlJJs&e=> 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_email-5Fdisclaimer&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6qPcDOqMgwf1K_r6YIIHhw&m=r3pgCHr5hs-WgnwILuBxkZ6Zh6LeqKwJLfR0NovNhM4&s=n6olHgWAAKC3bhFTWdTrHP-RdGP1JXt1j85SpII3Nso&e=> "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." _______________________________________________ ONAP-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at 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=6qPcDOqMgwf1K_r6YIIHhw&m=oSTVwWDVUzrnY8bUMMEEiULrmy_0QxwvShbSWsoyi8I&s=dBqv50lYqgKaFKfofi0FHoEZVjJ5PKCNNSe3T9zpx9Q&e=> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170413/56139704/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 386 bytes Desc: image001.jpg URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170413/56139704/attachment-0002.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 804 bytes Desc: image002.jpg URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170413/56139704/attachment-0003.jpg>
