From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=37832 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q7Cto-0005UT-9t
	for qemu-devel@nongnu.org; Tue, 05 Apr 2011 16:30:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q7Ctn-0003FS-6A
	for qemu-devel@nongnu.org; Tue, 05 Apr 2011 16:30:52 -0400
Received: from mail-yx0-f173.google.com ([209.85.213.173]:34830)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q7Ctn-0003FE-3p
	for qemu-devel@nongnu.org; Tue, 05 Apr 2011 16:30:51 -0400
Received: by yxk8 with SMTP id 8so382664yxk.4
	for <qemu-devel@nongnu.org>; Tue, 05 Apr 2011 13:30:50 -0700 (PDT)
Message-ID: <4D9B7BF5.9080509@codemonkey.ws>
Date: Tue, 05 Apr 2011 15:30:45 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] KVM call agenda for April 05
References: <m38vvpom86.fsf@neno.mitica>	<201104051601.02762.bradh@frogmouth.net>	<21351316-8430-4743-B75C-4299383F7D76@suse.de>	<201104052221.35703.bradh@frogmouth.net>	<BANLkTik+xFJ6VysuNOO1P3R+ynipNNeRVg@mail.gmail.com>
	<BANLkTi=Bsua7_FPS-B_xHYNOWcLRxp5v8Q@mail.gmail.com>
In-Reply-To: <BANLkTi=Bsua7_FPS-B_xHYNOWcLRxp5v8Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org, Brad Hards <bradh@frogmouth.net>

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
>