[onap-tsc] Frank Brockners to be Cisco's Representative to the ONAP TSC

Frank Brockners will be taking over for me as Cisco’s ONAP TSC Representative. Please offer him a warm welcome next week in Paris :) Ed ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] More Help For Adding Committers

Could we add the history of meritocratic contribution via a link to a gerrit query for the proposed committers contributions to the repos of the project? Ed On Thu, Aug 17, 2017 at 6:40 PM, Kenny Paul wrote: > In a further effort to both ease frustration of the PTLs

[onap-tsc] Frank Brockner will be my proxy for the Aug 17 ONAP TSC meeting.

Frank Brockner will be my proxy for the Aug 17 ONAP TSC meeting. Ed ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Giles Heron to be my proxy at this weeks ONAP TSC

Giles Heron to be my proxy at this weeks ONAP TSC Ed ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

I do tend to agree with Oliver here. There is a process of simply getting existing code upstream at all. Ideally, this happens with all the 'seed' code for a project going out at project creation. Early on in communities, this is sometimes difficult for a variety of reasons. As communities

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

I think getting something like statckalytics going is goodness, but I don't think it gets to the upstream first issue. Look at David's original complaint about 10k LOC patches coming in, and it *hinting* at code being developed behind closed doors and being pushed up in batch. 2 10k LOC patches

[onap-tsc] Bruce Thompson to be my proxy for Jul 27 TSC meeting

Bruce Thompson will be my proxy for Jul 27 TSC meeting. Ed ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

+1 On Sun, Jul 23, 2017 at 6:45 AM, pinghe wrote: > > > 2017-07-23 2:49 GMT+08:00 Kenny Paul : > >> As mentioned we have several repository requests queued up. Gildas has >> reviewed these and feels the requestors have done their due diligence >>

Re: [onap-tsc] REMINDER - Re: Irregularities in the Use Case Subcommittee Chair Election

My general instinct is to avoid 'company thinking' in open source communities whenever possible. Not always possible... but a good rule of thumb. Ed On Tue, Jul 11, 2017 at 3:50 PM, Stephen Terrill < stephen.terr...@ericsson.com> wrote: > Hi, > > Having one to two votes per company/affiliate

Re: [onap-tsc] Irregularities in the Use Case Subcommittee Chair Election

gt; > > > > > *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@ > lists.onap.org] *On Behalf Of *Ed Warnicke > *Sent:* Friday, July 07, 2017 6:05 PM > *To:* Lingli Deng <denglin...@chinamobile.com> > *Cc:* onap-tsc <onap-tsc@lists.onap.org> > *Sub

Re: [onap-tsc] Irregularities in the Use Case Subcommittee Chair Election

, 2017 at 7:59 AM, Ed Warnicke <hagb...@gmail.com> wrote: > Thinking for the last few days around these issues. I think we have a > flaw in our governance around subcommittees. If you look at the charter: > > > On Fri, Jul 7, 2017 at 7:49 AM, Lingli Deng <denglin...@chinamobi

Re: [onap-tsc] Irregularities in the Use Case Subcommittee Chair Election

Thinking for the last few days around these issues. I think we have a flaw in our governance around subcommittees. If you look at the charter: On Fri, Jul 7, 2017 at 7:49 AM, Lingli Deng wrote: > Hi Phil and all, > > > > It is a pity that we did not have time to

Re: [onap-tsc] YOUR ACTION IS REQUIRED: A Project needs new repos for microservices

Could someone point me to the wiki page listing the AAI PTL? I looked at the AAI page: https://wiki.onap.org/display/DW/Active+and+Available+Inventory+Project I would expect this request to come from the AAI PTL... Ed On Fri, Jul 7, 2017 at 6:43 AM, Haiby, Ranny (Nokia - US/San Jose USA) <

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

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

[onap-tsc] Giles Heron will be my proxy for the Thu Jun 29 TSC meeting

Giles Heron will be my proxy for the Thu Jun 29 TSC meeting. Ed ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] External Open Source Coordinator Update

We have begun tracking engagements as well as contacts between ONAP and other Open Source Communities here: https://wiki.onap.org/display/DW/External+Open+Source+Community+Coordination in order to facilitate their identification so members of the ONAP community who need to work with those

Re: [onap-tsc] Special (and longer) TSC meeting this Thursday 6/22/17

