| From: | Buford Tannen <buford(at)biffco(dot)net> |
|---|---|
| To: | Regina Obe <lr(at)pcorp(dot)us>, "'Joshua D(dot) Drake'" <jd(at)commandprompt(dot)com>, 'Brian Dunavant' <brian(at)omniti(dot)com> |
| Cc: | 'Scott Mead' <scottm(at)openscg(dot)com>, 'Adrian Klaver' <adrian(dot)klaver(at)aklaver(dot)com>, 'Gavin Flower' <GavinFlower(at)archidevsys(dot)co(dot)nz>, 'PostgreSQL General' <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Code of Conduct: Is it time? |
| Date: | 2016-01-11 21:55:00 |
| Message-ID: | 569424B4.2070602@biffco.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Regina Obe wrote:
>
> If we do write a CoC, can we give it a different acronym.
Notwithstanding the most regrettable childhood trauma, this request is
exactly the kind of ridiculousness that the Political Correctness
nonsense associated with CoCs that we should be worried about in the
aftermath of proposed adoption.
Complaining that the acronym "CoC" is anything remotely like the thing
the work "cock" means is, well, cockamamie
It's like someone becoming upset over the work "niggardly" as a racist
epithet. In fact that word and the one you are thinking of are
completely unrelated: entirely different etymology. Nothing in common
except, on the one hand, as you imagine the acronym might be pronounced,
and on the other because there are six similar letters.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Saulo Merlo | 2016-01-11 21:58:42 | Re: Slow Query - PostgreSQL 9.2 |
| Previous Message | Kevin Grittner | 2016-01-11 21:53:37 | Re: Code of Conduct: Is it time? |