qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: G 3 <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu-devel] Poll on QEMU documentation project
Date: Wed, 1 Feb 2017 15:50:58 -0800	[thread overview]
Message-ID: <1d27660e-84a3-d200-aa50-5bce1ab56046@redhat.com> (raw)
In-Reply-To: <87B90AC4-A4F9-4A6B-83F9-4E351BC71F80@gmail.com>



On 01/02/2017 15:36, G 3 wrote:
> On Feb 1, 2017, at 6:17 PM, Paolo Bonzini wrote:
>> The requirements for the format are:
>>
>> * support for HTML and man as output formats, optionally PDF and text
>> * support for QEMU's usual submission workflow
>> * producing documentation with a consistent look
>> * tool support and extensibility
>> * being easy to use and not too obscure
>>
>> in this order.  Based on this, the only formats we could plausibly use
>> are Texinfo (if only because that's what we use now), Markdown,
>> restructuredText, Docbook and Asciidoc.  The poll mentioned all of these
>> except Asciidoc, plus LaTeX as a "control group".
> 
> Ok. I understand.
> 
> For the above requirements of "tool support and extensibility", what do
> you mean by this? Do you mean command-line tool support? What do you
> mean by extensibility?

Basically, easily integrating QEMU-specific code in the build.  This
way, we don't need 20 different steps in the Makefile; instead a single
tool invocation will do everything from parsing the input, to extracting
documentation comments from C source, to finally generating the output.

Of course you need to find the right balance between redoing the same
work over and over (a solution purely based on Make can do that best)
and ease of use.

Paolo

  reply	other threads:[~2017-02-01 23:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.205.1485450031.31314.qemu-devel@nongnu.org>
2017-01-26 17:28 ` [Qemu-devel] Qemu-devel] Poll on QEMU documentation project G 3
2017-01-26 17:30   ` Paolo Bonzini
2017-01-26 17:40     ` G 3
2017-01-26 17:52       ` Paolo Bonzini
2017-01-26 17:57         ` Peter Maydell
2017-01-27  6:51           ` Markus Armbruster
2017-01-27 10:08             ` Peter Maydell
2017-01-30 14:21               ` Stefan Hajnoczi
2017-01-30 15:02                 ` Markus Armbruster
2017-02-01 22:50       ` G 3
2017-02-01 23:17         ` Paolo Bonzini
2017-02-01 23:36           ` G 3
2017-02-01 23:50             ` Paolo Bonzini [this message]
2017-01-26 17:58     ` Cornelia Huck

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=1d27660e-84a3-d200-aa50-5bce1ab56046@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=programmingkidx@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).