qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Sphinx and docs/index.rst: dead code?
Date: Thu, 25 Jul 2019 17:42:41 +0100	[thread overview]
Message-ID: <CAFEAcA8s=YbvO7Qw4twt5NemH4vVbZX8_mi5LveTYgYYQY5YNA@mail.gmail.com> (raw)
In-Reply-To: <676de2d8-b7bd-1f16-8270-8bc5f7de8254@redhat.com>

On Thu, 25 Jul 2019 at 17:34, John Snow <jsnow@redhat.com> wrote:
> Yup; I think a single point of entry would be nice -- I think we need to
> start hosting our sphinx documentation because it's confusing that we
> have both the traditional manual (hosted by Stefan Weil) and this newer
> one that isn't available anywhere.
>
> The interop manual in particular is crucial to get hosted.

Yes, this would be a good thing.

> We could perhaps formalize this as follows:
>
> - index.rst, which is an "absolutely everything included" single point
> of entry manual for developers and contributors,
>
> - user.rst, which could be a single point of entry for end users, to be
> bundled in distro packaging.

This means you'll end up building 90% of our documentation twice,
which is something I was trying to avoid with the current setup.

It occurs to me that we don't necessarily need the 'top level'
page to be generated by Sphinx -- we could just ship an index.html
which has helpful links to the individual manuals.

(https://wiki.qemu.org/Features/Documentation is the current
plan and lists the various manuals we'll end up with. 'user'
in that plan means the documentation for the user-mode emulation.)

thanks
-- PMM


  reply	other threads:[~2019-07-25 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 23:22 [Qemu-devel] Sphinx and docs/index.rst: dead code? John Snow
2019-07-25  9:08 ` Peter Maydell
2019-07-25 16:34   ` John Snow
2019-07-25 16:42     ` Peter Maydell [this message]
2019-07-25 17:26       ` John Snow
2019-07-25 17:53         ` Peter Maydell

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='CAFEAcA8s=YbvO7Qw4twt5NemH4vVbZX8_mi5LveTYgYYQY5YNA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=jsnow@redhat.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).