Bin, Separate from my factual statements, I do have opinions rooted in experience in multiple communities on the matter ;)
I do think coordinators are a good idea. There is a *lot* to coordinate across projects, and cross project coordination is the job of the TSC. In my experience in the absence of a mechanism like coordinators, particularly early in a project's life, there is a tendency for folks to turn to the TSC Chair for all of these purposes. No one (or even two or three) person has sufficient time to do this well, and no one (or even two or three) have the right set of skills and background to properly handle all of these coordinations. I've seen (and been) TSC Chairs in other projects trying... it is hard on the Chair, and produces suboptimal results. For this reason, I do support coordinators. Ed On Thu, Apr 13, 2017 at 6:48 AM, HU, BIN <bh526r at att.com> wrote: > 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 J > > > > Thanks > > Bin > > *From:* Ed Warnicke [mailto:hagbard at gmail.com] > *Sent:* Thursday, April 13, 2017 6:20 AM > *To:* HU, BIN <bh526r at att.com> > *Cc:* Ning.So at ril.com; stephen.terrill at ericsson.com; > 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> 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@ > lists.onap.org] *On Behalf Of *Ning.So at ril.com > *Sent:* Monday, April 10, 2017 12:11 PM > *To:* stephen.terrill at ericsson.com; 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@ > lists.onap.org] *On Behalf Of *Stephen Terrill > *Sent:* Monday, April 10, 2017 1:36 PM > *To:* 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: 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 <+34%20609%2016%2085%2015> > 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: 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 > 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/ab06caf2/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 386 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170413/ab06caf2/attachment-0002.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 804 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170413/ab06caf2/attachment-0003.jpg>
