Please note this un-conference discussion on Fri 4/5 15:10 Short Description: Explore opportunities for your LFN project to accelerate development of test frameworks, tools and methods through

04/02 & 04/05 TSC F2F Meeting When: Tuesday, 2nd April 2018 Friday, 5th April 2018 Where: San Francisco Bay Area, Santa Clara, CA (further details to follow) or Zoom Dial In Organizer: tsc@... An

Akraino Community, Reminder: If you have not done so, please take a minute to subscribe to the new subgroups created for TSC and Technical-Discussions if you would like to be included in those

+1 like the organization proposal Thank You, Margaret Chiosi VP Open Ecosystem Team Admin: Sophie Johnson Sophie.johnson1@... +1 (908) 541-3590 Futurewei Technologies, Inc. Fixed Network

Resending to main@... as requested by moderator. So some may already seen this - apologies if so. There is also very interesting suggestion from Frank of a higher level classification

Looks like the main@ list is rejecting new topics now. I guess the intention is moving all these to: technical-discuss@... or tsc@... Right now, these new groups have very few subscribers. You

We (TSC) are putting together a draft with all the terminologies this community to use and a process around it. As we promised in the yesterday’s community call, we will review the draft on next

I may have missed some threads, but I thought we were discussing 1) Integration Blueprints (architecture) 2) Functional Blueprints (components) I agree with some of the other comments

Actually I would have thought integration meant ‘testing’ and functional meant architectureJ But as long as we define the different blueprints and the definition of them. Thank You, Margaret

I will be surprised if we can come up with one functional set of components we all agree on based on my OPNFV/ONAP experience. But we can try. Thank You, Margaret Chiosi VP Open Ecosystem

--snip-- My understanding of the underlying list platform we're using is that the main list can't be renamed. -Andy- -- Andrew J Grimberg Manager Release Engineering The Linux Foundation

<andrew.wilkinson@...> wrote: I tend to agree. The term "blueprint" in Akraino is already confusing enough, even without using it also in the OpenStack Blueprint kind of sense ;) -- Frank

<agrimberg@...> wrote: Understood, np. Sorry for the noise. -- Frank Zdarsky | NFV&SDN Technology Strategy, Office of the CTO | Red Hat e: fzdarsky@... | irc:

I wouldn’t see a Test definition (3) as a ‘blueprint’. Nor would I see specific functional components (2) developed by the Akraino community as ‘blueprints’ either. I think using the

<jserafin@...> wrote: Would it make sense to rename this to "announce@..." then? -- Frank Zdarsky | NFV&SDN Technology Strategy, Office of the CTO | Red Hat e: fzdarsky@... |

I thought in email folks were ok with the following types of blueprint: 1. Architecture 2. components (Physical/virtual) supporting a specific 'use case' 3. Test

Akraino Community, In order to facilitate future discussions in clearly delineated forums utilizing open source project best practices we have made changes to the mail lists available for this

Hi all, We have scheduled the second Akraino community call for Thursday, September 13th. Since a lot of the people who have contributed to the blueprint discussion on the mailing list have

So selectively backporting patches from upstream's master into upstream's stable branch. That's something we might want to do in the upstream branch, too, but I can see the need for exceptions to

Hi Frank, On this: “ - Is Akraino look to build the images/containers? Or limit the scope to installers, starting with Airship? If so, which sister project(s) going to build binary