subject:"Re\: \[onap\-tsc\] We need to decide how to populate the ONAP Representative to the LFN TAC"

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-23 Thread Frank Brockners (fbrockne)

Hi Phil,

Thanks for putting forward a recommendation. I support your suggested approach.

Regards, Frank

From: Phil Robb [mailto:pr...@linuxfoundation.org]
Sent: Dienstag, 23. Januar 2018 14:16
To: CHAWKI Jamil IMT/OLN 
Cc: Stephen Terrill ; Frank Brockners (fbrockne) 
; GILBERT, MAZIN E (MAZIN E) ; Alla 
Goldner ; Gadiyar, Rajesh ; 
onap-tsc@lists.onap.org P ; 
onap-tsc-boun...@lists.onap.org
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Hello All:

I appreciate everyone's thoughtful discussion on the topic.

This may be anecdotal evidence, but I note that OPNFV, and FD.io, who both 
still have TSCs populated by Platinum Designates chose to have the TSC Chair be 
the TAC representative (our option #1), while ODL, who has a fully 
community-elected TSC chose to allow any Committer to self-nominate and run 
(our option #3).  I have noticed that the ODL TSC, since being fully elected, 
often leans toward the broadest, most inclusive election process for most 
decisions.  I believe they assume that in the end the community will make the 
right choice if given the opportunity to choose.. including electing the TSC 
Chair for the TAC position if he/she runs for it... after all, the person got 
elected to the highest position within the project by the same method.

For ONAP, it may make sense to have Mazin fill the TAC representative role as 
TSC Chair (since he has indicated he is willing and able) until after the 
Beijing release.  Once we elect a new TSC post Beijing, let's give them the 
opportunity to discuss and agree upon the best way to populate the TAC Rep. for 
ONAP going forward from there.

If that idea resonates with the TSC, then I suggest we put a vote up for that 
during the TSC meeting this week.  ONAP is the last to decide their method, and 
I would like to get the first TAC meeting scheduled ASAP.

Best,

Phil.

On Tue, Jan 23, 2018 at 12:29 PM, 
> wrote:
Hello
I agree with Steve that we need  to select an option. Phil do you have a 
proposal for selection?
Best
Jamil

Le 22 janv. 2018 à 23:45, Stephen Terrill 
> a écrit :
Hi,

Originally there were three proposals put on the table, have we settled on that:

  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
It sounds like we are settling on #2 but there were also voices for #1.

One approach is that after a TSC chair election and subsequent appointment, 
allow the TSC chair to decide to follow #1 or delegate it to the TSC #2 for 
that year.  If we were to agree with that, we should apply the same principle 
from now.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Frank Brockners (fbrockne)
Sent: 19 January 2018 08:11
To: GILBERT, MAZIN E (MAZIN E) 
>; Alla Goldner 
>; Gadiyar, Rajesh 
>; Phil Robb 
>
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc@lists.onap.org P 
>
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Thanks Mazin. Appreciated. IMHO it would be great if the TAC representative 
would also be part of the TSC.
Would it make sense to reassess the TAC representation post the composition of 
the a new TSC?

Thanks, Frank

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Donnerstag, 18. Januar 2018 19:03
To: Frank Brockners (fbrockne) >; 
Alla Goldner >; 
Gadiyar, Rajesh >; 
Phil Robb >
Cc: onap-tsc@lists.onap.org P 
>; 
onap-tsc-boun...@lists.onap.org
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Team,

I am happy to represent ONAP at TAC for one year. A new ONAP chair will need to 
be selected post Beijing release
so I will be stepping down as a Chair.

If there are several candidates who would like to represent

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-23 Thread Phil Robb

Hello All:

I appreciate everyone's thoughtful discussion on the topic.

This may be anecdotal evidence, but I note that OPNFV, and FD.io, who both
still have TSCs populated by Platinum Designates chose to have the TSC
Chair be the TAC representative (our option #1), while ODL, who has a fully
community-elected TSC chose to allow any Committer to self-nominate and run
(our option #3).  I have noticed that the ODL TSC, since being fully
elected, often leans toward the broadest, most inclusive election process
for most decisions.  I believe they assume that in the end the community
will make the right choice if given the opportunity to choose.. including
electing the TSC Chair for the TAC position if he/she runs for it... after
all, the person got elected to the highest position within the project by
the same method.

For ONAP, it may make sense to have Mazin fill the TAC representative role
as TSC Chair (since he has indicated he is willing and able) until after
the Beijing release.  Once we elect a new TSC post Beijing, let's give them
the opportunity to discuss and agree upon the best way to populate the TAC
Rep. for ONAP going forward from there.

If that idea resonates with the TSC, then I suggest we put a vote up for
that during the TSC meeting this week.  ONAP is the last to decide their
method, and I would like to get the first TAC meeting scheduled ASAP.

Best,

Phil.



On Tue, Jan 23, 2018 at 12:29 PM,  wrote:

> Hello
> I agree with Steve that we need  to select an option. Phil do you have a
> proposal for selection?
> Best
> Jamil
>
> Le 22 janv. 2018 à 23:45, Stephen Terrill 
> a écrit :
>
> Hi,
>
>
>
> Originally there were three proposals put on the table, have we settled on
> that:
>
>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
>
>
> It sounds like we are settling on #2 but there were also voices for #1.
>
>
>
> One approach is that after a TSC chair election and subsequent
> appointment, allow the TSC chair to decide to follow #1 or delegate it to
> the TSC #2 for that year.  If we were to agree with that, we should apply
> the same principle from now.
>
>
>
> BR,
>
>
>
> Steve
>
>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *Frank
> Brockners (fbrockne)
> *Sent:* 19 January 2018 08:11
> *To:* GILBERT, MAZIN E (MAZIN E) ; Alla Goldner <
> alla.gold...@amdocs.com>; Gadiyar, Rajesh ;
> Phil Robb 
> *Cc:* onap-tsc-boun...@lists.onap.org; onap-tsc@lists.onap.org P <
> onap-tsc@lists.onap.org>
> *Subject:* Re: [onap-tsc] We need to decide how to populate the ONAP
> Representative to the LFN TAC
>
>
>
> Thanks Mazin. Appreciated. IMHO it would be great if the TAC
> representative would also be part of the TSC.
>
> Would it make sense to reassess the TAC representation post the
> composition of the a new TSC?
>
>
>
> Thanks, Frank
>
>
>
> *From:* GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com
> ]
> *Sent:* Donnerstag, 18. Januar 2018 19:03
> *To:* Frank Brockners (fbrockne) ; Alla Goldner <
> alla.gold...@amdocs.com>; Gadiyar, Rajesh ;
> Phil Robb 
> *Cc:* onap-tsc@lists.onap.org P ;
> onap-tsc-boun...@lists.onap.org
> *Subject:* Re: [onap-tsc] We need to decide how to populate the ONAP
> Representative to the LFN TAC
>
>
>
> Team,
>
>
>
> I am happy to represent ONAP at TAC for one year. A new ONAP chair will
> need to be selected post Beijing release
>
> so I will be stepping down as a Chair.
>
>
>
> If there are several candidates who would like to represent ONAP at TAC
> then I suggest we go for a vote.
>
> Phil can help us to start a nomination and voting process.
>
>
>
> Mazin
>
>
>
>
>
>
>
> On Jan 18, 2018, at 7:27 AM, Frank Brockners (fbrockne) <
> fbroc...@cisco.com> wrote:
>
>
>
> 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:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *Alla
> Goldner
> *Sent:* Donnerstag, 11. Januar 2018 21:41
> *To:* Phil Robb ; Gadiyar, Rajesh <
>

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-22 Thread jamil.chawki

Hello
I agree with Steve that we need  to select an option. Phil do you have a 
proposal for selection?
Best
Jamil

Le 22 janv. 2018 à 23:45, Stephen Terrill 
> a écrit :

Hi,

Originally there were three proposals put on the table, have we settled on that:

  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

It sounds like we are settling on #2 but there were also voices for #1.

One approach is that after a TSC chair election and subsequent appointment, 
allow the TSC chair to decide to follow #1 or delegate it to the TSC #2 for 
that year.  If we were to agree with that, we should apply the same principle 
from now.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Frank Brockners (fbrockne)
Sent: 19 January 2018 08:11
To: GILBERT, MAZIN E (MAZIN E) 
>; Alla Goldner 
>; Gadiyar, Rajesh 
>; Phil Robb 
>
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc@lists.onap.org P 
>
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Thanks Mazin. Appreciated. IMHO it would be great if the TAC representative 
would also be part of the TSC.
Would it make sense to reassess the TAC representation post the composition of 
the a new TSC?

Thanks, Frank

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Donnerstag, 18. Januar 2018 19:03
To: Frank Brockners (fbrockne) >; 
Alla Goldner >; 
Gadiyar, Rajesh >; 
Phil Robb >
Cc: onap-tsc@lists.onap.org P 
>; 
onap-tsc-boun...@lists.onap.org
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Team,

I am happy to represent ONAP at TAC for one year. A new ONAP chair will need to 
be selected post Beijing release
so I will be stepping down as a Chair.

If there are several candidates who would like to represent ONAP at TAC then I 
suggest we go for a vote.
Phil can help us to start a nomination and voting process.

Mazin

On Jan 18, 2018, at 7:27 AM, Frank Brockners (fbrockne) 
> wrote:

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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Donnerstag, 11. Januar 2018 21:41
To: Phil Robb >; 
Gadiyar, Rajesh >
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc >
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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh >
Cc: onap-tsc >; 
onap-tsc-boun...@lists.onap.org
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,

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-22 Thread Stephen Terrill

Hi,

Originally there were three proposals put on the table, have we settled on that:

  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

It sounds like we are settling on #2 but there were also voices for #1.

One approach is that after a TSC chair election and subsequent appointment, 
allow the TSC chair to decide to follow #1 or delegate it to the TSC #2 for 
that year.  If we were to agree with that, we should apply the same principle 
from now.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Frank Brockners (fbrockne)
Sent: 19 January 2018 08:11
To: GILBERT, MAZIN E (MAZIN E) ; Alla Goldner 
; Gadiyar, Rajesh ; Phil 
Robb 
Cc: onap-tsc-boun...@lists.onap.org; onap-tsc@lists.onap.org P 

Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Thanks Mazin. Appreciated. IMHO it would be great if the TAC representative 
would also be part of the TSC.
Would it make sense to reassess the TAC representation post the composition of 
the a new TSC?

Thanks, Frank

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Donnerstag, 18. Januar 2018 19:03
To: Frank Brockners (fbrockne) >; 
Alla Goldner >; 
Gadiyar, Rajesh >; 
Phil Robb >
Cc: onap-tsc@lists.onap.org P 
>; 
onap-tsc-boun...@lists.onap.org
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Team,

I am happy to represent ONAP at TAC for one year. A new ONAP chair will need to 
be selected post Beijing release
so I will be stepping down as a Chair.

If there are several candidates who would like to represent ONAP at TAC then I 
suggest we go for a vote.
Phil can help us to start a nomination and voting process.

Mazin

On Jan 18, 2018, at 7:27 AM, Frank Brockners (fbrockne) 
> wrote:

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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Donnerstag, 11. Januar 2018 21:41
To: Phil Robb >; 
Gadiyar, Rajesh >
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc >
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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh >
Cc: onap-tsc >; 
onap-tsc-boun...@lists.onap.org
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>,

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-18 Thread Frank Brockners (fbrockne)

Thanks Mazin. Appreciated. IMHO it would be great if the TAC representative 
would also be part of the TSC.
Would it make sense to reassess the TAC representation post the composition of 
the a new TSC?

Thanks, Frank

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Donnerstag, 18. Januar 2018 19:03
To: Frank Brockners (fbrockne) ; Alla Goldner 
; Gadiyar, Rajesh ; Phil 
Robb 
Cc: onap-tsc@lists.onap.org P ; 
onap-tsc-boun...@lists.onap.org
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

Team,

I am happy to represent ONAP at TAC for one year. A new ONAP chair will need to 
be selected post Beijing release
so I will be stepping down as a Chair.

If there are several candidates who would like to represent ONAP at TAC then I 
suggest we go for a vote.
Phil can help us to start a nomination and voting process.

Mazin

On Jan 18, 2018, at 7:27 AM, Frank Brockners (fbrockne) 
> wrote:

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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Donnerstag, 11. Januar 2018 21:41
To: Phil Robb >; 
Gadiyar, Rajesh >
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc >
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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh >
Cc: onap-tsc >; 
onap-tsc-boun...@lists.onap.org
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >

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 
>
To:"HU, BIN" >, Phil Robb 
>, onap-tsc 
>
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-18 Thread Lisa Caywood

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) <
fbroc...@cisco.com> 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:lcayw...@linuxfoundation.org]
> *Sent:* Donnerstag, 18. Januar 2018 17:59
> *To:* Frank Brockners (fbrockne) 
> *Cc:* Alla Goldner ; Phil Robb <
> pr...@linuxfoundation.org>; Gadiyar, Rajesh ;
> onap-tsc ; onap-tsc-boun...@lists.onap.org
> *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) <
> fbroc...@cisco.com> 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' ; Phil Robb <
> pr...@linuxfoundation.org>; Gadiyar, Rajesh 
> *Cc:* onap-tsc-boun...@lists.onap.org; onap-tsc 
> *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:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *Alla
> Goldner
> *Sent:* Donnerstag, 11. Januar 2018 21:41
> *To:* Phil Robb ; Gadiyar, Rajesh <
> rajesh.gadi...@intel.com>
> *Cc:* onap-tsc-boun...@lists.onap.org; onap-tsc 
> *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:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *Phil Robb
> *Sent:* Thursday, January 11, 2018 9:24 PM
> *To:* Gadiyar, Rajesh 
> *Cc:* onap-tsc ; onap-tsc-boun...@lists.onap.org
> *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 <
> rajesh.gadi...@intel.com> wrote:
>
> +1
>
>
>
> *From: * on behalf of Jason Hunt <
> djh...@us.ibm.com>
> *Date: *Thursday, January 11, 2018 at 9:38 AM
> *To: *Dhananjay Pavgi 
> *Cc: *"onap-tsc-boun...@lists.onap.org" ,
> onap-tsc 
>
>
> *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: djh...@us.ibm.com
> Twitter:

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-18 Thread GILBERT, MAZIN E (MAZIN E)

