qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [qemu-web PATCH] documentation: update links to readthedocs
Date: Mon, 3 Feb 2020 12:07:23 +0000	[thread overview]
Message-ID: <CAFEAcA8pHXeqtC3WT67vwC=g4Vw7BsYpDxUih1XWYzC+dAjoGg@mail.gmail.com> (raw)
In-Reply-To: <82f0aa8e-b445-ad7f-1b17-03f4bb180a85@redhat.com>

On Mon, 3 Feb 2020 at 11:55, Thomas Huth <thuth@redhat.com> wrote:
>
> On 03/02/2020 12.46, Peter Maydell wrote:
> > On Wed, 15 Jan 2020 at 11:11, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> >> The qemu.git/master docs are built nightly here (index.html is now
> >> visible!):
> >> https://www.qemu.org/docs/master/
> >>
> >> qemu.org's docs are more useful at the moment since they include the
> >> user documentation in addition to the developer documentation.
> >
> > Our top-level documentation page https://www.qemu.org/documentation/
> > still points to https://qemu.weilnetz.de/qemu-doc.html -- should
> > we update that now to link to https://www.qemu.org/docs/master/
> > instead ?
>
> Sure, but I'm still waiting for someone to suggest a final patch here.
>
> Open questions:
>
> - Do we also want to link to readthedocs as suggested by Alex, or is our
>   own docs on www.qemu.org enough?

I think if we're hosting our own docs we should just link to
our own docs (which include the not-yet-converted-to-rST
parts, which readthedocs doesn't); linking to two different
versions of the same thing is just going to confuse users.

> - Do we still want to link to weilnetz.de (as it was the case with
>   StefanH's original patch https://patchwork.kernel.org/patch/11234545/)
>   or should that link be removed?

We should remove it; it's been really helpful for the project
that Stefan Weil has provided built-documentation we can link
to for all these years, but now we finally have an "authoritative"
built version on qemu.org that's what we should link to.
Again, having multiple links to different versions of the
same thing would just confuse people. (The exception is that
if we ever decide to provide "version 5.0 docs", "version 5.1
docs", "current master docs" on qemu.org we can do that, because
that's an understandable-to-end-users easily-describable reason
for there being different docs links).

> - Do we only link to https://www.qemu.org/docs/master/ or shall we
>   link to the individual docs (qemu-doc, qemu-qmp-ref, ...) ?

Just link to master/ would be my advice. Otherwise when we
add a new top-level manual (eg the under-discussion tools/
manual) we'll need to update this web page as well.

thanks
-- PMM


  reply	other threads:[~2020-02-03 12:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 10:35 [qemu-web PATCH] documentation: update links to readthedocs Alex Bennée
2020-01-14 11:04 ` Stefan Hajnoczi
2020-01-14 11:11 ` Thomas Huth
2020-01-15 11:10   ` Stefan Hajnoczi
2020-01-15 11:56     ` Alex Bennée
2020-01-15 12:01       ` Daniel P. Berrangé
2020-01-20 10:16         ` Stefan Hajnoczi
2020-01-20 10:31     ` Peter Maydell
2020-02-03 11:46     ` Peter Maydell
2020-02-03 11:54       ` Thomas Huth
2020-02-03 12:07         ` Peter Maydell [this message]
2020-02-03 12:12           ` Thomas Huth
2020-02-03 12:38             ` Peter Maydell
2020-02-03 12:44               ` Peter Maydell
2020-02-03 12:46                 ` Thomas Huth
2020-02-03 13:21                 ` Thomas Huth
2020-02-05 10:28       ` Stefan Hajnoczi

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='CAFEAcA8pHXeqtC3WT67vwC=g4Vw7BsYpDxUih1XWYzC+dAjoGg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /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).