Re: Code of Conduct plan

On Thu, Sep 20, 2018 at 07:12:22AM +0200, Chris Travers wrote: > If we have a committer who loudly and proudly goes to neo-nazi rallies or > pickup artist / pro-rape meetups, then actually yes, I have a problem with > that. That impacts my ability to work in the community, impacts every

Re: Code of Conduct plan

I would like to see us, as a group, do better. We should tolerate less bad behavior in ourselves and in others, and however good or bad we are today as people, we should try to be better people. Whether or not the code of conduct plan that the core committee has decided to implement is likely t

Re: Code of Conduct plan

This also highlights the problem of trying to enforce norms across global projects. My view simply is that we cannot. There are probably some rare cases even more extreme than this where enforcement globally might not be a problem. The goal of a code of conduct is to protect the community an

Re: Code of Conduct plan

On Fri, 14 Sep 2018 at 23:11, James Keener wrote: > And if you believe strongly that a given statement you may have made is >> not objectionable...you should be willing to defend it in an adjudication >> investigation. > > > So because someone doesn't like what I say in a venue 100% separate from

Re: Code of Conduct

On 09/19/2018 04:27 PM, Kevin Grittner wrote: On Tue, Sep 18, 2018 at 5:28 AM Dave Page wrote: The PostgreSQL Core team are pleased to announce that following a long consultation process, the project’s Code of Conduct (CoC) has now been finalised and published at https

Re: Code of Conduct

On Tue, Sep 18, 2018 at 5:28 AM Dave Page wrote: > > The PostgreSQL Core team are pleased to announce that following a long > consultation process, the project’s Code of Conduct (CoC) has now been > finalised and published at https://www.postgresql.org/about/policies/coc/. > >

Re: Code of Conduct

Greetings, * Francisco Olarte (fola...@peoplecall.com) wrote: > I will happily pardon brevity ( although I would not call a ten line > sig plus a huge bottom quote "breve", and AFAIK it means the same in > english as in spanish ) and/or typos, but the "I am not responsible" > feels nearly insultin

Re: Code of Conduct

Sorry, I emailed using my company account and thus the long sig. In an effort to avoid further insulting Mr Olarte, I will delete it this time.See, Self-policing works ! Fred

Re: Code of Conduct

On Wed, Sep 19, 2018 at 5:27 PM, Fred Pratt wrote: > Keep pg open and free. This smells of PC police. This community can > police itself No comment on this, just kept for context. > Sent from my mobile device. Please pardon my brevity and typos. I am not > responsible for changes made by

Re: Code of Conduct

groups I've been part of. Especially since this is the main place to come to get help for PostgreSQL and not a social club. Jim On September 18, 2018 6:27:56 AM EDT, Dave Page mailto:dp...@postgresql.org>> wrote: The PostgreSQL Core team are pleased to announce that f

Re: Code of Conduct

become a tool to enforce social > ideology like in other groups I've been part of. Especially since this is > the main place to come to get help for PostgreSQL and not a social club. > > Jim > > On September 18, 2018 6:27:56 AM EDT, Dave Page > wrote: >> >> The P

Re: Code of Conduct plan

I see a CoC as an infiltration of the PostgreSQL community which has worked OK since at least 10 years. The project owners have let their care slacken. I request that the project owners EXPEL/EXCOMMUNICATE ALL those who are advancing what can only be seen as an instrument for harassing members of a

Re: Code of Conduct

said, it is genuinely hard to sort through the noise and try to reach the > signal. I think the resurgence of the debate about whether we need a code > of conduct made it very difficult to discuss specific objections to > specific wording. So to be honest the breakdown was mutual. I wo

Re: Code of Conduct

nd concern with regard to one specific sentence added got much of a hearing. This being said, it is genuinely hard to sort through the noise and try to reach the signal. I think the resurgence of the debate about whether we need a code of conduct made it very difficult to discuss specific objection

Re: Code of Conduct

> > You may dislike the outcome, but it was not ignored. I can accept that I don't like the outcome, but I can point to maybe a dozen people in the last exchange worried about the CoC being used to further political goals, and the only response was "well, the CoC Committee will handle it reasona

Re: Code of Conduct

On 09/18/2018 01:47 PM, James Keener wrote: > following a long consultation process It's not a consultation if any dissenting voice is simply ignored. Don't sugar-coat or politicize it like this -- it was rammed down everyone's throats. That is core's right, but don't act as everyone's opinions

