[onap-tsc] Need to discuss Initial Project Committers, and PTL Elections at the next TSC meeting

[Phil Robb]

Hello ONAP TSC Members:

It has come to my attention that there are some questions and concerns from
community members regarding  the initial committer lists and subsequent PTL
elections for our newly formed sub-projects within ONAP.

When such issues arise within a sub-project, particularly when it is in
it's formative period, the TSC may be called upon to arbitrate and/or make
clear, the operating procedures/parameters for technical governance best
suited for all the sub-projects within the community.

I suggest that the TSC put this topic on the Agenda for the next TSC
meeting (July 6th) to discuss the issues raised and decide what, if any,
actions and/or further guidance need be provided to the ONAP sub-projects
as they are starting up.

I will be collecting further information on the issues raised as soon as
I'm back from vacation next week and will provide a summary of the
questions and concerns prior to the TSC meeting.

Thanks in advance for your help on this matter.

Best,

Phil.
-- 
Phil Robb
Executive Director, OpenDaylight Project
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] Committers and voting - Please read.

[MAHER, RANDA]

+1

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of SPATSCHECK, OLIVER
Sent: Friday, June 30, 2017 11:57 AM
To: Andrew Grimberg 
Cc: t...@lists.onap.org
Subject: Re: [onap-tsc] Committers and voting - Please read.

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
+1


On Jun 30, 2017, at 11:41 AM, Andrew Grimberg 
> wrote:

To help weed things down I would suggest that every repository in a
project be required to define a distinct list of committers and not
allow an umbrella project to define top level committers. That list may
be the same across several of them, but they should be distinct to each
repository and hold to the same configuration of just a few committers
per repository. It may mean a bit more administrative overhead for the
management, and definitely for the set-up but it will clearly define who
does, and does not have domain knowledge on a particular set of code.


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

[onap-tsc] Re： Corrective Action on Approved Project Proposals

[meng.zhaoxing1]

+1





发自我的zMail






 

 原始邮件
 
 

 

 

 

 
 发件人:
 KennyPaul 
 

 
 收件人:onap-tsc 
 

 
 日期:
 2017-06-30 03:12:59
 

 
 主题:[onap-tsc] Corrective Action on Approved Project Proposals
 

 

 

 TSC Members:


 

 
 

 

 The following are discrepancies and/or change requests in the approved 
versions of the Project Proposals have been identified during project 
infrastructure set up, which warrants your attention. To minimize email traffic 
I have consolidated these into a single message for your review. It is my 
recommendation that we pursue the necessary corrective action to maintain 
forward momentum.  In the event that any TSC member feels that any one of these 
items warrants further consideration/discussion please let me know and I will 
see that we address it a more formal fashion. 
 

 

 
 

 

 ACTION REQUIRED:  A +1, 0, -1 vote in response to this email will be deemed 
sufficient to cover all of these cases.
 

 

 
 

 

 Please let me know if you have any questions.
 

 

 
 

 
 
 
 
 
 
 
 
 
 
 
 Project 
 Descrepancy / Requested change 
 Corrective Action 
 
 
 Command Line Interface 
 Jira naming conflict with the Portal project  
 changing Jira Project name from PORTAL to CLI and Jira Prefix and Mailing list 
to CLI 
 
 
 
 
 
 
 
 University 
 conflicting repo naming within the different sections of the Proposal 
 setting repo name to onapuniversity 
 
 
 
 
 
 
 
 Software Defined Network Controller 
 - list of commiter names changed - addition of 2 repositories 
org.onap.sdnc/architecture org.onap.sdnc/features 
 Accept requested changes 
 
 
 
 
 
 
 
  Modeling 
 repository name change request- remove  “modeling” and replace with repos 
