On Mon, Sep 23, 2019 at 11:10:53AM +0100, Daniel P. Berrangé wrote:
> On Fri, Sep 20, 2019 at 07:33:08PM +0200, Pavel Hrdina wrote:
> > On Fri, Sep 20, 2019 at 03:12:01PM +0100, Daniel P. Berrangé wrote:
> > > There are various ideas / plans floating around for future libvirt work,
> > > some of
On Fri, Sep 20, 2019 at 07:33:08PM +0200, Pavel Hrdina wrote:
> On Fri, Sep 20, 2019 at 03:12:01PM +0100, Daniel P. Berrangé wrote:
> > There are various ideas / plans floating around for future libvirt work,
> > some of which is actively in progress. Historically we've never captured
> > this
On Fri, Sep 20, 2019 at 03:12:01PM +0100, Daniel P. Berrangé wrote:
> There are various ideas / plans floating around for future libvirt work,
> some of which is actively in progress. Historically we've never captured
> this kind of information anywhere, except in mailing list discussions.
> In
On Fri, 2019-09-20 at 15:12 +0100, Daniel P. Berrangé wrote:
[...]
> + This document attempts to outline the libvirt project strategy for
> + the near future. Think of this is a high level vision or todo list
s/is a high/as a high/
> + setting the direction for the project & its
On Fri, Sep 20, 2019 at 15:12:01 +0100, Daniel Berrange wrote:
> There are various ideas / plans floating around for future libvirt work,
> some of which is actively in progress. Historically we've never captured
> this kind of information anywhere, except in mailing list discussions.
> In
There are various ideas / plans floating around for future libvirt work,
some of which is actively in progress. Historically we've never captured
this kind of information anywhere, except in mailing list discussions.
In particular guidelines in hacking.html.in don't appear until a policy
is