Team,

I am happy to represent ONAP at TAC for one year. A new ONAP chair will need to 
be selected post Beijing release
so I will be stepping down as a Chair.

If there are several candidates who would like to represent ONAP at TAC then I 
suggest we go for a vote.
Phil can help us to start a nomination and voting process.

Mazin

On Jan 18, 2018, at 7:27 AM, Frank Brockners (fbrockne) 
> wrote:

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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Donnerstag, 11. Januar 2018 21:41
To: Phil Robb >; 
Gadiyar, Rajesh >
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc >
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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh >
Cc: onap-tsc >; 
onap-tsc-boun...@lists.onap.org
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >

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 
>
To:"HU, BIN" >, Phil Robb 
>, onap-tsc 
>
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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 >; 
onap-tsc >
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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-18 Thread Frank Brockners (fbrockne)

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:lcayw...@linuxfoundation.org]
Sent: Donnerstag, 18. Januar 2018 17:59
To: Frank Brockners (fbrockne) 
Cc: Alla Goldner ; Phil Robb 
; Gadiyar, Rajesh ; 
onap-tsc ; onap-tsc-boun...@lists.onap.org
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) 
> 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' >; 
Phil Robb >; 
Gadiyar, Rajesh >
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc >
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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Donnerstag, 11. Januar 2018 21:41
To: Phil Robb >; 
Gadiyar, Rajesh >
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc >
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

