From: Josh Triplett <josh@joshtriplett.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] New CoC and Brendan Eich
Date: Wed, 10 Oct 2018 13:17:59 -0700 [thread overview]
Message-ID: <20181010201759.GA3300@localhost> (raw)
In-Reply-To: <20181010171227.3f8e681f@coco.lan>
On Wed, Oct 10, 2018 at 05:12:27PM -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 10 Oct 2018 12:56:34 -0700
> Josh Triplett <josh@joshtriplett.org> escreveu:
>
> > On Wed, Oct 10, 2018 at 03:28:11PM -0300, Mauro Carvalho Chehab wrote:
> > > Em Wed, 10 Oct 2018 10:21:11 -0700
> > > Josh Triplett <josh@joshtriplett.org> escreveu:
> > >
> > > > On Wed, Oct 10, 2018 at 10:57:54AM -0300, Mauro Carvalho Chehab wrote:
> > > > > With regards to (2), I have to add that idiomatic expression violations
> > > > > are really hard to be detected by non-native English speakers.
> > > > >
> > > > > Recently, I wanted to post about exchanging gpg keys on an event
> > > > > we'll have. As this is something that I don't commonly organize, I browsed
> > > > > the Internet to check the proper term (it is "key chain party" or
> > > > > "key signing party"). On my google search, I omitted one of the words on
> > > > > that phase, and discovered an idiomatic expression that could be argued
> > > > > as a CoC violation.
> > > >
> > > > Unintentionally using a phrase like that seems easy enough to handle
> > > > with a reply (on-list or off, as appropriate) saying "You might wish to
> > > > rephrase that as 'key signing party' or similar, because the phrase you
> > > > used is also an idiom with risque connotations."
> > > >
> > > > To contrast that with the kind of *intentional* issue that would prompt
> > > > a less forgiving response (especially if repeated), consider if someone
> > > > submitted a script to manage such parties, named it "key-party", and
> > > > filled it with other related innuendo, to the point that there's no
> > > > doubt they were doing so intentionally. Sounds ridiculous, and yet there
> > > > are plenty of examples of that and worse in FOSS history.
> > >
> > > Yes, I know that an unintentional mention would have a completely
> > > different treatment.
> > >
> > > The point is that, as a maintainer, if one would write a patch with such
> > > expression - or whatever other idiomatic sentence that would have a "hidden"
> > > meaning inside it for non native speakers - I would probably end by applying
> > > it without I even realize about the issue.
> >
> > And the same notion of intent applies there, too. Mistakes happen, and
> > when they really are mistakes, that's not a critical issue. I'd assume
> > you'd also quickly apply a patch someone sent you to fix it. (By
> > contrast with someone who, for instance, might go off on a rant if asked
> > to do so.)
>
> Surely, but, except if I receive such fix soon enough, I probably won't
> be rebasing the tree (as rebasing a master tree usually causes damage
> to a lot of people).
>
> So, the bad wording will stay forever at the git history - and will
> probably be backported to -stable too (if stable people won't notice).
It happens. It's not the end of the world. I wouldn't expect to see a
git tree people work from rebased to remove something as minor as that,
even if it *hadn't* been propagated yet.
next prev parent reply other threads:[~2018-10-10 20:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 16:23 [Ksummit-discuss] New CoC and Brendan Eich jonsmirl
2018-10-04 18:33 ` Laurent Pinchart
2018-10-04 19:05 ` jonsmirl
2018-10-04 19:21 ` Rodrigo Vivi
2018-10-04 19:53 ` jonsmirl
2018-10-05 7:21 ` Geert Uytterhoeven
2018-10-08 21:35 ` Mauro Carvalho Chehab
2018-10-08 23:20 ` Rodrigo Vivi
2018-10-09 10:07 ` Mauro Carvalho Chehab
2018-10-09 15:59 ` Rodrigo Vivi
2018-10-09 16:52 ` Chris Mason
2018-10-09 22:03 ` Dan Williams
2018-10-10 6:47 ` Geert Uytterhoeven
2018-10-10 13:57 ` Mauro Carvalho Chehab
2018-10-10 17:21 ` Josh Triplett
2018-10-10 18:28 ` Mauro Carvalho Chehab
2018-10-10 19:56 ` Josh Triplett
2018-10-10 20:12 ` Mauro Carvalho Chehab
2018-10-10 20:17 ` Josh Triplett [this message]
2018-10-04 19:34 ` Laurent Pinchart
2018-10-04 20:39 ` Al Viro
2018-10-04 20:56 ` Jonathan Corbet
2018-10-04 21:27 ` Thomas Gleixner
2018-10-04 22:04 ` Jonathan Corbet
2018-10-05 16:03 ` Theodore Y. Ts'o
2018-10-04 22:05 ` Tim.Bird
2018-10-05 6:23 ` Christoph Hellwig
2018-10-05 7:12 ` Geert Uytterhoeven
2018-10-05 7:50 ` Josh Triplett
2018-10-05 9:20 ` Jani Nikula
2018-10-05 9:57 ` Laurent Pinchart
2018-10-05 10:45 ` Joe Perches
2018-10-05 10:55 ` Laurent Pinchart
2018-10-05 12:59 ` Jani Nikula
2018-10-05 13:09 ` Laurent Pinchart
2018-10-05 15:17 ` James Bottomley
2018-10-05 18:28 ` Josh Triplett
2018-10-05 18:39 ` James Bottomley
2018-10-04 20:57 ` Josh Triplett
2018-10-05 7:16 ` Geert Uytterhoeven
2018-10-05 7:51 ` Josh Triplett
2018-10-05 8:00 ` Geert Uytterhoeven
2018-10-05 8:44 ` Josh Triplett
2018-10-05 15:26 ` James Bottomley
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=20181010201759.GA3300@localhost \
--to=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mchehab+samsung@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).