Thanks to Ed, Steve, Alla, Lingli, Phil, and Chris. It's comprehensive. I've attached the document with some notes, and I hope these could help.
Regards, Xiaojun XIE Technical Director of IT R&D Center, Guangzhou Research Institute of China Telecom. (O) 86-20-38639130 (M) 86-13316090153 xiexj.gd at chinatelecom.cn From: Jason Hunt Date: 2017-04-06 11:11 To: Christopher.Donley CC: onap-tsc Subject: Re: [onap-tsc] DRAFT Technical Community Charter Thank you to Ed, Steve, Alla, Lingli, Phil, and Chris for pulling this together! It looks great! I've attached a marked up version with some comments -- none major, but just looking for clarifications. I would welcome hearing from others on the perceived differences of "coordinators" vs "subcommittees" and in what other projects these structures have been used. Whichever we choose, I would tend toward not specifying in the charter which topics would be covered (just like we don't specify the actual projects in the charter). Thanks! Regards, Jason Hunt Executive Software Architect, IBM Phone: +1-314-749-7422 Email: djhunt at us.ibm.com Twitter: @DJHunt ----- Original message ----- From: "Christopher Donley (Chris)" <[email protected]> Sent by: onap-tsc-bounces at lists.onap.org To: "onap-tsc at lists.onap.org" <onap-tsc at lists.onap.org> Cc: Subject: [onap-tsc] DRAFT Technical Community Charter Date: Wed, Apr 5, 2017 1:14 PM --> Dear TSC, Ed, Steve, Alla, Lingli, Phil, and I have put together the attached DRAFT technical community charter. It is largely based on similar documents from ODL, OPNFV, FD.IO, and OPEN-O. There are a number of open issues in the draft, and we are looking for your feedback. To highlight a few areas and some of our questions: ? TSC Vice Chair: should we have one, and if so, did we describe the role correctly? ? Coordinators (leadership roles focused on various technical topics that we may want to address as a community): Is this the right approach? Did we call out the right examples? ? Subcommittees: we describe rules for establishing subcommittees under the TSC. This is a slightly different approach than coordinators to ensuring critical topics are addressed. Do we want to use both? Did we capture the distinction clearly enough? ? Architecture Committee: we specifically call it out in this draft. Do we want an Architecture Committee? Should it be included in the Charter? We?d like to request a 30-minute slot during this week?s TSC meeting to present the existing draft and start to collect feedback. Thanks, Chris _______________________________________________ ONAP-TSC mailing list ONAP-TSC at lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170406/182ddc31/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ONAP TSC Charter DRAFT 6 6 Clean - XXJ.docx Type: application/octet-stream Size: 113543 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170406/182ddc31/attachment-0001.obj>