Re: Code of Conduct

tgreSQL and not a social club. Jim On September 18, 2018 6:27:56 AM EDT, Dave Page wrote: >The PostgreSQL Core team are pleased to announce that following a long >consultation process, the project’s Code of Conduct (CoC) has now been >finalised and published at >https://www.pos

Code of Conduct

The PostgreSQL Core team are pleased to announce that following a long consultation process, the project’s Code of Conduct (CoC) has now been finalised and published at https://www.postgresql.org/about/policies/coc/. Please take time to read and understand the CoC, which is intended to ensure

Re: Code of Conduct plan

On 09/17/2018 10:39 AM, Chris Travers wrote: > On Mon, Sep 17, 2018 at 5:28 PM Joshua D. Drake > wrote: ... >> My feedback is that those two sentences provide an overarching authority >> that .Org does not have the right to enforce ... > Fascinating that this would, on its face, not apply to a ha

Re: Code of Conduct plan

that is > a bit far reaching. Specifically I think people's main concern is these two > sentences: > > "To that end, we have established this Code of Conduct for community > interaction and participation in the project’s work and the community at > large. This Code

Re: Code of Conduct plan

ountability. At hand it appears that major concern is the CoC trying to be authoritative outside of community channels. As well as wording that is a bit far reaching. Specifically I think people's main concern is these two sentences: "To that end, we have established this Code of Cond

Re: Code of Conduct plan

On Sun, 16 Sep 2018 12:52:34 + Martin Mueller wrote: > ... The overreach is dubious on both practical and theoretical grounds. > "Stick to your knitting " or the KISS principle seem good advice in this > context. Moderated mailing lists ain't been broken all these years, therefore they ne

Re: Code of Conduct plan

As long as subscribers to the list or attendants at a conference do not violate explicit or implicit house rules, what business does Postgres have worrying about what they do or say elsewhere? Some version of an 'all-of-life' clause may be appropriate to the Marines or federal judges, but it s

Code of Conduct plan

On 2018-09-16 00:00, Mark Kirkwood wrote: > On 15/09/18 08:17, Tom Lane wrote: >> Yeah, this.  The PG community is mostly nice people, AFAICT.  I'll be >> astonished (and worried) if the CoC committee finds much to do.  We're >> implementing this mostly to make newcomers to the project feel that >>

Re: Code of Conduct plan

On 15/09/18 08:17, Tom Lane wrote: Yeah, this. The PG community is mostly nice people, AFAICT. I'll be astonished (and worried) if the CoC committee finds much to do. We're implementing this mostly to make newcomers to the project feel that it's a safe space. Agreed. However I think the a

Re: Code of Conduct plan

ot together and decided to impose a vaguely-worded code of conduct on a vaguely-defined group of people covering not only their work on PostgreSQL but also their entire life. It is not difficult to imagine that someone's private life might include "behavior that may bring the PostgreS

Re: Code of Conduct plan

Dear all, On Fri, Sep 14, 2018 at 5:18 PM Tom Lane wrote: > Robert Haas writes: > > It's not clear to me that there IS a general consensus here. It looks > > to me like the unelected core team got together and decided to impose > > a vaguely-worded code of conduct

Re: Code of Conduct plan

Robert Haas writes: > It's not clear to me that there IS a general consensus here. It looks > to me like the unelected core team got together and decided to impose > a vaguely-worded code of conduct on a vaguely-defined group of people > covering not only their work on PostgreS

Re: Code of Conduct plan

r and decided to impose a vaguely-worded code of conduct on a vaguely-defined group of people covering not only their work on PostgreSQL but also their entire life. It is not difficult to imagine that someone's private life might include "behavior that may bring the PostgreSQL project into

Re: Code of Conduct plan

On 09/14/2018 07:41 AM, James Keener wrote: > Community is people who joined it We're not a "community." I do not think you are going to get very many people on board with that argument. As anyone who knows me will attest I am one of the most contrarian members of this community but I still

Re: Code of Conduct plan

On Fri, 14 Sep 2018, 15:55 James Keener, wrote: > > > Yes. They can. The people who make the majority of the contributions to >> the software can decide what happens, because without them there is no >> software. If you want to spend 20 years of your life >> > > So everyone who moderates this gro

Re: Code of Conduct plan

ir own Terms of Use and complaint departments > 3. If it is abuse there are laws > > I agree that within Postgresql.org we must have a professional code of > conduct but the idea that an arbitrary committee appointed by an unelected > board can decide the fate of a community member based