named “toscaparsers” and “yangvalidators” 
 Accept requested changes 
 
 
 
 
 
 
 
 MultiVIM/cloud: 
 Addition of 1 repository - windriver 
 Accept requested change 
 
 
 
 
 

 

 
 

 

 
 

 

 
 

 

 
 

 

 
 
 

 

 

 Best Regards, 
 -kenny
 
 
 Kenny Paul,  Technical Program Manager
 
 kp...@linuxfoundation.org
 
 510.766.5945___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Corrective Action on Approved Project Proposals

[Haiby, Ranny (Nokia - US/San Jose USA)]

+1

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Thursday, June 29, 2017 12:13 PM
To: onap-tsc 
Subject: [onap-tsc] Corrective Action on Approved Project Proposals

TSC Members:

The following are discrepancies and/or change requests in the approved versions 
of the Project Proposals have been identified during project infrastructure set 
up, which warrants your attention. To minimize email traffic I have 
consolidated these into a single message for your review. It is my 
recommendation that we pursue the necessary corrective action to maintain 
forward momentum.  In the event that any TSC member feels that any one of these 
items warrants further consideration/discussion please let me know and I will 
see that we address it a more formal fashion.

ACTION REQUIRED:  A +1, 0, -1 vote in response to this email will be deemed 
sufficient to cover all of these cases.

Please let me know if you have any questions.

Project

Descrepancy / Requested change

Corrective Action

Command Line Interface

Jira naming conflict with the Portal project

changing Jira Project name from PORTAL to CLI and Jira Prefix and Mailing list 
to CLI


University

conflicting repo naming within the different sections of the Proposal

setting repo name to onapuniversity


Software Defined Network Controller

- list of commiter names changed
- addition of 2 repositories
org.onap.sdnc/architecture
org.onap.sdnc/features

Accept requested changes


 Modeling

repository name change request- remove  “modeling” and replace with repos named 
“toscaparsers” and “yangvalidators”

Accept requested changes


MultiVIM/cloud:

Addition of 1 repository - windriver

Accept requested change





Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

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

Re: [onap-tsc] Committers and voting - Please read.

[Ed Warnicke]

Something else that helps a great deal is for the original author of the
proposal to be the gatekeeper on changes to the proposal, including adding
committers.  Wiki's are wonderful in that anyone can fix anything, but for
project proposals, editing them to shift without consent their intent or
original initial committer list is strongly at the root of the problem.  It
also allows the TSC to be *thoughtfully* flexible in places, because it can
then ask the proposer "Why do you have 6 committers?".  Sometimes there
*will* be a good reason, and in the situations where there isn't one... the
*fact* that the proposer knows they will be asked will likely lead to the
correct outcome long before it comes to the TSC.

Ed

On Fri, Jun 30, 2017 at 8:56 AM, SPATSCHECK, OLIVER (OLIVER) <
spat...@research.att.com> wrote:

> +1
>
>
> On Jun 30, 2017, at 11:41 AM, Andrew Grimberg <
> agrimb...@linuxfoundation.org> wrote:
>
> To help weed things down I would suggest that every repository in a
> project be required to define a distinct list of committers and not
> allow an umbrella project to define top level committers. That list may
> be the same across several of them, but they should be distinct to each
> repository and hold to the same configuration of just a few committers
> per repository. It may mean a bit more administrative overhead for the
> management, and definitely for the set-up but it will clearly define who
> does, and does not have domain knowledge on a particular set of code.
>
>
>
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-tsc
>
>
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Committers and voting - Please read.

[SPATSCHECK, OLIVER (OLIVER)]

+1


On Jun 30, 2017, at 11:41 AM, Andrew Grimberg 
> wrote:

To help weed things down I would suggest that every repository in a
project be required to define a distinct list of committers and not
allow an umbrella project to define top level committers. That list may
be the same across several of them, but they should be distinct to each
repository and hold to the same configuration of just a few committers
per repository. It may mean a bit more administrative overhead for the
management, and definitely for the set-up but it will clearly define who
does, and does not have domain knowledge on a particular set of code.


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

