From: "Jürgen Groß" <jgross@suse.com>
To: Lars Kurth <lars.kurth@xenproject.org>, xen-devel@lists.xenproject.org
Cc: Lars Kurth <lars.kurth@citrix.com>,
xen-api@lists.xenproject.org, minios-devel@lists.xenproject.org,
committers@xenproject.org, mirageos-devel@lists.xenproject.org,
win-pv-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH v4 6/7] Add guide on Communication Best Practice
Date: Mon, 6 Jan 2020 08:20:15 +0100 [thread overview]
Message-ID: <add01572-9d87-61e0-80d4-25696b4459bc@suse.com> (raw)
In-Reply-To: <2d005116379febe0e6cfe0ea32792eb90bc74f9d.1577733361.git.lars.kurth@citrix.com>
On 30.12.19 20:32, Lars Kurth wrote:
> From: Lars Kurth <lars.kurth@citrix.com>
>
> This guide covers the bulk on Best Practice related to code review
> It primarily focusses on code review interactions
> It also covers how to deal with Misunderstandings and Cultural
> Differences
>
> Changes since v3
> * Fixed typo
>
> Changes since v2 (added in v2)
> * Fix typos
> * Extended "Verbose vs. terse"
> * Added "Clarity over Verbosity"
> * Broke "Identify the severity of an issue or disagreement" into two chapters
> - "Identify the severity and optionality of review comments" and made
> clarifications
> - "Identify the severity of a disagreement"
> - Expanded "Prioritize significant flaws"
> * Added "Reviewers: Take account of previous reviewer(s) comments"
> * Added prefixes such as "Reviewers:" where appropriate
> * Fixed lien wrapping to 80 characters
> * Replaced inline links with reference links
>
> Signed-off-by: Lars Kurth <lars.kurth@citrix.com>
> ---
> Cc: minios-devel@lists.xenproject.org
> Cc: xen-api@lists.xenproject.org
> Cc: win-pv-devel@lists.xenproject.org
> Cc: mirageos-devel@lists.xenproject.org
> Cc: committers@xenproject.org
> ---
> communication-practice.md | 504 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 504 insertions(+)
> create mode 100644 communication-practice.md
>
> diff --git a/communication-practice.md b/communication-practice.md
> new file mode 100644
> index 0000000..438b73a
> --- /dev/null
> +++ b/communication-practice.md
> @@ -0,0 +1,504 @@
> +# Communication Best Practice
> +
> +This guide provides communication Best Practice that helps you in
> +* Using welcoming and inclusive language
> +* Keeping discussions technical and actionable
> +* Being respectful of differing viewpoints and experiences
> +* Being aware of your own and counterpart’s communication style and culture
> +* Show empathy towards other community members
> +
> +## Code reviews for **reviewers** and **patch authors**
> +
> +Before embarking on a code review, it is important to remember that
> +* A poorly executed code review can hurt the contributors feeling, even when a
> + reviewer did not intend to do so. Feeling defensive is a normal reaction to
> + a critique or feedback. A reviewer should be aware of how the pitch, tone,
> + or sentiment of their comments could be interpreted by the contributor. The
> + same applies to responses of an author to the reviewer.
> +* When reviewing someone's code, you are ultimately looking for issues. A good
> + code reviewer is able to mentally separate finding issues from articulating
> + code review comments in a constructive and positive manner: depending on your
> + personality this can be **difficult** and you may need to develop a technique
> + that works for you.
> +* As software engineers we like to be proud of the solutions we came up with.
> + This can make it easy to take another people’s criticism personally. Always
> + remember that it is the code that is being reviewed, not you as a person.
> +* When you receive code review feedback, please be aware that we have reviewers
> + from different backgrounds, communication styles and cultures. Although we
add "are"
> + all trying to create a productive, welcoming and agile environment, we do
> + not always succeed.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-06 7:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 19:32 [Xen-devel] [PATCH v4 0/7] Code of Conduct + Extra Guides and Best Practices + VOTE Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 1/7] Import v1.4 of Contributor Covenant CoC Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 2/7] Xen Project Code of Conduct Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 3/7] Reformat Xen Project CoC to fit into 80 character limit Lars Kurth
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 4/7] Add Communication Guide Lars Kurth
2020-01-06 6:41 ` Jürgen Groß
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 5/7] Add Code Review Guide Lars Kurth
2020-01-06 7:03 ` Jürgen Groß
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 6/7] Add guide on Communication Best Practice Lars Kurth
2020-01-06 7:20 ` Jürgen Groß [this message]
2020-01-13 19:54 ` George Dunlap
2020-01-13 21:21 ` Lars Kurth
2020-01-15 10:47 ` George Dunlap
2020-01-15 12:22 ` Lars Kurth
2020-01-15 17:07 ` George Dunlap
2019-12-30 19:32 ` [Xen-devel] [PATCH v4 7/7] Added Resolving Disagreement Lars Kurth
2020-01-06 7:25 ` Jürgen Groß
2020-01-06 12:54 ` Lars Kurth
2020-01-06 13:00 ` Jürgen Groß
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=add01572-9d87-61e0-80d4-25696b4459bc@suse.com \
--to=jgross@suse.com \
--cc=committers@xenproject.org \
--cc=lars.kurth@citrix.com \
--cc=lars.kurth@xenproject.org \
--cc=minios-devel@lists.xenproject.org \
--cc=mirageos-devel@lists.xenproject.org \
--cc=win-pv-devel@lists.xenproject.org \
--cc=xen-api@lists.xenproject.org \
--cc=xen-devel@lists.xenproject.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).