toggle quoted messageShow quoted text
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.
As long as we agree that such work should take place in Akraino, then it’s just naming. Yes, we could have a “non-integration blueprint”, but it seems really
confusing to me.
From: main@... [mailto:main@...]
On Behalf Of Thomas Nadeau
Sent: Tuesday, September 04, 2018 1:34 PM
Subject: Re: [akraino] Akraino Charter
Very good point. We do need to clarify this as soon as possible.
In the initial draft on blueprints, I proposed that we (a) use “project” as a unit for all the development work in Akraino, and (b) categorize projects
into 2 types: functional projects and blueprint integration projects. (b) is similar to what Kandan called “vertical” and “horizontal”, but uses terms closer to those in other communities.
Functional projects develop functionalities to fill identified gaps.
Why wouldn't you do a blueprint for those too - perhaps a shorter blue print?
Integration projects are responsible to deliver end-to-end ‘blueprints’. Integration projects can utilize the outputs of functional projects, and all upstream open source projects.
On Behalf Of Srini
Sent: Tuesday, September 04, 2018 9:50 AM
Subject: [akraino] Akraino Charter
Hi Akraino TSC,
In the last developer conference, TSC has taken an AI to come out with the Akraino charter definition.
Much of the discussion on last developer conference is mostly about blueprints, except for one break-out session.
In regional orchestration, Edge API and AI breakout session, we talked about the need for them and the consensus is that Akraino project is the right place to develop them. In
one of the Kandan’s presentation, it was clear that Akraino is not only for developing blueprints for various use cases, but is also a home for Edge related open source projects for the functionality where there is a gap in the open source community. Please
consider making the Akraino charter clear on the aspect of development projects to avoid any confusion.