Re: [onap-tsc] Committers and voting - Please read.

[Andrew Grimberg]

On 06/30/2017 07:00 AM, SPATSCHECK, OLIVER  (OLIVER) wrote:

> I think the TSC needs to either step up and enforce it’s own rules or
> abandon the rule altogether. The current status quo punish people which
> play by the rules which I would think is not the intend of the TSC.
> 
> I would be interested to hear how the open source “gurus” have handled
> this in the past as I suspect this has happened before in other projects.

Oliver,

As you state, the TSC sort of needs to be more willing to vote -1 on
creation if the committer list is really bad. Our other communities have
generally held the line during the review process so don't really have
the problem. What we've seen instead is that as a project matures the
list may grow to be a bit larger than is initially thought to be good,
but the number of committers tends to flex up to what is needed instead
of trying to trim down.

What you end up needing to do is have the PTL start working on trimming
the committer list and have current committers voluntarily step down.

I'll also note, that the large lists of committers is also likely partly
a result of the umbrella project methodology of committer definition as
person X may need committer on sub-project Y but with how the lists are
currently defined, it's basically only at the top level umbrella level.

To help weed things down I would suggest that every repository in a
project be required to define a distinct list of committers and not
allow an umbrella project to define top level committers. That list may
be the same across several of them, but they should be distinct to each
repository and hold to the same configuration of just a few committers
per repository. It may mean a bit more administrative overhead for the
management, and definitely for the set-up but it will clearly define who
does, and does not have domain knowledge on a particular set of code.

-Andy-

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



signature.asc
Description: OpenPGP digital signature
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Committers and voting - Please read.

[SPATSCHECK, OLIVER (OLIVER)]

Mazin,

your email triggered me to actually go through the wiki and get some stats. I 
attached a spreadsheet with committers per company and project (I did this 
manually so there might be some minor mistakes but the trend holds). Also the 
companies are sorted by appearance so the order is random.

Seems the TSC has failed miserably enforcing it’s own policies.

The average number of committers is 8.6. The max is 26 the min is 1.  Based on 
the 27 approved projects on the wiki 15 are not in compliance of the policy. 
There are 10 projects with more then 10 committers.

Looking at some of the trends it seems to be a self feeding process one company 
adds more then the others don’t want to be “left out” and respond in kind. So 
it’s more driven by ego/politics then merit in most cases I can see.

I think the TSC needs to either step up and enforce it’s own rules or abandon 
the rule altogether. The current status quo punish people which play by the 
rules which I would think is not the intend of the TSC.

I would be interested to hear how the open source “gurus” have handled this in 
the past as I suspect this has happened before in other projects.

Oliver



On Jun 29, 2017, at 9:35 PM, GILBERT, MAZIN E (MAZIN E) 
> wrote:

*** Security Advisory: This Message Originated Outside of AT ***.
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

ONAP Community,

I have sent a note on this before, so my apology for sending it again.
It is important that this community follow the guidelines of the TSC on
committers and PTLs. We have provided guidelines that projects should
have between 3-5 committers that have actual development experience
and deep knowledge in the software or release software. While I love
the passion and involvement of the community, I see few projects that
misused those directions and ended up with committers in excess of 10, some
signed up the last minute to steer the PTL vote.

I hesitated to manage and clean-up the committers per advice from
the Linux Foundation, but I will ask the TSC to enforce those guidelines
in future to ensure fair outcomes across all projects.

Thank you.. I will soon share some great news of new exciting members who
are joining ONAP. Thank you again for your hard work to making ONAP
a success and let’s make the Amsterdam Release a blast.

Mazin

___
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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=rUHhj9ph_CQ3Np2G-F9zUffASbFXC8e__XGg_VFgjtE=AOatY2_khrWMjoCancKkJNqTK5U3Z5woGJ-3-uMx4jY=



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

[onap-tsc] [onap-discuss] The aproach of interact with External System. PTLs pay attention please

