On Fri, Jul 29, 2016, at 11:55 AM, Ben Nemec wrote:
> As I noted in the meeting yesterday, I think the lack of response from
> TripleO regarding this topic is kind of answer enough. TripleO has
> moved away from having a heavy dependency on diskimage-builder (it's
> basically used to install some
As I noted in the meeting yesterday, I think the lack of response from
TripleO regarding this topic is kind of answer enough. TripleO has
moved away from having a heavy dependency on diskimage-builder (it's
basically used to install some packages and a handful of elements that
we haven't been able
Hello everyone,
The subject sort of says it all - I'd like to propose making
diskimage-builder its own project team.
When we started diskimage-builder and many of the other TripleO
components we designed them with the goal in mind of creating tools that
are useful outside of the TripleO context (