Re: Code of Conduct plan
От | Melvin Davidson |
---|---|
Тема | Re: Code of Conduct plan |
Дата | |
Msg-id | CANu8FixGdAM0trxfo_dnLVmRB2mjfwWe_NBRQp+qS=-XKYbOPQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Code of Conduct plan (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Code of Conduct plan
Re: Code of Conduct plan |
Список | pgsql-general |
How about we just simplify the code of conduct to the following:
Any member in the various PostgreSQL lists is expected to maintain
respect to others and not use foul language. A variation from
the previous sentence shall be considered a violation of the CoC.
Any member in the various PostgreSQL lists is expected to maintain
respect to others and not use foul language. A variation from
the previous sentence shall be considered a violation of the CoC.
On Sat, Sep 15, 2018 at 11:51 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Bruce Momjian <bruce@momjian.us> writes:
> There is a risk that if we adopt a CoC, and nothing happens, and the
> committee does nothing, that they will feel like a failure, and get
> involved when it was best they did nothing. I think the CoC tries to
> address that, but nothing is perfect.
Yeah, a busybody CoC committee could do more harm than good.
The way the CoC tries to address that is that the committee can't
initiate action of its own accord: somebody has to bring it a complaint.
Of course, a member of the committee could go out and find a "problem"
and then file a complaint --- but then they'd have to recuse themselves
from dealing with that complaint, so there's an incentive not to.
regards, tom lane
--
Melvin Davidson
Maj. Database & Exploration Specialist
Universe Exploration Command – UXC
Employment by invitation only!
Maj. Database & Exploration Specialist
Universe Exploration Command – UXC
Employment by invitation only!
В списке pgsql-general по дате отправления: