From: Joe Perches <joe@perches.com>
To: Ivan Chavero <ichavero@chavero.com.mx>, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] Fix Code of Conduct ambiguities
Date: Sun, 14 Oct 2018 18:46:37 -0700 [thread overview]
Message-ID: <97e8ce1370ed45b771538c67712920322ecdd3aa.camel@perches.com> (raw)
In-Reply-To: <20181014185241.4085197-1-ichavero@chavero.com.mx>
On Sun, 2018-10-14 at 13:52 -0500, Ivan Chavero wrote:
> The language and focus of the CoC has some ambiguities that
> could lead to conflicts that might distract maintainers and
> contributors attention from the technical nature of the
> Linux kernel.
> This patch aims to clarify this problems and focus the document
> to a more possitive, healthy and technical standpoint.
[]
> diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst
[]
> @@ -17,23 +19,22 @@ Our Standards
> Examples of behavior that contributes to creating a positive environment
> include:
>
> -* Using welcoming and inclusive language
> -* Being respectful of differing viewpoints and experiences
> -* Gracefully accepting constructive criticism
> -* Focusing on what is best for the community
> -* Showing empathy towards other community members
> +* Using welcoming and inclusive language.
> +* Being respectful of differing viewpoints and experiences.
> +* Gracefully accepting constructive criticism.
> +* Focusing on what is best for the community:.
> +* Showing empathy towards other community members.
> +* Use facts instead of opinions.
trivia:
bullet points do not need periods.
next prev parent reply other threads:[~2018-10-15 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 18:52 [PATCH] Fix Code of Conduct ambiguities Ivan Chavero
2018-10-15 1:46 ` Joe Perches [this message]
2018-10-16 12:21 ` Iván Chavero
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=97e8ce1370ed45b771538c67712920322ecdd3aa.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=ichavero@chavero.com.mx \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).