| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | 'Regina Obe *EXTERN*' <lr(at)pcorp(dot)us>, 'Roxanne Reid-Bennett' <rox(at)tara-lu(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: A motion |
| Date: | 2016-01-25 08:55:41 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B537D7123@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Regina Obe wrote:
> At this point I feel we should:
>
> a) Move this to pgsql-advocacy [...]
> Or
>
> b) Start a new PostgreSQL mailing list - call it - pgsql-coc.
-1
While I personally feel that a code of conduct does not need to be an explicit
document and is something that "happens" through the way people on the lists
behave and the way the core team and list maintainers handle problems,
pgsql-general is where the community meets, and that is where such a discussion
should take place.
If it annoys some people, so be it; if people express their dislike, that's
a statement as well. A code of conduct is about non-technical implications
of activity on the mailing lists, so using the non-technical nature of this
discussion as a reason to push it off the radar is counter-productive.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2016-01-25 09:44:06 | Re: Performance options for CPU bound multi-SUM query |
| Previous Message | Tom Smith | 2016-01-25 08:55:20 | Re: TABLESAMPLE usage |