From: Paolo Bonzini <pbonzini@redhat.com>
To: Anirudha Bose <ani07nov@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Documentation tools for QEMU
Date: Fri, 04 Apr 2014 11:25:32 +0200 [thread overview]
Message-ID: <533E7A8C.60301@redhat.com> (raw)
In-Reply-To: <CA+XvPywY56Y06ddt-yrYcBH=21N82WyhL0gM=X9z9VEOvEU-3g@mail.gmail.com>
Il 03/04/2014 20:56, Anirudha Bose ha scritto:
> Hi Paolo !
>
> I would like to volunteer to develop Documentation tools for QEMU during
> my summer holidays. Yesterday I had expressed my intent to work on this
> project in the IRC channel of QEMU. This is a follow up email of your reply.
That's awesome. I've CCed qemu-devel so that other folks see what you'd
like to do.
I'll be away for three weeks starting tomorrow, unfortunately, so making
this public is even more important.
> We can use Pandoc to convert all the docs in different formats to HTML,
> rather than integrating all of them to qemu-tech.texi. We can do the
> same thing with other files as well like qemu-docs.texi and qemu-img.texi.
>
> A challenge in this project would be to process the plaintext files
> which have no styles defined in them. So rather than making the script
> do it, wouldn't it be better if all of them are rewritten in Markdown so
> that the final HTML will have a consistent look?
Yes, rewriting docs/ to Markdown is a good first step.
Some things you could do include:
- do the above Markdown rewrite, and test it with pandoc conversion to HTML
- send patches for it, so that you can get warm with the patches review
process
- build a pandoc filter that converts @foo to `foo`. I think there are
examples in pandoc's homepage.
- look at command descriptions from qmp-commands.hx and start
integrating missing information into qapi-schema.json. Make
qapi-schema.json doc comments much closer to Markdown (plus with the
@foo syntax).
- study the QAPISchema class in scripts/qapi.py. Start thinking of a
qapi-schema.json -> Markdown converter and draft it in Python. Later we
can parse the JSON too, to include type information in the documentation.
- move *.texi files to docs/ and update the Makefile for it.
> What you expectations with this project? Would the final HTML
> documentation be hosted somewhere like readthedocs.org
> <http://readthedocs.org>? Have you considered using Spinx for this purpose?
No, you know more than I do it seems. :)
Paolo
parent reply other threads:[~2014-04-04 9:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+XvPywY56Y06ddt-yrYcBH=21N82WyhL0gM=X9z9VEOvEU-3g@mail.gmail.com>]
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=533E7A8C.60301@redhat.com \
--to=pbonzini@redhat.com \
--cc=ani07nov@gmail.com \
--cc=qemu-devel@nongnu.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 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).