I would request that we please respect the fd.io TSC meeting, which I chair, which is held at 8am PST, by extending the ONAP TSC meeting to two hours by starting it at 6am PST, rather than extending its ending to 9am PST. Ed On Wed, Jun 21, 2017 at 12:16 AM, Phil Robb

Re: [onap-tsc] [ONAP TSC VOTE] vCPE Residential Broadband Use Case For Release-1

+1 On Sat, Jun 17, 2017 at 11:26 AM, Gadiyar, Rajesh wrote: > -- > > > > Hello ONAP TSC Members: > > > > As we left it on the ONAP TSC call this week, please review and vote on > the vCPE Residential Broadband Use Case proposal for inclusion

[onap-tsc] Bruce Thompson is my proxy to the TSC at the ONAP F2F

Bruce Thompson is my proxy to the TSC at the ONAP F2F ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] External Open Source Contact Tracking Page

As part of coordinating External Open Source project interactions, I've created a wiki page for folks to list themselves if they have ties to other Open Source communities that may prove useful for members of the ONAP community to leverage:

Re: [onap-tsc] Common Frameworks - Project Proposal

ar how you guys think the community should align on > common frameworks and embed those in the core components. I think we all > share the same goal of making ONAP not just working, but also maintainable > and extendable. > > > > Thanx, > > Liron > > > > *Fro

Re: [onap-tsc] ONAP TSC Members - Are you Attending the China Face To Face Next Week?

-1 Ed On Fri, Jun 2, 2017 at 8:08 AM, Bob Monkman wrote: > +1 I will attend > > > > Robert (Bob) Monkman > > Networking Software Strategy & Ecosystem Programs > > ARM > > 150 Rose Orchard Way > > San Jose, Ca 95134 > > M: +1.510.676.5490 <(510)%20676-5490> > > Skype:

Re: [onap-tsc] Common Frameworks - Project Proposal

I second Zhaoxing's comments. A project should have a well defined, limited scope, for the reasons cited above as well as many others having to do with the overall health of the community. A DMaap project makes sense to me, AAA project, a Common Frameworks project does not. Ed On Thu, Jun 1,

Re: [onap-tsc] wiki and conference calls

g note. We are wondering if we should post these recording and > meeting notes, and if so, where? > > > > Danny > > > > *From: *<onap-tsc-boun...@lists.onap.org> on behalf of Ed Warnicke < > hagb...@gmail.com> > *Date: *Friday, May 26, 2017 at 8:35 AM >

Re: [onap-tsc] wiki and conference calls

+1k I would strongly suggest we adopt the community norm that its totally cool for teams to start calls/IRC channels but they *really* need to list them in a central index so people can find them. Aggressive Openness :) Ed On Fri, May 26, 2017 at 8:03 AM, SPATSCHECK, OLIVER (OLIVER) <

Re: [onap-tsc] Seed code for Service Orchestrator

In many other communities, as a matter of social norm, not governance, if one is going to edit a project proposal, it is considered good manners to ask the originator of a proposal before editing it in a substantive way. Perhaps we should consider communicating this social norm withing the ONAP

Re: [onap-tsc] [onap-discuss] Projects

this week the latest, we need the email to > TSC mailing list to “propose” the proposal. Is this understanding correct? > > > > Danny > > > > > > *From: *<onap-discuss-boun...@lists.onap.org> on behalf of Ed Warnicke < > hagb...@gmail.com> > *Date:

Re: [onap-tsc] [onap-discuss] Projects

> I know Mazin was pushing for having most proposals ready by Thu so there > is little time left… . > > Thoughts? > > Oliver > > > On May 8, 2017, at 8:47 AM EDT, Ed Warnicke <hagb...@gmail.com> wrote: > > > > I am agnostic as to which way we res

Re: [onap-tsc] [onap-discuss] Projects

** > *** > > > > *From:* onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-bounces@ > lists.onap.org] *On Behalf Of *Danny Lin > *Sent:* Sunday, May 07, 2017 4:14 AM > *To:* Ed Warnicke > *Cc:* onap-disc...@lists.onap.org; onap-tsc > *S

Re: [onap-tsc] [onap-discuss] Projects

I have seen a bunch of proposal wiki pages for projects, but only see a small number listed in the index for such proposals: https://wiki.onap.org/display/DW/Proposing+A+Project For the folks working on proposals, would you list them there? It allows the others who might be interested to see

[onap-tsc] Reminder - ONAP TSC Meeting Today 7:00am PDT, 10:00pm China Time

*Alla Goldner* > > > > Open Network Division > > Amdocs Technology > > > > > > > > *From:* onap-tsc-bounces at lists.onap.org [mailto: > onap-tsc-bounces at lists.onap.org] *On Behalf Of *Ed Warnicke > *Sent:* Thursday, April 27, 2017 2:58 PM > *To:* Phi

[onap-tsc] Reminder - ONAP TSC Meeting Today 7:00am PDT, 10:00pm China Time

Also... the meeting invite I have still says 7 am. Ed On Thu, Apr 27, 2017 at 4:56 AM Ed Warnicke wrote: > I recall a proposal to move the meeting to two hours, but do not recall an > agreement being reached. > > I specifically objected to meeting times that run past 8am PST as I ha

[onap-tsc] Reminder - ONAP TSC Meeting Today 7:00am PDT, 10:00pm China Time

n for next week's face to face > meeting. > > Best, > > Phil. > > On Thu, Apr 27, 2017 at 8:20 PM, Ed Warnicke wrote: > >> I do see in the meeting minutes a note from twelve minutes after the >> conclusion if the meetin without vote to move the >> meeting t

[onap-tsc] Charter

> > Thank you for confirming that there is no precedent of such structural > components in other communities. > > > > And thank you everyone for great volunteer work J > > > > Thanks > > Bin > > *From:* Ed Warnicke [mailto:hagbard at gmail.com] > *Sent:

[onap-tsc] DRAFT Technical Community Charter

Bin, I love your statement: "So it is pretty much merit-based, contribution driven, autonomous management by deliverables. o Code is the King o Deliverables and release determines the success." The charter simply lays out the basic structure of the community, how projects run, their

[onap-tsc] DRAFT Technical Community Charter

Jason, Thank you for the excellent comments. I wanted to ask a follow on question to your comment about 3.3.4 "Tailoring". That section is in the project lifecycle, but appears to address 'Tailoring' for a Simultaneous Release plan, not the life cycle of a project. Does it make sense to simply

[onap-tsc] Charter

The minority of the charter is actually about the TSC, the bulk of it is about the technical community. I recommend calling it the 'Technical Community Charter'. Ed On Mon, Apr 10, 2017 at 12:10 PM, wrote: > My preference is ?Technical Steering Committee Charter? to be consistent > with the

[onap-tsc] F2F Meeting in May Details?

Do we have a wiki page or page off of onap.org that is providing details for the May F2F? I recall us coming to a decision, but the meeting minutes are a little inspecific to my eyes: http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-04-06-22.42.html It would be

[onap-tsc] DRAFT Technical Community Charter

t out. > > Oliver > > On Apr 6, 2017, at 4:44 PM, Ed Warnicke wrote: > > > > On Thu, Apr 6, 2017 at 11:19 AM, Haiby, Ranny (Nokia - US/San Jose USA) < > ranny.haiby at nokia.com> wrote: > > Thanks Ed, Steve, Alla, Lingli, Phil, and Chris. > > I sug

[onap-tsc] DRAFT Technical Community Charter

On Thu, Apr 6, 2017 at 11:19 AM, Haiby, Ranny (Nokia - US/San Jose USA) < ranny.haiby at nokia.com> wrote: > Thanks Ed, Steve, Alla, Lingli, Phil, and Chris. > > I suggest adding another coordinator - a "usability coordinator". The > inherent complexity of each of the merged projects, the

[onap-tsc] DRAFT Technical Community Charter

It might be more precise to say that the TSC is a *part* of the technical community. Thus we have a Technical Community Charter, which covers, among other aspects of the technical community, the TSC :) Ed On Thu, Apr 6, 2017 at 12:56 PM, HU, BIN wrote: > Steve, > > > > Thank you for the

[onap-tsc] ONAP TSC Policies & Processes

er promotion. Our policy is here: > https://wiki.open-o.org/display/TSC/Committer+Promotion+Process. It?s > aligned with the one in the FD.IO charter, but goes into a bit more > detail to provide transparency, checks-and-balances, and a paper trail to > help build trust in the community. > &g

[onap-tsc] ONAP TSC Policies & Processes

Phil, Thank you for raising this and for being clear about distinguishing the charter for the technical community from the 'ONAP Charter'. I would recommend we look at the fd.io 'Technical Community Charter': https://fd.io/governance/technical-community-charter as a guide *structurally*. It is