WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen document day (Oct 12 or 26)

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen document day (Oct 12 or 26)
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Thu, 22 Sep 2011 17:32:46 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Sep 2011 09:33:42 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NiHIzUI/6zNLBbfyIiTQzwoh1xm+e1Krq5T5IYisNGE=; b=GAKCjKSc1jC7dv49i9BV60PjD/xdQmCUHsAhWwIV+RNRE5TFO60mWDT5DM89pIRi9V o6oe8RDp/mfQTV0EvKG+hTdsSCHDSGG04TwI9Asj7ZvUh8QQXZ4melObY3PuNcKiev5G tZEU2N+3CfIA5sZUADyh3++yoFn7eV+tnCXBE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110922130618.GA13238@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110922130618.GA13238@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Another thing that needs to be done is to write man pages for xl, and
update the man pages for xm to indicate that it is deprecated.

We also discussed the idea of moving some of the documentation and the
HOWTOs into the xen.hg/docs folder, preferrably in a nice language
like Markdown, so that we can enforce changes in documentation with
changes code.  I propose using Markdown, if no one has a better idea.
:-)

 -George

On Thu, Sep 22, 2011 at 2:06 PM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> Part of what we brainstormed at Xen Hackathon was what we could do make Xen 
> easier.
>
> And the one thing that seemed to surface up was making the docs better - 
> either
> be the Wiki or the three .pdfs that get created/shipped with Xen.
>
> One thought was to come up with a Documention Day - where volunteers would 
> try to
> fix up some portion of the documentation that they feel they have
> a good grasp of knowledge off and are willing to change (and also look
> to be incorrect)
>
> What do you guys think of Oct 12th or Oct 26 as a day for this?
>
> And then the next question - what page/pdf section interests you?
>
> http://bits.xensource.com/Xen/docs/user.pdf
> http://www.rites.uic.edu/~solworth/xenInterfaceManual.pdf [the one on Xen.org 
> is an older version]
>
> Or Wiki pages:
> http://wiki.xensource.com/xenwiki/
>
> http://wiki.xensource.com/xenwiki/XenDom0Kernels
> http://wiki.xensource.com/xenwiki/XenSerialConsole
> http://wiki.xensource.com/xenwiki/XenParavirtOps
> http://wiki.xensource.com/xenwiki/XenCommonProblems
>
> http://wiki.xensource.com/xenwiki/Consulting
> http://wiki.xensource.com/xenwiki/Consultants
> http://wiki.xensource.com/xenwiki/VpsHostingWithXen
>
> http://wiki.xen.org/xenwiki/XenPCIpassthrough
> http://wiki.xen.org/xenwiki/VTdHowTo
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel