Re: Akraino Charter
|
Wenjing Chu <Wenjing.Chu@...>
Visibility is the same whether we call it project or blueprint. I’m fine with either name.
Do note that if blueprint A and blueprint B share a component developed within Akraino, we will then need to create another blueprint C, as you suggested, and A and B would have dependency on C. The key point here that Srini brought up is that we explicitly state that functionality development is in scope for Akraino. Wenjing 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:
|
|
|