This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-API] Xen Management API draft

To: Hollis Blanchard <hollisb@xxxxxxxxxx>
Subject: Re: [Xen-API] Xen Management API draft
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Sat, 24 Jun 2006 21:26:10 +0100
Cc: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 24 Jun 2006 13:26:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1150998703.2599.29.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <20060622170130.GI25606@xxxxxxxxxxxxxxxxxxxxxx> <1150998703.2599.29.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Jun 22, 2006 at 12:51:42PM -0500, Hollis Blanchard wrote:

> On Thu, 2006-06-22 at 18:01 +0100, Ewan Mellor wrote:
> > 
> > Like the OVA spec, this document is for narrow circulation, and once
> > we are getting happy with it, we'll circulate it more widely.  I'd
> > like to be able to circulate this before OLS, as that will be a good
> > chance to discuss it with people face-to-face once they've had a
> > chance to read it.
> I'm confused. You said this is an open mailing list, but this document
> says "DO NOT CIRCULATE" on the title page?

I would like to keep discussion and circulation of this document on this list,
for now.  I'm happy for other people to join this list, and to see the
document, but we've already had problems with people seeing this work out of
context and getting confused.  I don't think that the document has enough in
the way of explanation to stand on its own just yet, so I think that the best
way to ensure that everyone gets the right context is to keep the discussion
here on this list, just for a short while.

Once we're happy that the document can stand on its own feet, in good time
before OLS, then we can relax the circulation restrictions, change the
copyright statement, and so on.


xen-api mailing list