Re: Code of Conduct plan

her Code of Conduct that takes precedence (such as a conference's Code of Conduct)." I second that objection. It is not in PGDG's remit to cure the world, for whatever form of cure you ascribe to. This is especially true as 'community member' has no strict definition. I und

Re: Code of Conduct plan

w is null and void: > > "This Code is meant to cover all interaction between community members, > whether or not it takes place within postgresql.org infrastructure, so > long as there is not another Code of Conduct that takes precedence (such as > a conference's Code of Conduc

Re: Code of Conduct plan

ki.postgresql.org/wiki/Code_of_Conduct > > > >(That's the updated text, but you can use the diff tool on the page > >history tab to see the changes from the previous draft.) > > > >I really have to object to this addition: > >"This Code

Re: Code of Conduct plan

> On 14. Sep 2018, at 16:31, Ilya Kosmodemiansky wrote: > > > > > I could only heavily +1 this. I can get I can’t get of course, sorry for typo > from where comes the idea that community is only what happens just on > postgresql.org or just on some other channel community uses. > . >

Re: Code of Conduct plan

On 09/14/2018 07:36 AM, Dave Page wrote: On Fri, Sep 14, 2018 at 3:21 PM, James Keener > wrote: Now, you may say that (2) would be rejected by the committee, but I would counter that it's still a stain on me and something that

Re: Code of Conduct plan

I hesitate to exacerbate what is a society-wide debate that is being worked out across organizations across the spectrum, but if I may provide a thought for consideration. The framing and language of the Code of Conduct, as written and proposed, includes a large number of checkpoints to protect

Re: Code of Conduct plan

Greetings, * Joshua D. Drake (j...@commandprompt.com) wrote: > I think this is a complicated issue. On the one hand, postgresql.org has no > business telling people how to act outside of postgresql.org. Full stop. This is exactly what this CoC points out- yes, PG.Org absolutely can and should con

Re: Code of Conduct plan

>> history tab to see the changes from the previous draft.) >>> >> >> I really have to object to this addition: >> "This Code is meant to cover all interaction between community members, >> whether or not it takes place within postgresql.org infrastructure

Re: Code of Conduct plan

> > And if you believe strongly that a given statement you may have made is > not objectionable...you should be willing to defend it in an adjudication > investigation. So because someone doesn't like what I say in a venue 100% separate from postgres, I have to subject myself, and waste my time,

Re: Code of Conduct plan

On Fri, Sep 14, 2018 at 3:57 PM, James Keener wrote: > > >> Yes, I believe so. Isn't that what "To that end, we have established >> this Code of Conduct for community interaction and participation in the >> project’s work and the community at large."

Re: Code of Conduct plan

committee would result in a non-violation UNLESS they referenced postgresql within the post? Yes, I believe so. Isn't that what "To that end, we have established this Code of Conduct for community interaction and participation in the project’s work and the community at large." basi

Re: Code of Conduct plan

On Fri, Sep 14, 2018 at 3:55 PM, James Keener wrote: > > > Yes. They can. The people who make the majority of the contributions to >> the software can decide what happens, because without them there is no >> software. If you want to spend 20 years of your life >> > > So everyone who moderates thi

Re: Code of Conduct plan

> > Yes, I believe so. Isn't that what "To that end, we have established this Code > of Conduct for community interaction and participation in the project’s > work and the community at large." basically says? > No? What's the "community at large"? To m

Re: Code of Conduct plan

Yes. They can. The people who make the majority of the contributions to the > software can decide what happens, because without them there is no > software. If you want to spend 20 years of your life > So everyone who moderates this group and that will be part of the CoC committee will have had to

Re: Code of Conduct plan

> To many of us, we absolutely are a community. Remember, there are people > here who have been around for 20+ years, of which many have become close > friends, having started working on PostgreSQL as a hobby. We have always > seen the project as a community of like-minded technologists, and welcom

Re: Code of Conduct plan

> becomes our business. > > If it's unrelated to PostgreSQL, then it's your personal business and not > something the project would get involved in. > > > O.k. so this isn't clear (at least to me) within the CoC. I want to make > sure I understand. You are say

Re: Code of Conduct plan

On Fri, Sep 14, 2018 at 3:41 PM, James Keener wrote: > > Community is people who joined it > > We're not a "community." We're people using email to get help with or > discuss technical aspects of PostgreSQL. The types of discussions that > would normally be held within a "community" would be enti

Fwd: Code of Conduct plan

I didn't realize they had replied personally to me. -- Forwarded message -- From: James Keener Date: Fri, Sep 14, 2018 at 10:43 AM Subject: Re: Code of Conduct plan To: Dave Page If that business is publicly bringing the project into disrepute, or > harassing other c

Re: Code of Conduct plan

the updated text, but you can use the diff tool on the page >>> history tab to see the changes from the previous draft.) >>> >> >> I really have to object to this addition: >> "This Code is meant to cover all interaction between community members, >> whe

