From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
Cc: | tomas(dot)vondra(at)2ndquadrant(dot)com, James Keener <jim(at)jimkeener(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, dpage(at)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Code of Conduct |
Date: | 2018-09-18 17:14:30 |
Message-ID: | 20180918171430.GF4184@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Greetings,
* Chris Travers (chris(dot)travers(at)gmail(dot)com) wrote:
> I said I would stand aside my objections after the last point I mentioned
> them but I did not feel that my particular objection and concern with
> regard to one specific sentence added got much of a hearing. This being
> said, it is genuinely hard to sort through the noise and try to reach the
> signal. I think the resurgence of the debate about whether we need a code
> of conduct made it very difficult to discuss specific objections to
> specific wording. So to be honest the breakdown was mutual.
I would ask that you, and anyone else who has a suggestion for how to
improve or revise the CoC, submit your ideas to the committee by
email'ing coc(at)postgresql(dot)org(dot)
As was discussed previously, the current CoC isn't written in stone and
it will be changed and amended as needed.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-09-18 18:35:54 | Re: Code of Conduct |
Previous Message | Tom Lane | 2018-09-18 17:10:26 | Re: Select into table%ROWTYPE failed |
From | Date | Subject | |
---|---|---|---|
Next Message | Hironobu SUZUKI | 2018-09-18 17:15:51 | Re: pgbench - add pseudo-random permutation function |
Previous Message | Chris Travers | 2018-09-18 17:08:09 | Re: Code of Conduct |