[cid:image001.png@01D3908B.27C03C40]

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh >
Cc: onap-tsc >; 
onap-tsc-boun...@lists.onap.org
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >

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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-18 Thread Lisa Caywood

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) <
fbroc...@cisco.com> 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' ; Phil Robb <
> pr...@linuxfoundation.org>; Gadiyar, Rajesh 
> *Cc:* onap-tsc-boun...@lists.onap.org; onap-tsc 
> *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:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *Alla
> Goldner
> *Sent:* Donnerstag, 11. Januar 2018 21:41
> *To:* Phil Robb ; Gadiyar, Rajesh <
> rajesh.gadi...@intel.com>
> *Cc:* onap-tsc-boun...@lists.onap.org; onap-tsc 
> *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:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *Phil Robb
> *Sent:* Thursday, January 11, 2018 9:24 PM
> *To:* Gadiyar, Rajesh 
> *Cc:* onap-tsc ; onap-tsc-boun...@lists.onap.org
> *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 <
> rajesh.gadi...@intel.com> wrote:
>
> +1
>
>
>
> *From: * on behalf of Jason Hunt <
> djh...@us.ibm.com>
> *Date: *Thursday, January 11, 2018 at 9:38 AM
> *To: *Dhananjay Pavgi 
> *Cc: *"onap-tsc-boun...@lists.onap.org" ,
> onap-tsc 
>
>
> *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: djh...@us.ibm.com
> Twitter: @DJHunt
>
>
>
>
> From:Dhananjay Pavgi 
> To:"HU, BIN" , Phil Robb <
> pr...@linuxfoundation.org>, onap-tsc 
> Date:01/11/2018 11:00 AM
> Subject:Re: [onap-tsc] We need to decide how to populate
>  theONAPRepresentative 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 <+91%2098220%2022264>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *HU, BIN
> * Sent:* Thursday, January 11, 2018 10:24 PM
> * To:* Phil Robb ; 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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-18 Thread Frank Brockners (fbrockne)

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' ; Phil Robb 
; Gadiyar, Rajesh 
Cc: onap-tsc-boun...@lists.onap.org; onap-tsc 
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: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Donnerstag, 11. Januar 2018 21:41
To: Phil Robb >; 
Gadiyar, Rajesh >
Cc: onap-tsc-boun...@lists.onap.org; 
onap-tsc >
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