[li.zi30]

Hi PTLs,




Since each project have a PTL and acording to last TSC meeting, we still need 
feed back from SO/APP-C/ONAP SDN-C team. See detail for the table below.





I will set up a meeting next wednesday(9 PM China, 1 PM UTC, 9 AM US/Eastern, 
5th July ) to discuss about the approach of your project to interact with 
External system. If you can not attend, please call for a proxy or give me a 
feadback about the approach by email. 

If we still can not hear from you, I will send you an email alone and fwd this 
mail to Mazin and TSC members.





Scenario


External system to be provisioned


Baseline approach

Reflections Connection to cloud infra

Address and capabilities of VIM managers


(e.g. openstack port)

Mult-VIM: will register infrastructure site/location/region and their 
attributes and capabilities in A, including compute, storage, networking 
(including local and vendor SDN controllers) etc.
VID: manually input the VIM addresses and connection information to the portal, 
and sent this info to MSO which later call controllers which interact with all 
of these systems (VNFMS , VIM , EMS)
VF-C: query VIM addresses from ESR
SO: ?
Connection to transport

SDN controller address’s and capabilities

vendor sdn controler which managed by VIM is not in the scope of ESR. How about 
the vendor sdn controller managed by ONAP SDN-C?



ONAP SDN-C: ?


Connecting to S-VNFM

S-VNFM and capabilites

VF-C: query S-VNFM addresses from ESRCould be part of the tosca/heat   
templateEMS


(Element Management System)

EMS address and capabilitiesAPP-C: ?
Other





@Kenny, Can you set up a one-time session for ESR at 1 PM UTC, Wednesday, 5th 
July.




Thank You for Cooperation,

LiZi













李滋 lizi






IT开发工程师 IT Development
Engineer
网管及服务开发二部/中心研究院/系统产品 Network Management & Service Development Dept. II/Central 
R＆D Institute/System Product









成都市高新区天府大道中段800号中兴通讯大厦
ZTE
Corporation Building, No. 800 Middle Section Tianfu Avenue, 
Chengdu, P..R.China, 610041 
M: +86 15583405168 
E: li.z...@zte.com.cn 
www.zte.com.cn___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Corrective Action on Approved Project Proposals

[Jason Hunt]

+1

Regards,
Jason Hunt
Executive Software Architect
+1-314-749-7422
Twitter: @DJHunt

Sent from my iPhone

> On Jun 30, 2017, at 2:49 AM, Stephen Terrill  
> wrote:
> 
> +1
>  
> From: onap-tsc-boun...@lists.onap.org 
> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
> Sent: 29 June 2017 21:13
> To: onap-tsc 
> Subject: [onap-tsc] Corrective Action on Approved Project Proposals
>  
> TSC Members:
>  
> The following are discrepancies and/or change requests in the approved 
> versions of the Project Proposals have been identified during project 
> infrastructure set up, which warrants your attention. To minimize email 
> traffic I have consolidated these into a single message for your review. It 
> is my recommendation that we pursue the necessary corrective action to 
> maintain forward momentum.  In the event that any TSC member feels that any 
> one of these items warrants further consideration/discussion please let me 
> know and I will see that we address it a more formal fashion. 
>  
> ACTION REQUIRED:  A +1, 0, -1 vote in response to this email will be deemed 
> sufficient to cover all of these cases.
>  
> Please let me know if you have any questions.
>  
> Project
> Descrepancy / Requested change
> Corrective Action
> Command Line Interface
> Jira naming conflict with the Portal project 
> changing Jira Project name from PORTAL to CLI and Jira Prefix and Mailing 
> list to CLI
> University
> conflicting repo naming within the different sections of the Proposal
> setting repo name to onapuniversity
> Software Defined Network Controller
> - list of commiter names changed
> - addition of 2 repositories 
> org.onap.sdnc/architecture
> org.onap.sdnc/features
> Accept requested changes
>  Modeling
> repository name change request- remove  “modeling” and replace with repos 
> named “toscaparsers” and “yangvalidators”
> Accept requested changes
> MultiVIM/cloud:
> Addition of 1 repository - windriver
> Accept requested change
>  
>  
>  
>  
> Best Regards, 
> -kenny
> 
> Kenny Paul,  Technical Program Manager
> kp...@linuxfoundation.org
> 510.766.5945
>  

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

