From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Brad Hards <bradh@frogmouth.net>
Subject: Re: [Qemu-devel] KVM call agenda for April 05
Date: Tue, 05 Apr 2011 15:30:45 -0500 [thread overview]
Message-ID: <4D9B7BF5.9080509@codemonkey.ws> (raw)
In-Reply-To: <BANLkTi=Bsua7_FPS-B_xHYNOWcLRxp5v8Q@mail.gmail.com>
On 04/05/2011 03:25 PM, Peter Maydell wrote:
> On 5 April 2011 14:14, Stefan Hajnoczi<stefanha@gmail.com> wrote:
>> This stems from the fact that development is centered around the
>> mailing list. Some folks have put technical documentation on the wiki
>> but a lot simply happens on the mailing list.
>> I'm unsure how we can sustainably keep the wiki up-to-date on detailed
>> code internals knowledge. Any suggestions, any examples of projects
>> doing this successfully?
> Another approach would be to try to increase the use of docs/
> for technical code internals information. The advantage would be
> that we could choose to require docs/ updates for design changes
> in order for a code change to pass patch review; the disadvantage
> would be that it's inevitably more of a pain to update.
We've been unofficially doing that for a lot of recent stuff.
I don't know that that really helps with the problem of keeping it up to
date though.
Regards,
Anthony Liguori
> -- PMM
>
next prev parent reply other threads:[~2011-04-05 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 19:22 [Qemu-devel] KVM call agenda for April 05 Juan Quintela
2011-04-04 19:59 ` Anthony Liguori
2011-04-04 20:38 ` Lucas Meneghel Rodrigues
2011-04-05 6:01 ` Brad Hards
2011-04-05 8:27 ` Stefan Hajnoczi
2011-04-05 8:29 ` Alexander Graf
2011-04-05 8:42 ` Stefan Hajnoczi
2011-04-05 9:44 ` Brad Hards
2011-04-05 9:50 ` Alexander Graf
2011-04-05 10:53 ` Stefan Hajnoczi
2011-04-05 12:04 ` Brad Hards
2011-04-05 12:21 ` Brad Hards
2011-04-05 13:14 ` Stefan Hajnoczi
2011-04-05 20:25 ` Peter Maydell
2011-04-05 20:30 ` Anthony Liguori [this message]
2011-04-07 9:38 ` Harsh Bora
2011-04-05 9:36 ` Alon Levy
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=4D9B7BF5.9080509@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=bradh@frogmouth.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).