[cid:image001.png@01D3906E.96CDFA40]

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh >
Cc: onap-tsc >; 
onap-tsc-boun...@lists.onap.org
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >

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 
>
To:"HU, BIN" >, Phil Robb 
>, onap-tsc 
>
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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 >; 
onap-tsc >
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.

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-18 Thread Frank Brockners (fbrockne)

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: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Donnerstag, 11. Januar 2018 21:41
To: Phil Robb ; Gadiyar, Rajesh 

Cc: onap-tsc-boun...@lists.onap.org; onap-tsc 
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

[cid:image001.png@01D39060.09F2E5D0]

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh >
Cc: onap-tsc >; 
onap-tsc-boun...@lists.onap.org
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >

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 
>
To:"HU, BIN" >, Phil Robb 
>, onap-tsc 
>
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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 >; 
onap-tsc >
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]
 On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 7:08 AM
To: onap-tsc >
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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Alla Goldner

Yes.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology

[cid:image001.png@01D38B2D.4DC79130]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 9:24 PM
To: Gadiyar, Rajesh 
Cc: onap-tsc ; onap-tsc-boun...@lists.onap.org
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >

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 
>
To:"HU, BIN" >, Phil Robb 
>, onap-tsc 
>
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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 >; 
onap-tsc >
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]
 On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 7:08 AM