Re: [onap-tsc] Corrective Action on Approved Project Proposals

[Lingli Deng]

+1

 

Lingli

 

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: 2017年6月30日 15:50
To: Kenny Paul ; onap-tsc 
Subject: Re: [onap-tsc] Corrective Action on Approved Project Proposals

 

+1

 

From: onap-tsc-boun...@lists.onap.org   
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: 29 June 2017 21:13
To: onap-tsc  >
Subject: [onap-tsc] Corrective Action on Approved Project Proposals

 

TSC Members:

 

The following are discrepancies and/or change requests in the approved versions 
of the Project Proposals have been identified during project infrastructure set 
up, which warrants your attention. To minimize email traffic I have 
consolidated these into a single message for your review. It is my 
recommendation that we pursue the necessary corrective action to maintain 
forward momentum.  In the event that any TSC member feels that any one of these 
items warrants further consideration/discussion please let me know and I will 
see that we address it a more formal fashion. 

 

ACTION REQUIRED:  A +1, 0, -1 vote in response to this email will be deemed 
sufficient to cover all of these cases.

 

Please let me know if you have any questions.

 


Project

Descrepancy / Requested change

Corrective Action


Command Line Interface

Jira naming conflict with the Portal project 

changing Jira Project name from PORTAL to CLI and Jira Prefix and Mailing list 
to CLI



University

conflicting repo naming within the different sections of the Proposal

setting repo name to onapuniversity



Software Defined Network Controller

- list of commiter names changed
- addition of 2 repositories 
org.onap.sdnc/architecture
org.onap.sdnc/features

Accept requested changes



 Modeling

repository name change request- remove  “modeling” and replace with repos named 
“toscaparsers” and “yangvalidators”

Accept requested changes



MultiVIM/cloud:

Addition of 1 repository - windriver

Accept requested change

 

 

 

 

Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org  
510.766.5945

 

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

Re: [onap-tsc] Corrective Action on Approved Project Proposals

[Stephen Terrill]

+1

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: 29 June 2017 21:13
To: onap-tsc 
Subject: [onap-tsc] Corrective Action on Approved Project Proposals

TSC Members:

The following are discrepancies and/or change requests in the approved versions 
of the Project Proposals have been identified during project infrastructure set 
up, which warrants your attention. To minimize email traffic I have 
consolidated these into a single message for your review. It is my 
recommendation that we pursue the necessary corrective action to maintain 
forward momentum.  In the event that any TSC member feels that any one of these 
items warrants further consideration/discussion please let me know and I will 
see that we address it a more formal fashion.

ACTION REQUIRED:  A +1, 0, -1 vote in response to this email will be deemed 
sufficient to cover all of these cases.

Please let me know if you have any questions.

Project

Descrepancy / Requested change

Corrective Action

Command Line Interface

Jira naming conflict with the Portal project

changing Jira Project name from PORTAL to CLI and Jira Prefix and Mailing list 
to CLI


University

conflicting repo naming within the different sections of the Proposal

setting repo name to onapuniversity


Software Defined Network Controller

- list of commiter names changed
- addition of 2 repositories
org.onap.sdnc/architecture
org.onap.sdnc/features

Accept requested changes


 Modeling

repository name change request- remove  “modeling” and replace with repos named 
“toscaparsers” and “yangvalidators”

Accept requested changes


MultiVIM/cloud:

Addition of 1 repository - windriver

Accept requested change





Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

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