From: "Iván Chavero" <ichavero@chavero.com.mx>
To: Joe Perches <joe@perches.com>, 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: Tue, 16 Oct 2018 07:21:42 -0500 [thread overview]
Message-ID: <5cd87f8299de9fa0d2726a2d3fa2bdae349281be.camel@chavero.com.mx> (raw)
In-Reply-To: <97e8ce1370ed45b771538c67712920322ecdd3aa.camel@perches.com>
El 14/10/18 a las 8:46 p. m., Joe Perches escribió:
> 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.
>
>
When there are complete sentences the period is optional according to
the Oxford dictionary [1]
if it's bad form i can remove them.
[1] https://en.oxforddictionaries.com/punctuation/bullet-points
prev parent reply other threads:[~2018-10-16 12:22 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
2018-10-16 12:21 ` Iván Chavero [this message]
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=5cd87f8299de9fa0d2726a2d3fa2bdae349281be.camel@chavero.com.mx \
--to=ichavero@chavero.com.mx \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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).