Re: Code of Conduct plan

> Community is people who joined it We're not a "community." We're people using email to get help with or discuss technical aspects of PostgreSQL. The types of discussions that would normally be held within a "community" would be entirely off-topic here. We should be professional to each other he

Re: Code of Conduct plan

stgresql.org> infrastructure, so long as there is not another Code of Conduct that takes precedence (such as a conference's Code of Conduct)." That covers things like public twitter messages over live political controversies which might not be personally directed.  

Re: Code of Conduct plan

o this addition: > "This Code is meant to cover all interaction between community members, > whether or not it takes place within postgresql.org infrastructure, so > long as there is not another Code of Conduct that takes precedence (such as > a conference's Code of Conduct)." &

Re: Code of Conduct plan

On Fri, Sep 14, 2018 at 3:21 PM, James Keener wrote: > > Now, you may say that (2) would be rejected by the committee, but I would >>> counter that it's still a stain on me and something that will forever >>> appear >>> along side my name in search results and that the amount of time and >>> stre

Re: Code of Conduct plan

> On 14. Sep 2018, at 16:17, Dave Page wrote: > > > The lists are just one of many different ways people in this community > interact. I could only heavily +1 this. I can get from where comes the idea that community is only what happens just on postgresql.org or just on some other channel

Re: Code of Conduct plan

ace within postgresql.org infrastructure, so long as there is not another Code of Conduct that takes precedence (such as a conference's Code of Conduct)." Not sure how the above can be enforced without someone reporting on what is said outside the 'postgresql.org infrastructure'?

Re: Code of Conduct plan

> Now, you may say that (2) would be rejected by the committee, but I would >> counter that it's still a stain on me and something that will forever >> appear >> along side my name in search results and that the amount of time and >> stress it'd take me to defend myself would make my voluntarily le

Re: Code of Conduct plan

ly have to object to this addition: >>>> "This Code is meant to cover all interaction between community members, >>>> whether or not it takes place within postgresql.org < >>>> http://postgresql.org> >>>> infrastructure, so long as there is

Re: Code of Conduct plan

On Fri, Sep 14, 2018 at 3:10 PM, James Keener wrote: > I understand the concern, however, if you look at how attacks happen > >> it is frequently through other sites. Specifically under/poorly >> moderated sites. For specific examples, people who have issues with >> people on Quora will frequentl

Re: Code of Conduct plan

On Fri, 14 Sep 2018 at 15:10, James Keener wrote: > I understand the concern, however, if you look at how attacks happen > >> it is frequently through other sites. Specifically under/poorly >> moderated sites. For specific examples, people who have issues with >> people on Quora will frequently g

Re: Code of Conduct plan

ithin postgresql.org <http://postgresql.org> infrastructure, so long as there is not another Code of Conduct that takes precedence (such as a conference's Code of Conduct)." I second that objection. It is not in PGDG's remit to cure the world, for whatever form of cure you ascr

Re: Code of Conduct plan

I understand the concern, however, if you look at how attacks happen > it is frequently through other sites. Specifically under/poorly > moderated sites. For specific examples, people who have issues with > people on Quora will frequently go after them on Facebook and Twitter. > > these aren't a s

Re: Code of Conduct plan

ace within postgresql.org <http://postgresql.org> infrastructure, so long as there is not another Code of Conduct that takes precedence (such as a conference's Code of Conduct)." That covers things like public twitter messages over live political controversies which might not be perso

Re: Code of Conduct plan

>> https://wiki.postgresql.org/wiki/Code_of_Conduct >> >> (That's the updated text, but you can use the diff tool on the page >> history tab to see the changes from the previous draft.) >> >> >> I really have to object to this addi

Re: Code of Conduct plan

etween community members, whether or not it takes place within postgresql.org <http://postgresql.org> infrastructure, so long as there is not another Code of Conduct that takes precedence (such as a conference's Code of Conduct)." I second that objection. It is not in PGD

Re: Code of Conduct plan

I have followed this list for a couple of years, have benefited several times from quick and helpful advice, and wonder whether all this code of conduct stuff is a solution in search of a problem. Or, if there is a problem now and then, whether an elaborate code does a better job than

Re: Code of Conduct plan

>members, >> > whether or not it takes place within postgresql.org infrastructure, >so >> long >> > as there is not another Code of Conduct that takes precedence (such >as a >> > conference's Code of Conduct)." >> > >> > That covers things

Re: Code of Conduct plan

the changes from the previous draft.) > > I really have to object to this addition: > "This Code is meant to cover all interaction between community members, > whether or not it takes place within postgresql.org <http://postgresql.org/> > infrastructure, so long as th

Re: Code of Conduct plan

On Fri, Sep 14, 2018 at 10:31 AM, Chris Travers wrote: > I really have to object to this addition: > "This Code is meant to cover all interaction between community members, > whether or not it takes place within postgresql.org infrastructure, so long > as there is not another Cod

Re: Code of Conduct plan

or not it takes place within postgresql.org infrastructure, so > long > > as there is not another Code of Conduct that takes precedence (such as a > > conference's Code of Conduct)." > > > > That covers things like public twitter messages over live political > > cont

Re: Code of Conduct plan

ou can use the diff tool on the page > history tab to see the changes from the previous draft.) > I really have to object to this addition: "This Code is meant to cover all interaction between community members, whether or not it takes place within postgresql.org infrastructure, so long as the

Re: Code of Conduct plan

I wrote: > Stephen Frost writes: >> We seem to be a bit past that timeline... Do we have any update on when >> this will be moving forward? >> Or did I miss something? > Nope, you didn't. Folks have been on holiday which made it hard to keep > forward progress going, particularly with respect t

Re: Code of Conduct plan

Greetings, * Tom Lane (t...@sss.pgh.pa.us) wrote: > Unless there are substantial objections, or nontrivial changes as a result > of this round of comments, we anticipate making the CoC official as of > July 1 2018. We seem to be a bit past that timeline... Do we have any update on when this will

Re: Code of Conduct plan

Stephen Frost writes: > * Tom Lane (t...@sss.pgh.pa.us) wrote: >> Unless there are substantial objections, or nontrivial changes as a result >> of this round of comments, we anticipate making the CoC official as of >> July 1 2018. > We seem to be a bit past that timeline... Do we have any update

Re: Code of Conduct plan

On Wed, Aug 15, 2018 at 03:22:10PM -0400, Stephen Frost wrote: > Greetings, > > * Tom Lane (t...@sss.pgh.pa.us) wrote: > > Unless there are substantial objections, or nontrivial changes as a result > > of this round of comments, we anticipate making the CoC official as of > > July 1 2018. > > We

Code of Conduct committee: call for volunteers

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

Re: Code of Conduct plan

On 5 June 2018 at 17:34, Ozz Nixon wrote: > Sorry... > > > 1) CoC might result in developers leaving projects > > > I know this on going regurgitation is going to cause my team to > leave the project, right around 100 posts on this off topic topic it > was bad enough when the original

Re: Code of Conduct plan

> On Jun 5, 2018, at 15:20, Peter Geoghegan wrote: > I don't follow. Practically any organized group has rules around > conduct, with varying degrees of formality, means of enforcement, etc. I believe the objection is to setting up a separate CoC committee, rather than using the core team as t

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 2:06 PM, Sven R. Kunze wrote: > 1) CoC might result in developers leaving projects > http://lists.llvm.org/pipermail/llvm-dev/2018-May/122922.html This guy left LLVM for several reasons. The pertinent reason for us was that he had to agree to a code of conduct in or

