Actually, the MAC will need to discuss and agree on a process for forming the workgroups that report to it. I have recommendations for what that should look like, which I'll be sharing with the group when we meet next week, but the MAC will need to debate and agree upon them.
The Project workgroups will continue to be the point of contact for their respective TSCs. There is no action needed here from the TSC side. Cheers, Lisa On Thu, Jan 18, 2018 at 9:35 AM, Frank Brockners (fbrockne) < [email protected]> wrote: > Hi Lisa, > > > > thanks – I didn’t mean to say that the TSC has to choose a MAC > representative. I just meant that “the technical project” (i.e. ONAP) needs > a representative on the MAC, and hence we (as a community) need to figure > out how to choose this representative. > > > > Regards, Frank > > > > *From:* Lisa Caywood [mailto:[email protected]] > *Sent:* Donnerstag, 18. Januar 2018 17:59 > *To:* Frank Brockners (fbrockne) <[email protected]> > *Cc:* Alla Goldner <[email protected]>; Phil Robb < > [email protected]>; Gadiyar, Rajesh <[email protected]>; > onap-tsc <[email protected]>; [email protected] > *Subject:* Re: [onap-tsc] We need to decide how to populate the ONAP > Representative to the LFN TAC > > > > Frank, this is not accurate. There will be workgroups under the MAC > focused on Project-level marketing. It's my expectation that those > workgroups will liaise regularly with their corresponding TSCs as has been > the case all along. And those workgroups also report to the MAC. But TSCs > do not need to have representatives on the MAC. > > > > Regards, Lisa > > > > On Thu, Jan 18, 2018 at 6:11 AM, Frank Brockners (fbrockne) < > [email protected]> wrote: > > BTW/ - on a related topic – from what I understand, the marketing > committee (MAC) is also to include 1 rep from each Technical Project (where > possible): We probably also need to choose a representative for the MAC. > > > > Frank > > > > *From:* Frank Brockners (fbrockne) > *Sent:* Donnerstag, 18. Januar 2018 13:27 > *To:* 'Alla Goldner' <[email protected]>; Phil Robb < > [email protected]>; Gadiyar, Rajesh <[email protected]> > *Cc:* [email protected]; onap-tsc <[email protected]> > *Subject:* RE: [onap-tsc] We need to decide how to populate the ONAP > Representative to the LFN TAC > > > > Given that during the transition period into the LFN structure some > continuity would make sense, #1 would be the straight-forward choice, > assuming that Mazin has the cycles (Mazin, any thoughts?). Once we move to > a newly composed TSC in May, we could also re-assess the question how we’d > choose the TAC representative for ONAP. > > BTW/ - several other communities, .e.g. FD.io and OPNFV went with the same > approach – i.e. have the TSC chair also be the TAC representative. > > > > Regards, Frank > > > > *From:* [email protected] [mailto:onap-tsc-bounces@ > lists.onap.org <[email protected]>] *On Behalf Of *Alla > Goldner > *Sent:* Donnerstag, 11. Januar 2018 21:41 > *To:* Phil Robb <[email protected]>; Gadiyar, Rajesh < > [email protected]> > *Cc:* [email protected]; onap-tsc <[email protected]> > *Subject:* Re: [onap-tsc] We need to decide how to populate the ONAP > Representative to the LFN TAC > > > > Yes. > > > > Best regards, > > > > *Alla Goldner* > > > > Open Network Division > > Amdocs Technology > > > > > > > > *From:* [email protected] [mailto:onap-tsc-bounces@ > lists.onap.org <[email protected]>] *On Behalf Of *Phil Robb > *Sent:* Thursday, January 11, 2018 9:24 PM > *To:* Gadiyar, Rajesh <[email protected]> > *Cc:* onap-tsc <[email protected]>; [email protected] > *Subject:* Re: [onap-tsc] We need to decide how to populate the ONAP > Representative to the LFN TAC > > > > Hello Rajesh and Alla: > > > > Just so I'm clear on your +1s, you are agreeing with Jason's comment, with > a preference for #1 unless the TSC Chair does not want to sign up for the > responsibility, in which case we move to #2? > > > > Best, > > > > Phil. > > > > On Thu, Jan 11, 2018 at 12:41 PM, Gadiyar, Rajesh < > [email protected]> wrote: > > +1 > > > > *From: *<[email protected]> on behalf of Jason Hunt < > [email protected]> > *Date: *Thursday, January 11, 2018 at 9:38 AM > *To: *Dhananjay Pavgi <[email protected]> > *Cc: *"[email protected]" <[email protected]>, > onap-tsc <[email protected]> > > > *Subject: *Re: [onap-tsc] We need to decide how to populate the ONAP > Representative to the LFN TAC > > > > #1 makes the most sense to me, but if Mazin feels it's too much for the > chair to take on, #2 is a fine backup option. > > > Regards, > Jason Hunt > Executive Software Architect, IBM > > Phone: 314-749-7422 <(314)%20749-7422> > Email: [email protected] > Twitter: @DJHunt > > > > > From: Dhananjay Pavgi <[email protected]> > To: "HU, BIN" <[email protected]>, Phil Robb < > [email protected]>, onap-tsc <[email protected]> > Date: 01/11/2018 11:00 AM > Subject: Re: [onap-tsc] We need to decide how to populate > the ONAP Representative to the LFN TAC > Sent by: [email protected] > ------------------------------ > > > > > Support Option 1; as TSC Chair for a particular stream has broader 360 > view of the program including roadmap, priorities etc. > > thanks & regards, > Dhananjay Pavgi > +91 98220 22264 <+91%2098220%2022264> > > *From:* [email protected] [mailto:onap-tsc-bounces@ > lists.onap.org <[email protected]>] *On Behalf Of *HU, BIN > * Sent:* Thursday, January 11, 2018 10:24 PM > * To:* Phil Robb <[email protected]>; onap-tsc < > [email protected]> > * Subject:* Re: [onap-tsc] We need to decide how to populate the ONAP > Representative to the LFN TAC > > Just FYI: > - OPNFV TSC voted on Tuesday (Jan 9) to have TSC Chair to > represent OPNFV in TAC > - fd.io voted the same today to have TSC Chair represent fd.io > in TAC, if I am not mistaken. > > Option 1 is used by both of our sister communities under the same LFN. > > Just an FYI. > > Thanks > Bin > > *From:* [email protected][mailto:onap-tsc-bounces@ > lists.onap.org <[email protected]>] *On Behalf Of *Phil Robb > * Sent:* Thursday, January 11, 2018 7:08 AM > * To:* onap-tsc <[email protected]> > * Subject:* [onap-tsc] We need to decide how to populate the ONAP > Representative to the LFN TAC > > Hello ONAP TSC Members: > > Now that ONAP is a part of the Linux Foundation Networking (LFN) Directed > Fund, we need to decide how we are going to populate our ONAP > Representative in the LFN Technical Advisory Council (TAC). > > As a reminder, the Scope of the responsibilities of the TAC are: > ===== > §Scope of responsibility > •Recommend acceptance or removal of projects under the Umbrella to be > approved by the Governing Board > •Focus on activities that drive collaboration and integration across > projects (e.g. collaborative development, testing, etc) > •Elected TAC Chair provides guidance to Governing Board on investment > needs of the project communities > > ===== > > Some of the options for us to populate our representative include: > 1) Just have the TSC Chair represent ONAP in the TAC > 2) Have the TSC vote for some TSC member to represent ONAP in the TAC > 3) Have the Committers vote for some Committer-At-Large to represent ONAP > in the TAC > ... etc. > > I will be setting up the first TAC meeting to occur somewhere in the last > third of January and it would be good for the ONAP community to have > representation from the start. > > I personally lean toward option #2 because a) it does not by default put > more burden on the TSC Chair unless they choose to run for the position, > and b) having the representative come from the TSC ensures that our > representative is up to speed on all TSC conversations that have occurred. > However, I certainly believe the other options are viable as well. > > Given our tight schedule during TSC meetings in the coming weeks, it would > be nice if we can come to a decision on this topic via email. Please > respond with your thoughts and opinions and based on the feedback received, > I'll try to put together a vote on this topic in about a week. > > Thanks, > > Phil. > -- > Phil Robb > VP Operations - Networking & Orchestration, The Linux Foundation > (O) 970-229-5949 <(970)%20229-5949> > (M) 970-420-4292 <(970)%20420-4292> > Skype: Phil.Robb > ============================================================ > ================================================================ > Disclaimer: This message and the information contained herein is > proprietary and confidential and subject to the Tech Mahindra policy > statement, you may review the policy at http://www.techmahindra.com/ > Disclaimer.html > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=oMOO2HmZ8JJWvUc1M7SklmdX3xn2mSb9tP9VrdTjcqg&m=xpb9iDaHZ3rFPDWWGLuq3g2AEaY4_V7LmX4ofC3h2c8&s=30ogMKHKBS9IsAwXSpwA14AW2fegZs1niPDeEYb-pxI&e=>externally > http://tim.techmahindra.com/tim/disclaimer.html > <https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=oMOO2HmZ8JJWvUc1M7SklmdX3xn2mSb9tP9VrdTjcqg&m=xpb9iDaHZ3rFPDWWGLuq3g2AEaY4_V7LmX4ofC3h2c8&s=raYJ1oNjvFg-1p7C7F2LfU4YNFjw1yHSBejxhQuwfes&e=>internally > within TechMahindra. > ============================================================ > ================================================================ > _______________________________________________ > ONAP-TSC mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r= > oMOO2HmZ8JJWvUc1M7SklmdX3xn2mSb9tP9VrdTjcqg&m= > xpb9iDaHZ3rFPDWWGLuq3g2AEaY4_V7LmX4ofC3h2c8&s=Rj707DwdiZ15hmPuDPNts- > w6YrmXMiWMBDuvzGn82ow&e= > > > _______________________________________________ > ONAP-TSC mailing list > [email protected] > https://lists.onap.org/mailman/listinfo/onap-tsc > > > > > > -- > > Phil Robb > > VP Operations - Networking & Orchestration, The Linux Foundation > > (O) 970-229-5949 <(970)%20229-5949> > > (M) 970-420-4292 <(970)%20420-4292> > > Skype: Phil.Robb > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer > > > _______________________________________________ > ONAP-TSC mailing list > [email protected] > https://lists.onap.org/mailman/listinfo/onap-tsc > > > > > > -- > > ______________ > > > > *Lisa Caywood* > > Director of Ecosystem Development > > OpenDaylight <https://www.opendaylight.org/> and ONAP > <https://www.onap.org/> Projects > > > > [email protected] > > +1 (408) 857-3642 <(408)%20857-3642> > > Skype: RealLisaC > > Twitter: @RealLisaC > -- ______________ *Lisa Caywood* Director of Ecosystem Development OpenDaylight <https://www.opendaylight.org/> and ONAP <https://www.onap.org/> Projects [email protected] +1 (408) 857-3642 Skype: RealLisaC Twitter: @RealLisaC
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
