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: Thu, 26 Jan 2017 18:52:42 +0100 [thread overview]
Message-ID: <d95139a6-0e38-75b5-b8df-b4e12391e032@redhat.com> (raw)
In-Reply-To: <265EAA01-0C75-45D5-A55D-481DAC288AE5@gmail.com>
On 26/01/2017 18:40, G 3 wrote:
>
> On Jan 26, 2017, at 12:30 PM, Paolo Bonzini wrote:
>
>>
>>
>> On 26/01/2017 18:28, G 3 wrote:
>>>
>>> On Jan 26, 2017, at 12:00 PM, qemu-devel-request@nongnu.org wrote:
>>>
>>>>
>>>> Hi all,
>>>>
>>>> as you may know I've been collecting some ideas about documentation for
>>>> QEMU at http://wiki.qemu-project.org/Features/Documentation.
>>>>
>>>> I've now prepared a poll to understand how familiars developers are
>>>> with
>>>> various documentation tools. I've CCed people with most commits to
>>>> QEMU
>>>> documentation, or with whom I have discussed about this before, but
>>>> everybody's opinion is of course welcome!
>>>>
>>>> The poll is hosted with Google Forms and you can fill it in at
>>>> https://goo.gl/Yfxj1M. If you hate Google Forms, contact me offlist
>>>> and
>>>> I'll send you the questions by email (and remind you when I need
>>>> someone
>>>> to review my patches).
>>>>
>>>> Paolo
>>>>
>>>>
>>>> tl;dr: poll is at https://goo.gl/Yfxj1M
>>>
>>>
>>> For this question:
>>> What's your opinion on the maintainability of the following
>>> documentation formats?
>>>
>>> Is it from 1(least maintainable) to 5 (most maintainable)?
>>>
>>> The survey looks good. I will take it.
>>
>> Yes, all of them are 1=bad 5=good.
>
> Could we add HTML to the list of documentation formats?
Since you have mentioned that in the comments and someone else mentioned
AsciiDoc, they weren't included because:
- HTML is mostly a destination format. With the listed formats it is
possible to produce a variety of outputs (mostly HTML itself and PDF;
secondarily text or ePub or others).
- AsciiDoc was considered by the Linux kernel folks but they complained
about the tools.
Paolo
next prev parent reply other threads:[~2017-01-26 17:52 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 [this message]
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
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=d95139a6-0e38-75b5-b8df-b4e12391e032@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).