Re: Code of Conduct plan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: James Keener <jim(at)jimkeener(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Code of Conduct plan
Date: 2018-06-05 17:08:20
Message-ID: 3092.1528218500@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers pgsql-www

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> Tangential, are there plans to increase number of core team members. IIRC
> its actually decreased by one between the time of the first proposal of the
> CoC and now.

We're thinking about it, but it's not something to be hasty over.

> As an outside observer I am a bit curious that the Core Team wouldn't be
> able to handle accepting the, likely low volume, of complaints directly; is
> the management of a committee necessary?

That's more or less how things have worked up to now, or really not
worked, because there have been hardly any incidents in which anyone
approached core for such a complaint. I would say there are a number
of things wrong with it:

1. Nobody knows that they could approach core on such a matter;

2. Nobody knows exactly what sorts of matters core might be willing
to act on;

3. There's no appeal process, nor any clean way to deal with the
situation if the complaint is against a core member. (Which is a
case I sure hope never happens, but we ought to design to handle it.)

So publishing a formal CoC at all is mainly meant to deal with weak
points 1 and 2, and then the details of the process are there to try
to fix point 3.

Yeah, managing the committee is a lot of overhead that in an ideal
world we wouldn't need, but I think we have to accept it to have a
process people will have confidence in.

regards, tom lane

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Chris Travers 2018-06-05 17:26:06 Re: Code of Conduct plan
Previous Message Benjamin Scherrey 2018-06-05 17:05:25 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2018-06-05 17:26:06 Re: Code of Conduct plan
Previous Message Benjamin Scherrey 2018-06-05 17:05:25 Re: Code of Conduct plan

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-06-05 17:08:38 Re: Remove mention in docs that foreign keys on partitioned tables are not supported
Previous Message Peter Eisentraut 2018-06-05 17:06:01 Re: libpq compression

Browse pgsql-www by date

  From Date Subject
Next Message Chris Travers 2018-06-05 17:26:06 Re: Code of Conduct plan
Previous Message Benjamin Scherrey 2018-06-05 17:05:25 Re: Code of Conduct plan