| From: | Dmitri Maziuk <dmaziuk(at)bmrb(dot)wisc(dot)edu> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "pgsql-advocacy(at)lists(dot)postgresql(dot)org" <pgsql-advocacy(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Code of Conduct plan |
| Date: | 2018-09-17 15:11:36 |
| Message-ID: | 20180917101136.d348dbb534b2b26256be5fe4@bmrb.wisc.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general pgsql-hackers pgsql-www |
On Sun, 16 Sep 2018 12:52:34 +0000
Martin Mueller <martinmueller(at)northwestern(dot)edu> wrote:
> ... The overreach is dubious on both practical and theoretical grounds. "Stick to your knitting " or the KISS principle seem good advice in this context.
Moderated mailing lists ain't been broken all these years, therefore they need fixing. Obviously.
--
Dmitri Maziuk <dmaziuk(at)bmrb(dot)wisc(dot)edu>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2018-09-17 15:27:48 | Re: Code of Conduct plan |
| Previous Message | Steve Litt | 2018-09-17 03:35:58 | Re: Code of Conduct plan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2018-09-17 15:21:41 | Re: Logical locking beyond pg_advisory |
| Previous Message | Merlin Moncure | 2018-09-17 15:10:24 | Re: Logical locking beyond pg_advisory |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2018-09-17 15:13:28 | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| Previous Message | Tom Lane | 2018-09-17 14:48:32 | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2018-09-17 15:27:48 | Re: Code of Conduct plan |
| Previous Message | Steve Litt | 2018-09-17 03:35:58 | Re: Code of Conduct plan |