Re: [onap-tsc] Clarifying the plan for developer gathering at ONS

[Alla Goldner]

Hi Phil,

Thanks a lot for this information!

As we know, ONS attendants have to pay registration fees.
What is arrangement for those coming to attend ONAP meeting?


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D394EC.DBC882A0]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Phil Robb
Sent: Tuesday, January 23, 2018 8:50 PM
To: onap-tsc ; onap-disc...@lists.onap.org; Raymond 
Paik 
Subject: [onap-tsc] Clarifying the plan for developer gathering at ONS

Hello ONAP developers and TSC members:

I wanted to provide some clarity on the activities and timeframe we have to 
gather during ONS.

The developer event during ONS week will be from 8:00am to 6:00pm on Monday, 
March 26th, and 8:00am to 12:00 noon on Tuesday, March 27th.  From requests we 
have received we had also been investigating the possibility to extend the 
event into the proceeding Sunday, but we've determined that such an extension 
is not going to be possible.  That said, we still have the Monday/Tuesday time 
for formal presentations, as well as break out rooms and a developer lounge for 
continued meetings, discussions, and hacking at ONS during the rest of the week.

As we've mentioned before, we would like to take advantage of the fact that the 
communities from the different projects will be in the same place at the same 
time.  As such, we encourage you to propose sessions that can further 
cross-collaboration among the LFN projects.  We also recognize that there are 
plenty of project-specific topics that need to be discussed.  Please also 
propose those sessions for this event.

With the LFN formally announced today, we are working to get the LFN wiki site 
up and running as quickly as possible.  One of the first uses for this site 
will be the location for submitting your proposed talks and presentations for 
the developer event at ONS.  We apologize that it is not up quite yet but it 
will be up within the next 2 or 3 days.

Once the site is up, Ray Paik (cc-ed) will send out an email to all communities 
on where to find it along with a call-for-presentations for you to post your 
discussion and presentation topics.  Between February 9th and February 15th, we 
will convene the TAC representatives from the LFN projects to review the 
submissions and to form an outline/framework for the developer event, giving 
time for cross-project discussions, project-specific sessions, and a TAC 
meeting.  From there, we will work with each project TSC to prioritize 
project-specific sessions during the event.

I am looking forward to this first-of-its-kind event and the breadth and depth 
of discussions we will have during this week.  Please be preparing your topics 
over the coming days and submit them to the LFN wiki once it is live.

Best regards,

Phil.
--
Phil Robb
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-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
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Clarifying the plan for developer gathering at ONS

[Phil Robb]

Hello ONAP developers and TSC members:

I wanted to provide some clarity on the activities and timeframe we have to
gather during ONS.

The developer event during ONS week will be from 8:00am to 6:00pm on
Monday, March 26th, and 8:00am to 12:00 noon on Tuesday, March 27th.  From
requests we have received we had also been investigating the possibility to
extend the event into the proceeding Sunday, but we've determined that such
an extension is not going to be possible.  That said, we still have the
Monday/Tuesday time for formal presentations, as well as break out rooms
and a developer lounge for continued meetings, discussions, and hacking at
ONS during the rest of the week.

As we've mentioned before, we would like to take advantage of the fact that
the communities from the different projects will be in the same place at
the same time.  As such, we encourage you to propose sessions that can
further cross-collaboration among the LFN projects.  We also recognize that
there are plenty of project-specific topics that need to be discussed.
Please also propose those sessions for this event.

With the LFN formally announced today, we are working to get the LFN wiki
site up and running as quickly as possible.  One of the first uses for this
site will be the location for submitting your proposed talks and
presentations for the developer event at ONS.  We apologize that it is not
up quite yet but it will be up within the next 2 or 3 days.

Once the site is up, Ray Paik (cc-ed) will send out an email to all
communities on where to find it along with a call-for-presentations for you
to post your discussion and presentation topics.  Between February 9th and
February 15th, we will convene the TAC representatives from the LFN
projects to review the submissions and to form an outline/framework for the
developer event, giving time for cross-project discussions,
project-specific sessions, and a TAC meeting.  From there, we will work
with each project TSC to prioritize project-specific sessions during the
event.

I am looking forward to this first-of-its-kind event and the breadth and
depth of discussions we will have during this week.  Please be preparing
your topics over the coming days and submit them to the LFN wiki once it is
live.

Best regards,

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

[onap-tsc] Committer Promotion Request for [Logging-Anaytics] - Luke Parker

[Michael O'Brien]

Hello TSC,
I would like to request that the ONAP TSC consider the Committer Promotion 
Luke Parker for the Logging-Analytics project.
The 2 active committers have voted, I have posted the results and details 
of the commit and contribution history to the page below and added an item on 
the next TSC agenda

https://wiki.onap.org/pages/viewpage.action?pageId=19202311

https://wiki.onap.org/display/DW/TSC+2018-01-25+Meeting+Agenda


Michael O'Brien
Amdocs Technology
16135955268
55268
[amdocs-a]


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

[onap-tsc] Committer Promotion Request for [Logging-Anaytics] - Michael O'Brien

[Michael O'Brien]

Hello TSC,
I would like to request that the ONAP TSC consider the Committer Promotion 
of Michael O'Brien (myself) for the Logging-Analytics project.
The 2 active committers have voted, I have posted the results and details 
of the commit and contribution history to the page below and added an item on 
the next TSC agenda

https://wiki.onap.org/pages/viewpage.action?pageId=25428014

This committer promotion will also unblock the pending PTL request from 
20171130
https://wiki.onap.org/display/DW/Michael+O%27Brien+PTL+vote+notes
https://wiki.onap.org/display/DW/TSC+2017-11-30

I have also posted details of the PTL promotion request that is pending on 
this committer request in the next TSC agenda
https://wiki.onap.org/display/DW/TSC+2018-01-25+Meeting+Agenda


Michael O'Brien
Amdocs Technology
16135955268
55268
[amdocs-a]

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

[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

[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 <
>