+1 From: <onap-tsc-boun...@lists.onap.org> on behalf of Jason Hunt <djh...@us.ibm.com> Date: Thursday, January 11, 2018 at 9:38 AM To: Dhananjay Pavgi <dp00476...@techmahindra.com> Cc: "onap-tsc-boun...@lists.onap.org" <onap-tsc-boun...@lists.onap.org>, onap-tsc <onap-tsc@lists.onap.org> 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 Email: djh...@us.ibm.com Twitter: @DJHunt From: Dhananjay Pavgi <dp00476...@techmahindra.com> To: "HU, BIN" <bh5...@att.com>, Phil Robb <pr...@linuxfoundation.org>, onap-tsc <onap-tsc@lists.onap.org> 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: onap-tsc-boun...@lists.onap.org ________________________________ 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 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of HU, BIN Sent: Thursday, January 11, 2018 10:24 PM To: Phil Robb <pr...@linuxfoundation.org>; onap-tsc <onap-tsc@lists.onap.org> 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: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: Thursday, January 11, 2018 7:08 AM To: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> 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 (M) 970-420-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 ONAP-TSC@lists.onap.org 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 ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
