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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170405/498a27df/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ONAP TSC Charter DRAFT 6 6 Clean.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 107976 bytes Desc: ONAP TSC Charter DRAFT 6 6 Clean.docx URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170405/498a27df/attachment-0001.docx>
