On 04/05/2011 03:25 PM, Peter Maydell wrote:
On 5 April 2011 14:14, Stefan Hajnoczi<stefa...@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