RE: Code of Conduct plan

Sorry... > 1) CoC might result in developers leaving projects I know this on going regurgitation is going to cause my team to leave the project, right around 100 posts on this off topic topic it was bad enough when the original idea came up (2 years ago I think). It used to be exc

Re: Code of Conduct plan

6.2018 20:29, Tom Lane wrote: Two years ago, there was considerable discussion about creating a Code of Conduct for the Postgres community, as a result of which the core team announced a plan to create an exploration committee to draft a CoC [1]. That process has taken far longer than expected, but the

Re: Code of Conduct plan

Greetings, * Magnus Hagander (mag...@hagander.net) wrote: > On Tue, Jun 5, 2018 at 4:45 PM, Chris Travers > wrote: > > If I may suggest: The committee should be international as well and > > include people from around the world. The last thing we want is for it to > > be dominated by people fro

Re: Code of Conduct plan

On Tue, Jun 5, 2018 at 4:45 PM, Chris Travers wrote: > > > On Mon, Jun 4, 2018 at 6:59 PM, Joshua D. Drake > wrote: > >> On 06/03/2018 04:08 PM, Gavin Flower wrote: >> >> My comments: 1) Reiterate my contention that this is a solution is search of problem. Still it looks like it i

Re: [MASSMAIL]Re: Code of Conduct plan

