From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
peter.maydell@linaro.org, agraf@csgraf.de
Subject: Re: [RFC PATCH 0/4] docs/devel suggestions for discussion
Date: Wed, 12 Oct 2022 11:02:50 -0400 [thread overview]
Message-ID: <Y0bXGmSNngicSxxt@fedora> (raw)
In-Reply-To: <20221012121152.1179051-1-alex.bennee@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
On Wed, Oct 12, 2022 at 01:11:48PM +0100, Alex Bennée wrote:
> Hi,
>
> This is an attempt to improve our processes documentation by:
>
> - adding an explicit section on maintainers
> - reducing the up-front verbiage in patch submission
> - emphasising the importance to respectful reviews
>
> I'm sure the language could be improved further so I humbly submit
> this RFC for discussion.
>
> Alex Bennée (4):
> docs/devel: add a maintainers section to development process
> docs/devel: make language a little less code centric
> docs/devel: simplify the minimal checklist
> docs/devel: try and improve the language around patch review
>
> docs/devel/code-of-conduct.rst | 2 +
> docs/devel/index-process.rst | 1 +
> docs/devel/maintainers.rst | 84 +++++++++++++++++++
> docs/devel/submitting-a-patch.rst | 101 +++++++++++++++--------
> docs/devel/submitting-a-pull-request.rst | 12 +--
> roms/qboot | 2 +-
> 6 files changed, 157 insertions(+), 45 deletions(-)
> create mode 100644 docs/devel/maintainers.rst
>
> --
> 2.34.1
>
Modulo comments:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-12 15:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 12:11 [RFC PATCH 0/4] docs/devel suggestions for discussion Alex Bennée
2022-10-12 12:11 ` [RFC PATCH 1/4] docs/devel: add a maintainers section to development process Alex Bennée
2022-10-12 14:59 ` Stefan Hajnoczi
2022-10-13 8:39 ` Markus Armbruster
2022-10-14 9:26 ` Mark Cave-Ayland
2022-10-14 11:23 ` Markus Armbruster
2022-10-14 13:24 ` Alex Bennée
2022-10-20 10:51 ` Peter Maydell
2022-10-12 12:11 ` [RFC PATCH 2/4] docs/devel: make language a little less code centric Alex Bennée
2022-10-12 15:53 ` Paolo Bonzini
2022-10-12 12:11 ` [RFC PATCH 3/4] docs/devel: simplify the minimal checklist Alex Bennée
2022-10-12 12:14 ` Daniel P. Berrangé
2022-10-12 15:02 ` Stefan Hajnoczi
2022-10-14 9:31 ` Mark Cave-Ayland
2022-10-12 12:11 ` [RFC PATCH 4/4] docs/devel: try and improve the language around patch review Alex Bennée
2022-10-13 8:40 ` Markus Armbruster
2022-10-12 15:02 ` Stefan Hajnoczi [this message]
2022-10-12 15:56 ` [RFC PATCH 0/4] docs/devel suggestions for discussion Paolo Bonzini
2022-10-14 9:46 ` Mark Cave-Ayland
2022-10-14 11:35 ` Markus Armbruster
2022-10-14 13:31 ` Alex Bennée
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=Y0bXGmSNngicSxxt@fedora \
--to=stefanha@redhat.com \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.