All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] docs/system/s390x: Improve the 3270 documentation
Date: Fri, 10 Jul 2020 12:40:51 +0100	[thread overview]
Message-ID: <CAFEAcA-+OTjANDWSBrsK4J6M=VCu9gPAjFuxfUo88-kk3O4O9Q@mail.gmail.com> (raw)
In-Reply-To: <20200710125552.1ad24571.cohuck@redhat.com>

On Fri, 10 Jul 2020 at 11:56, Cornelia Huck <cohuck@redhat.com> wrote:
>
> On Thu,  9 Jul 2020 18:04:39 +0200
> Thomas Huth <thuth@redhat.com> wrote:
>
> > There is some additional information about the 3270 support in our
> > Wiki at https://wiki.qemu.org/Features/3270 - so let's include this
> > information into the main documentation now to have one single
> > source of information (the Wiki page could later be removed).
>
> No objection; but what should our general policy with regard to wiki
> pages vs. documentation be? The 3270 support is pretty much static, but
> e.g. for vfio-ccw, we use the wiki page as a place where we track
> things that should be worked on etc.

I think that (apart from docs/devel) the ideal would be that a
user should be able to look at the documentation to find what
they need to know and not have to look in the wiki. So "feature X
is unsupported" is useful to have in the documentation; developer
TODO lists, design notes, suggestions for improvements, etc
would be better on the wiki.

> (Related: What is the scope of our QEMU documentation? Is a libvirt XML
> snippet on topic? Kernel configuration options (as in here)?)

If we don't think they're liable to become rapidly out of date,
I guess we might as well err on the side of providing information
that's helpful to users. (I think a full-on "here is a tutorial
and how-to guide on setting up guest OS Foo on this model"
would perhaps be a bit out of place, but there's lots of space
between here and there.)

thanks
-- PMM


  reply	other threads:[~2020-07-10 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 16:04 [PATCH] docs/system/s390x: Improve the 3270 documentation Thomas Huth
2020-07-10 10:55 ` Cornelia Huck
2020-07-10 11:40   ` Peter Maydell [this message]
2020-07-13  7:38   ` Thomas Huth

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='CAFEAcA-+OTjANDWSBrsK4J6M=VCu9gPAjFuxfUo88-kk3O4O9Q@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.