To: onap-tsc >
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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread jamil.chawki

Hi Phil
I am in favor with your proposal for #2

Best
Jamil

Le 11 janv. 2018 à 16:08, Phil Robb 
> a écrit :

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
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Gadiyar, Rajesh

Yes.

--
Regards,
Rajesh

From: Phil Robb 
Date: Thursday, January 11, 2018 at 11:23 AM
To: Rajesh Gadiyar 
Cc: Jason Hunt , Dhananjay Pavgi 
, onap-tsc , 
"onap-tsc-boun...@lists.onap.org" 
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 
> wrote:
+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >

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 
To:"HU, BIN" >, Phil Robb 
>, onap-tsc 
>
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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 >; 
onap-tsc >
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]
 On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 7:08 AM
To: onap-tsc >
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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Phil Robb

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 
wrote:

> +1
>
>
>
> *From: * on behalf of Jason Hunt <
> djh...@us.ibm.com>
> *Date: *Thursday, January 11, 2018 at 9:38 AM
> *To: *Dhananjay Pavgi 
> *Cc: *"onap-tsc-boun...@lists.onap.org" ,
> onap-tsc 
>
> *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: djh...@us.ibm.com
> Twitter: @DJHunt
>
>
>
>
> From:Dhananjay Pavgi 
> To:"HU, BIN" , Phil Robb <
> pr...@linuxfoundation.org>, onap-tsc 
> Date:01/11/2018 11:00 AM
> Subject:Re: [onap-tsc] We need to decide how to populate
>  theONAPRepresentative 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 <+91%2098220%2022264>
>
> *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@
> lists.onap.org ] *On Behalf Of *HU, BIN
> * Sent:* Thursday, January 11, 2018 10:24 PM
> * To:* Phil Robb ; 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-bounces@
> lists.onap.org ] *On Behalf Of *Phil Robb
> * Sent:* Thursday, January 11, 2018 7:08 AM
> * To:* onap-tsc 
> * 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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Alla Goldner

