From: Lars Kurth <lars.kurth-LM2mM/qkH7s@public.gmane.org>
To: Ian Campbell <Ian.Campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Cc: "xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
"xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>
Subject: Re: [Xen-devel] Proposal - Add xe manpages to xen-org
Date: Tue, 25 Sep 2012 16:53:06 +0100 [thread overview]
Message-ID: <5061D362.8070402@xen.org> (raw)
In-Reply-To: <1348583438.11229.23.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
On 25/09/2012 15:30, Ian Campbell wrote:
> According to the original mail it is in asciidoc already, so maybe
> this is already the case?
My understanding is that the existing XenServer/XCP docs are primarily
task driven (i.e. “to achieve X you do Y”). Man pages are per command
references (i.e. “doing Y will cause X to happen”), which is hardly
covered in
existing XS documentation.
> I agree that actually in the source is even better than next to the
> source, if it's an option...
>
>> Manually keeping the zillion commands in sync will be quite the ongoing
>> effort.
> Someone still needs to write/update the text regardless of where it
> lives, but that's as much a code review thing as anything else.
>
I wouldn't want to create a barrier for Grant's students (or other
people that want to contribute). Remember that most are not developers
but users of XCP. Embedding the documentation into the code would mean:
a) existing document source code would need to be refactored
b) it would create a psychological barrier to contribute
c) possibly unnecessary process
Keeping the documentation separate (either in a separate repo, or
directory in an existing repo) is probably the easiest and quickest way
to get this project off the ground quickly.
Lars
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
next prev parent reply other threads:[~2012-09-25 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 15:06 Proposal - Add xe manpages to xen-org Grant McWilliams
[not found] ` <CAGnmK4wB3ZJ3Tb9-VFgWCkcZNwibDzRYV8tvb14vLgw1wj2awQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-24 15:21 ` Lars Kurth
[not found] ` <50607A68.2090604-LM2mM/qkH7s@public.gmane.org>
2012-09-25 8:22 ` [Xen-devel] " Ian Campbell
[not found] ` <1348561354.3452.105.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
2012-09-25 14:19 ` Anil Madhavapeddy
[not found] ` <2D15A521-63E8-4CE7-8D42-62A67FBD75B2-1e/NZYDlv+odnm+yROfE0A@public.gmane.org>
2012-09-25 14:30 ` Ian Campbell
[not found] ` <1348583438.11229.23.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
2012-09-25 15:53 ` Lars Kurth [this message]
[not found] ` <5061D362.8070402-LM2mM/qkH7s@public.gmane.org>
2012-09-25 16:01 ` Ian Campbell
[not found] ` <1348588898.12592.16.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
2012-09-26 15:45 ` Grant McWilliams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5061D362.8070402@xen.org \
--to=lars.kurth-lm2mm/qkh7s@public.gmane.org \
--cc=Ian.Campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.