From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH 2/4] CoC: Correct punctuation
Date: Mon, 29 Aug 2016 21:52:09 -0400 [thread overview]
Message-ID: <20160830015209.GB12517@jasmine> (raw)
In-Reply-To: <20160828095252.GA26107@jocasta.intra>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
On Sun, Aug 28, 2016 at 11:52:52AM +0200, John Darrington wrote:
> On Sun, Aug 28, 2016 at 12:19:15PM +0300, Efraim Flashner wrote:
> On Sat, Aug 27, 2016 at 08:19:37PM +0200, John Darrington wrote:
> > +++ b/CODE-OF-CONDUCT
> > @@ -21,7 +21,7 @@ Examples of unacceptable behavior by participants include:
> > * Personal attacks
> > * Trolling or insulting/derogatory comments
> > * Public or private harassment
> > -* Publishing other's private information, such as physical or electronic
> > +* Publishing others' private information, such as physical or electronic
> > addresses, without explicit permission
> > * Other unethical or unprofessional conduct
>
> This Code of Conduct is adapted from the Contributor Covenant
> (http://contributor-covenant.org), version 1.3.0, available at
> http://contributor-covenant.org/version/1/3/0/
>
> I would rather see what they have to saw about it upstream.
> ...actually, upstream has "other's"
>
> "other's" would imply that publishing one person's details is unacceptable,
> but publishing many persons' is ok. Whereas, "others'" means that publishing
> anybody's details is unacceptable.
The current wording is, at best, awkward. But, I think this patch should
be sent upstream so all adopters of the Contributor Covenant can benefit
from the clarification.
https://github.com/ContributorCovenant/contributor_covenant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-30 1:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 18:19 [PATCH 1/4] gnu: yelp: Update to 3.21.3 John Darrington
2016-08-27 18:19 ` [PATCH 2/4] CoC: Correct punctuation John Darrington
2016-08-28 9:19 ` Efraim Flashner
2016-08-28 9:52 ` John Darrington
2016-08-30 1:52 ` Leo Famulari [this message]
2016-08-27 18:19 ` [PATCH 3/4] gnu: Add German Aspell dictionary John Darrington
2016-08-28 9:20 ` Efraim Flashner
2016-08-28 12:41 ` John Darrington
2016-08-29 8:35 ` Alex Kost
2016-08-29 16:50 ` Ludovic Courtès
2016-08-27 18:19 ` [PATCH 4/4] gnu: libtirpc: Remove the --disable-gssapi configure flag John Darrington
2016-08-28 9:43 ` Efraim Flashner
2016-08-28 9:45 ` John Darrington
2016-08-29 16:52 ` Ludovic Courtès
2016-08-29 19:51 ` John Darrington
2016-09-02 13:16 ` [PATCH 1/4] gnu: yelp: Update to 3.21.3 Ludovic Courtès
2016-09-02 14:56 ` John Darrington
2016-09-03 13:57 ` Ludovic Courtès
2016-09-03 14:28 ` John Darrington
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=20160830015209.GB12517@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.