+1

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D38B1C.743E4720]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Gadiyar, Rajesh
Sent: Thursday, January 11, 2018 7:41 PM
To: Jason Hunt ; Dhananjay Pavgi 

Cc: onap-tsc ; onap-tsc-boun...@lists.onap.org
Subject: Re: [onap-tsc] We need to decide how to populate the ONAP 
Representative to the LFN TAC

+1

From: > 
on behalf of Jason Hunt >
Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
>
Cc: "onap-tsc-boun...@lists.onap.org" 
>, 
onap-tsc >
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 
>
To:"HU, BIN" >, Phil Robb 
>, onap-tsc 
>
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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 >; 
onap-tsc >
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]
 On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 7:08 AM
To: onap-tsc >
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

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Gadiyar, Rajesh

+1

From:  on behalf of Jason Hunt 

Date: Thursday, January 11, 2018 at 9:38 AM
To: Dhananjay Pavgi 
Cc: "onap-tsc-boun...@lists.onap.org" , 
onap-tsc 
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 
To:"HU, BIN" , Phil Robb , 
onap-tsc 
Date:01/11/2018 11:00 AM
Subject:Re: [onap-tsc] We need to decide how to populatethe 
   ONAPRepresentative 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 ; onap-tsc 
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]
 On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 7:08 AM
To: onap-tsc >
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.htmlexternally

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Jason Hunt

#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 
To: "HU, BIN" , Phil Robb , 
onap-tsc 
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 ; onap-tsc 

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] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 7:08 AM
To: onap-tsc 
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 externally 
http://tim.techmahindra.com/tim/disclaimer.html 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=DwICAg=jf_iaSHvJObTbx-siA1ZOg=oMOO2HmZ8JJWvUc1M7SklmdX3xn2mSb9tP9VrdTjcqg=xpb9iDaHZ3rFPDWWGLuq3g2AEaY4_V7LmX4ofC3h2c8=Rj707DwdiZ15hmPuDPNts-w6YrmXMiWMBDuvzGn82ow=





___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Dhananjay Pavgi

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 ; onap-tsc 
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] On Behalf Of Phil Robb
Sent: Thursday, January 11, 2018 7:08 AM
To: onap-tsc >
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 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

2018-01-11 Thread Christopher Donley (Chris)

Thanks Phil.  I agree with your recommendation – I would prefer #2, as well.

Thanks,
Chris

From: 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 
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
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

Re: [onap-tsc] We need to decide how to populate the ONAP Representative to the LFN TAC

20 matches

Site Navigation

Mail list logo

Footer information