Re: Akraino Charter
|
Srini
Thank you for discussion on this.
Terminology suggested by Wenjing on categorization (features/functional and integration) seems good to me too.
Thanks Srini
From: main@... [mailto:main@...]
On Behalf Of Margaret Chiosi
Sent: Thursday, September 6, 2018 5:11 AM To: main@... Subject: Re: [akraino] Akraino Charter
I like the functional blueprint description which can focus on ‘features’ and the integration blueprint which focuses on the ‘funcitions/modules’ which will be integrated together. I don’t think we need any more granular splits than these.
Thank You, Margaret Chiosi VP Open Ecosystem Team
Admin: Sophie Johnson +1 (908) 541-3590
Futurewei Technologies, Inc. Fixed Network Solution CC 400 Crossing Blvd Bridgewater, NJ 08807 (cell) +1-732-216-5507
From:
main@... [mailto:main@...]
On Behalf Of Andrew Wilkinson
Agree we should not call “feature development” projects Blueprints.
The terms ‘Feature Project’ and ‘Blueprint’ seem sufficiently distinct and descriptive to me
Andrew
Glenn,
From: Glenn Seiler To: main<main@...> Subject: Re: [akraino] Akraino Charter Time: 2018-09-05 14:03:18
I don’t love the idea of using the term BluePrint for the functional development projects. I think the term is already overloaded enough, and there is already some confusion between the term blueprint as it applies to OpenStack and an Akraino Integration blueprint.
I like the term blueprint as it applies to things are being ‘built’ or integrated from multiple sources, with potentially multiple regulations (or standards) to apply and potentially with very different components (HW, VIM, MW or APIs) etc. Using the same term to apply to a more focused and singular project may be pretty confusing.
Perhaps we could do something more consistent with what OPNFV is doing? Using project proposals/plans to define and propose new functional projects. -glenn
From:
main@... [mailto:main@...]
On Behalf Of Wenjing Chu
Visibility is the same whether we call it project or blueprint. I’m fine with either name.
From: Thomas Nadeau To: main<main@...> Subject: Re: [akraino] Akraino Charter Time: 2018-09-05 08:00:05
The idea for doing everything in blueprints is that it brings visibility into any work that impacts the project to both the TSC, but also clearly in writing so any others (i.e.: integration, testing, etc...) that might be external to the project have clear information about what is planned or underway. On a related note, I view blue prints as being largely analogous to epics, and in the same way are a good way to plan for a current or future release, and just a good way to organize the moving parts of a large project like this one potentially can turn out to be.
--Tom
On Tue, Sep 4, 2018 at 7:30 PM Wenjing Chu <Wenjing.Chu@...> wrote:
|
|
|
