From: Lars Kurth <lars.kurth@xen.org>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Xen Document Day : Thank You!
Date: Thu, 27 Oct 2011 15:23:18 +0100 [thread overview]
Message-ID: <4EA96956.4070300@xen.org> (raw)
Hi everybody!
I wanted to thank you for helping out with the document day. As far as I
can see, we got quite a bit of stuff done:t, etc.
Dev Docs:
- Made some progress on man pages
- Some discussion on API docs (still an open issue how we will do this :
tried doxygen)
Wiki:
- A good handle on the pages : what's old, what's important (see
https://docs.google.com/spreadsheet/ccc?key=0AiRyVp8djqV3dEJRdVZaQzZmLVNKTERwMDNGaTlKdkE&hl=en_US#gid=0).
Still a few pages that need to be classified, but we handled most
- Some Wiki pages were improved
What did surprise me, is how little documentation for users there
actually is on the Wiki. I thought we were in bad shape, but not that
bad. Have to think about how to address this.
We are also working on setting up a new wiki and then find a way to
start migrating content over. It may make sense to have regular document
days. Any views?
Regards
Lars
next reply other threads:[~2011-10-27 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 14:23 Lars Kurth [this message]
2011-11-03 13:48 ` Xen Document Day : Thank You! eva
2011-11-15 9:10 ` [Xen-users] " eva
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=4EA96956.4070300@xen.org \
--to=lars.kurth@xen.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).