t whoever "snowflake", I find that term hilarious others find it highly offensive. Which is correct? I agree with both concerns in the above exchange. This is an economic common project.  The goal should be for people to come together and act civilly.  Waging culture war using the co

Re: Code of Conduct plan

sive. Which is correct? I agree with both concerns in the above exchange. This is an economic common project.  The goal should be for people to come together and act civilly.  Waging culture war using the code of conduct itself should be a violation of the code of conduct and this goes on *all*

Re: [MASSMAIL]Re: Code of Conduct plan

oever "snowflake", I find that term hilarious others find it highly offensive. Which is correct? I agree with both concerns in the above exchange. This is an economic common project. The goal should be for people to come together and act civilly. Waging culture war using the code of conduct

Re: [MASSMAIL]Re: Code of Conduct plan

hilarious others find it highly offensive. Which is correct? I agree with both concerns in the above exchange. This is an economic common project. The goal should be for people to come together and act civilly. Waging culture war using the code of conduct itself should be a violation of the c

Re: Code of Conduct plan

ed -- also in >> using that that expression "get their knickers in a twist" could offend >> some snowflake) claiming that I'm suggesting that whoever >> > > "snowflake", I find that term hilarious others find it highly offensive. > Which is correct

Re: Code of Conduct plan

> Two years ago, there was considerable discussion about creating a > Code of Conduct for the Postgres community, as a result of which > the core team announced a plan to create an exploration committee > to draft a CoC [1]. That process has taken far longer than expected, > but th

Re: [MASSMAIL]Re: Code of Conduct plan

states that this is about participation within postgresql.org only. It is not postgresql.org's mission or purpose to police actions outside of their domain. The following minor modification would work: "To that end, we have established this Code of Conduct for community interaction and par

Re: Code of Conduct plan

On 06/03/2018 04:08 PM, Gavin Flower wrote: My comments: 1) Reiterate my contention that this is a solution is search of problem. Still it looks like it is going forward, so see below. 2) "... engaging in behavior that may bring the PostgreSQL project into disrepute, ..." This to me is over

Re: Code of Conduct plan

within postgresql.org only. It is not postgresql.org's mission or purpose to police actions outside of their domain. The following minor modification would work: "To that end, we have established this Code of Conduct for community interaction and participation within the Postgresql.o

Re: Code of Conduct plan

Some people are not paying attention and are sending code-of-conduct comments to all lists, not just pgsql-general, but -hackers and -advocacy too. I've seen 3 of these so far today. This is a reminder to please send the comments to pgsql-general only. -- Darren Duncan On 2018-06-03 11:

Re: Code of Conduct plan

On Jun 3, 2018, at 16:08 , Gavin Flower wrote: > > Be very careful in attempting to codify 'correct' behaviour! +1 this is a distraction.

Re: Code of Conduct plan

On 04/06/18 07:32, Adrian Klaver wrote: On 06/03/2018 11:29 AM, Tom Lane wrote: Two years ago, there was considerable discussion about creating a Code of Conduct for the Postgres community, as a result of which the core team announced a plan to create an exploration committee to draft a CoC [1

Re: Code of Conduct plan

On 06/03/2018 11:29 AM, Tom Lane wrote: Two years ago, there was considerable discussion about creating a Code of Conduct for the Postgres community, as a result of which the core team announced a plan to create an exploration committee to draft a CoC [1]. That process has taken far longer than

Re: Code of Conduct plan

Two years ago, there was considerable discussion about creating a Code of Conduct for the Postgres community, as a result of which the core team announced a plan to create an exploration committee to draft a CoC [1]. That process has taken far longer than expected, but the committee has not been