Re: Code of Conduct plan

From: Jeremy Schneider <schnjere(at)amazon(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Code of Conduct plan
Date: 2018-06-06 18:51:19
Message-ID: 4c72b19b-08dd-efbd-0582-72177b460d61@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers pgsql-www

On 6/6/18 11:24, David G. Johnston wrote:
> Yeah, while it is pretty much self-evident I would agree that stating
> it explicitly would benefit the document.  Both parts.
>
> On the topic of privacy - who exactly, from an administrative aspect,
> has access to the systems that house these kinds of confidential
> communications?  Do these emails end up in PostgreSQL.org servers
> long-term or is it mainly transient distribution and only individual's
> personal email accounts, with whatever hosting provider they choose,
> hold the messages long-term?

I was just thinking the same question.  Given the technical nature of
our audience, it's fair to assume many people will think about this. 
It's not just about technology either; if someone considers reporting
harassment they should have confidence that friends on the core team
won't talk about the report at the bar.  I don't think these things are
self-evident; it's sometimes obvious what the right thing is to do, but
frankly there are too many cases where people didn't do the right thing
in the past. That's why there's generally high relational and
professional risk for people to report harassment.

Maybe something general like "Confidentiality will be maintained; the
committee/core member in question will not gain access to any
information from the report or proceedings directly or indirectly at any
point in time."

I could see some value to stating it.  But this isn't a requirement, and
I also highly value the concision of the current draft.  So we'll see
what happens.  :)

-Jeremy

--
Jeremy Schneider
Database Engineer
Amazon Web Services

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Jan Claeys 2018-06-07 00:14:48 Re: Code of Conduct plan
Previous Message Tom Lane 2018-06-06 18:36:53 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2018-06-06 18:52:02 Re: Slow planning time for simple query
Previous Message Tom Lane 2018-06-06 18:36:53 Re: Code of Conduct plan

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2018-06-06 19:22:19 Pushing down join clauses into subqueries
Previous Message Tom Lane 2018-06-06 18:36:53 Re: Code of Conduct plan

Browse pgsql-www by date

  From Date Subject
Next Message Peter Eisentraut 2018-06-06 20:20:24 Re: SCRAM with channel binding downgrade attack
Previous Message Tom Lane 2018-06-06 18:36:53 Re: Code of Conduct plan