|From:||Josh Berkus <josh(at)agliodbs(dot)com>|
|To:||PostgreSQL general <pgsql-general(at)postgresql(dot)org>|
|Cc:||PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>|
|Subject:||Code of Conduct plan|
|Views:||Raw Message | Whole Thread | Download mbox|
|Lists:||pgsql-advocacy pgsql-general pgsql-hackers pgsql-www|
A number of people have contacted the Core Team about taking action
regarding a Code of Conduct (CoC) for the project. After some
discussion, the plan we have come up with is below.
**Please do not reply-all to this email, as we do not wish to generate
additional list traffic regarding CoCs**
1. The Core Team will appoint an exploration committee which will look
at various proposals (including the one drafted on pgsql-general) for
CoCs and discuss them. This committee will include both major community
members and less central folks who have hands-on experience with CoCs
and community management issues. If you know of PostgreSQL community
members who have relevant experience, please nominate them by emailing
the core team: pgsql-core(at)postgresql(dot)org(dot)
2. We will also hire a professional consultant to advise the committee
on CoC development, adoption, training, and enforcement. Again, if
community members have a consultant to recommend, please email the core
3. This committee will post a draft CoC or possibly a selection of draft
CoCs by or before late April for community comment. Likely the
committee will be publishing drafts more frequently, but that will be up
to them to work out.
4. At the pgCon Community Unconference, and again at pgconf.EU, we will
have sessions where people can discuss and provide feedback about
proposed (or adopted) CoCs. Possibly we will have CoC-related trainings
5. Once a draft is agreed upon, it will be circulated to our various
sub-communities for comment.
6. A "final" CoC will be endorsed by the committee and the Core Team
shortly after pgConf.EU, unless there is sufficently strong consensus to
adopt one before then.
Yes, we realize this is a long timeline. The PostgreSQL Project has
never been about implementing things in a hurry; our practice has always
been to take all of the time required to develop the right feature the
right way. Adopting a CoC is no different; if anything, we need to take
*more* time in order to get input from community members who do not
speak up frequently or assertively.
In the meantime, our policy remains: if you have experienced harassment
or feel that you are being treated unfairly by other project members,
email the Core Team and we will investigate your complaint and take
Also, we want to thank Josh Drake for raising the CoC issue and getting
it off the TODO list and into process, and devising an initial "seed"
CoC. Such things are all too easy to keep postponing.
Again, Please DO NOT comment on this plan on-list; one of the pieces of
feedback we have received loud and clear is that many community members
are unhappy with the amount of list traffic devoted to the subject of
CoCs. As such, if you have comments on the plan above, please email the
core team instead of replying on-list, or wait for the committee and
address comments to them.
PostgreSQL Core Team
|Next Message||benjamin barber||2016-02-08 10:04:32||Re: Code of Conduct plan|
|Previous Message||Alvaro Herrera||2016-01-18 16:52:03||Re: 20th anniversary of PostgreSQL ?|
|Next Message||Tatsuo Ishii||2016-01-27 05:13:07||Re: Why format() adds double quote?|
|Previous Message||Pavel Stehule||2016-01-27 04:56:24||Re: Why format() adds double quote?|
|Next Message||Alexander Pyhalov||2016-01-27 08:06:55||pgpool II, streaming replication and HA|
|Previous Message||leo||2016-01-27 02:42:37||Does pglogical support PG 9.4.5?|
|Next Message||Josh Kupershmidt||2016-01-28 19:53:44||Re: Editor privs?|
|Previous Message||Oleg Bartunov||2016-01-26 11:12:55||Re: archives.postgresql.org problem|