Code of Conduct committee: call for volunteers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, PostgreSQL Advocacy <pgsql-advocacy(at)lists(dot)postgresql(dot)org>
Subject: Code of Conduct committee: call for volunteers
Date: 2018-06-07 20:57:36
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-advocacy pgsql-general pgsql-hackers

The proposed Postgres Code of Conduct [1] calls for an investigation
and enforcement committee, which is to be appointed by and ultimately
answerable to the core team, though no core members may sit on it.

The core team is pleased to announce that Stacey Haysler has agreed
to serve as the first Chair of the CoC committee. Many of you know
Stacey from various conferences etc, and I don't feel that I need to
repeat her excellent qualifications for this task.

While we have a few names in mind for additional committee members,
we need more in order that the committee can represent a diverse
range of viewpoints and cultures. Therefore we are calling for
volunteers, as indeed is required by the proposed CoC. This call
will remain open until June 15; the committee membership will be
decided and announced before the end of June.

We encourage community members who, perhaps, have not previously
taken large roles in the community to step forward for this.
What is needed is not technical skills but empathy and the ability
to understand varying viewpoints.

If you are interested in serving, please write to coc(at)postgresql(dot)org
(do not follow up to this message). Please include answers to these

1. What interests you about being on the CoC Committee?

2. Have you been on another CoC Committee, or had a similar role at
another organization? (Prior experience is not required, it's just
helpful to know everyone's background.)

3. What else would you like to tell us that is helpful for us to know
about your potential involvement with the CoC Committee?

regards, tom lane



Browse pgsql-hackers by date

  From Date Subject
Next Message Nico Williams 2018-06-07 21:00:59 Re: [PATCH v16] GSSAPI encryption support
Previous Message Tom Lane 2018-06-07 20:22:23 Re: Performance regression with PostgreSQL 11 and partitioning

Browse pgsql-advocacy by date

  From Date Subject
Next Message Simon Riggs 2018-06-08 08:46:57 Re: Code of Conduct plan
Previous Message Chris Travers 2018-06-07 07:00:29 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2018-06-07 21:34:55 Re: Query hitting empty tables taking 48 minutes
Previous Message Laurenz Albe 2018-06-07 20:15:55 Re: Query hitting empty tables taking 48 minutes