All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	"Laurent Vivier" <laurent@vivier.eu>,
	qemu-devel@nongnu.org, "John Snow" <jsnow@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: In-tree docs vs. Wiki [Was: Re: [PATCH 0/3] rSTify SubmitAPatch, TrivialPatches, and SpellCheck wiki pages]
Date: Tue, 5 Oct 2021 18:03:58 +0200	[thread overview]
Message-ID: <YVx3bqvVny2wdTEh@paraplu> (raw)
In-Reply-To: <YVxxTgCxQ39nIQxc@redhat.com>

On Tue, Oct 05, 2021 at 04:37:50PM +0100, Daniel P. Berrangé wrote:
> On Tue, Oct 05, 2021 at 05:07:06PM +0200, Philippe Mathieu-Daudé wrote:

[...]

> > One point Peter raised on IRC is it is easier to update a Wiki page
> > than get a patch merged into the repository. IOW we are making things
> > harder.
> 
> There are factors to consider beyond ease of contributions.
> 
> Certain information here is documenting a fundamental part of the
> QEMU community operation & processes. That ought to have a high
> trust level and be subject to review of content changes.  I'd say
> the SubmitAPatch page falls in this category.
> 
> Other information is essentially random adhoc user written content
> that isn't critical to the project. This can live with a low trust
> level and little-to-no review.
> 
> IMHO, the wiki should only be considered for the latter type of
> content, with any important project content being subject to
> review.
> 
> I also feel like docs in git is more likely to be kept upto date
> by the regular maintainers, than wikis which can become a bit of
> outdated mess.

I agree.  Here's an example that proves your point: had I written this
huge 'live-block-operations.rst'[1] doc as a Wiki, pretty sure it
would've been slowly rotting away.  Now I see 5 other contributors
besides me (including Peter, yourself, and Paolo in this thread) that
have patched it ... by virtue of it being in-tree.

That makes me even more convinced that having development, interface,
and any valuable docs that are in-tree are more well-maintained.

(FWIW, I seem to have more motivation to write docs in rST or similar
formats that can be iterated over, with in-line reviews like regular
patches.  I can't claim the same level of motivation to write Wiki pages
somehow.)

> It is a shame that our normal contribution workflow doesn't make
> it easy for simple docs changes to be accepted and merged :-(

Yeah; improving that can be nicer.

[1] https://qemu.readthedocs.io/en/latest/interop/live-block-operations.html

-- 
/kashyap



  reply	other threads:[~2021-10-05 16:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 12:10 [PATCH 0/3] rSTify SubmitAPatch, TrivialPatches, and SpellCheck wiki pages Kashyap Chamarthy
2021-09-22 12:10 ` [PATCH 1/3] docs: rSTify the "SpellCheck" wiki Kashyap Chamarthy
2021-09-22 13:10   ` Peter Maydell
2021-09-22 13:48     ` Kashyap Chamarthy
2021-09-22 12:10 ` [PATCH 2/3] docs: rSTify the "TrivialPatches" wiki Kashyap Chamarthy
2021-09-22 13:05   ` Philippe Mathieu-Daudé
2021-09-22 13:16     ` Kashyap Chamarthy
2021-09-22 13:18     ` Daniel P. Berrangé
2021-09-22 12:10 ` [PATCH 3/3] docs: rSTify the "SubmitAPatch" wiki Kashyap Chamarthy
2021-09-22 13:05 ` [PATCH 0/3] rSTify SubmitAPatch, TrivialPatches, and SpellCheck wiki pages Peter Maydell
2021-09-22 13:23   ` Kashyap Chamarthy
2021-09-28 17:31 ` Paolo Bonzini
2021-09-29  7:53   ` Kashyap Chamarthy
2021-10-05 14:01 ` Stefan Hajnoczi
2021-10-05 14:11   ` Kashyap Chamarthy
2021-10-05 14:24     ` Stefan Hajnoczi
2021-10-05 14:39       ` Kashyap Chamarthy
2021-10-05 15:07       ` Philippe Mathieu-Daudé
2021-10-05 15:37         ` Daniel P. Berrangé
2021-10-05 16:03           ` Kashyap Chamarthy [this message]
2021-10-05 16:06             ` In-tree docs vs. Wiki [Was: Re: [PATCH 0/3] rSTify SubmitAPatch, TrivialPatches, and SpellCheck wiki pages] Philippe Mathieu-Daudé

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=YVx3bqvVny2wdTEh@paraplu \
    --to=kchamart@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@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 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.