Re: [GENERAL] Book or other resource on Postgres-local code?

> As an aside from my last question about my LYDB effort: > https://medium.com/@gisborne/love-your-database-lydb-23c69f480a1d#.4jngp2rcb > I would like to find a book or other resource about SQL server-side > programming (stored procedures etc) best practices in general and for > Postgres in p

Re: [GENERAL] Code of Conduct: Is it time?

Josh informed me you guys are thinking about a CoC. Let me start off by saying that I don't think you need one and in fact having one may be dangerous. I fear for your safety. I think Roxanne mentioned some good points in an earlier thread that you should itemize what you expect to achieve with

Re: [GENERAL] Code of Conduct: Is it time?

> I was at the 2015 Australian Linux Conference (held in Auckland, NZ), when Sarah Sharp harangued Linus Torvalds for over 20 minutes. Linus remained calm and polite throughout, yet most people would have been obviously annoyed within the first 5 minutes. As backround see: > http://www.networkwor

Re: [GENERAL] Code of Conduct: Is it time?

> On 01/10/2016 08:07 AM, Bill Moran wrote: >> So, the purpose of a CoC is twofold: >> >> A) Define what "being excellent" means to this particular >> community. >> B) Provide a process for how to resolve things when "being >> excellent" doesn't happen. >> >> Without #1, nobody will want t

Re: [GENERAL] Code of Conduct: Is it time?

>> She won Red Hat Woman of the Year Award - >> https://www.redhat.com/en/about/women-in-open-source >> >> Sarah Sharp >> 2015 Community Award winner >> >> Am I the only one concerned about some of the women role models we have in >> FOSS? > Am I, as a mere male, entitled to have an opinion on this

Re: [GENERAL] Code of Conduct: Is it time?

> On 01/10/2016 10:44 AM, Regina Obe wrote: >>> JD >> >> This may come as a big shock to many of you, but as a contributor I >> don't care if you are racist, sexist, transphobic or whatever as long >> as you > I think this is reasonable but my point

Re: [GENERAL] Code of Conduct: Is it time?

Gavin, > I once went out of my way to help someone with Mac. They were so Mac centric they did not realize that they were not giving us the right information to help them, but this was not obvious until later in the thread. I made some comment about Linux - next moment they were accusing > every

Re: [GENERAL] Code of Conduct: Is it time?

>ISTM that if we develop a code of conduct, it would need to be designed to > insulate the community and individuals within it from becoming targets of > legal action. "Mike said I was bad at postgres, it hurt my consulting and I > want to sue Joe for replying-all and upping the hit-count o

Re: [GENERAL] Code of Conduct: Is it time?

Brian, >> We expect of everyone in our spaces to try their best to do the same >> in a kind and gentle manner. If you feel it's just a minor offense and >> the person didn't mean harm by it, >> >> simply ignore it unless the pattern of talk continues. If the person >> continues or they say some

Re: [GENERAL] Code of Conduct: Is it time?

ks, Regina -Original Message- From: Joshua D. Drake [mailto:j...@commandprompt.com] Sent: Monday, January 11, 2016 2:00 PM To: Regina Obe ; 'Brian Dunavant' Cc: 'Scott Mead' ; 'Adrian Klaver' ; 'Gavin Flower' ; 'PostgreSQL General' Su

Re: [GENERAL] Code of Conduct: Is it time?

> Regina, > Although I can appreciate your sensitivity to the terminology based on your > experience (and I am very sorry to read about that), I don't think it is > reasonable to change from an Industry Standard acronym on that basis. > Sincerely, > JD Fair enough. -- Sent via pgsql-g

[GENERAL]

> On Mon, Jan 11, 2016 at 12:39:12PM -0500, Regina Obe wrote: >> HANDLING ISSUES >... >> If you have contributed nothing to our project and you make >> demands for change, we will try to tell you that kindly and >> request you to change or leave. > May I kind

Re: [GENERAL] Code of Conduct: Is it time?

Sorry screwed up sending this email the first time. Trying again: > On Mon, Jan 11, 2016 at 12:39:12PM -0500, Regina Obe wrote: >> HANDLING ISSUES >... >> If you have contributed nothing to our project and you make >> demands for change, we will try to tell you that k

Re: [GENERAL] Code of Conduct

Geoff, > Gosh, I've got a lot of love for CoCs; I've heard great things, really good > things, some things, about CoCs, that some of them have been really helping > in a yuge way with some fantastic projects. > Sometimes some people, a lot of people, have said that I could write a CoC, > and y

Re: [GENERAL] Code of Conduct: Is it time?

> Hmm. I'm not sure that telling us that should amount to an offense; such a person might even have a good idea from time to time. > Now, if the person is rude about it, that would be an offense, but that should already be covered under other sections of the CoC no? > Another possibly offensive

Re: [GENERAL] Code of Conduct

Geoff, > If there were a CoC that would explicitly disallow occasional lighthearted > humour to a non-development list that is intended to offend no-one then I > would most definitely remove myself from such a project. > Some may consider that a positive thing, but I would like to think that i

Re: [GENERAL] Code of Conduct: Is it time?

Regina Obe wrote: > > If we do write a CoC, can we give it a different acronym. > Notwithstanding the most regrettable childhood trauma, this request is > exactly the kind of ridiculousness that the Political Correctness nonsense > associated with CoCs that we should be worri

Re: [GENERAL] WIP: CoC

> 2. The CoC is not about being offended. The act of being offended is purely a > recipient response and usually the offended individual is more interested in > being a victim than moving forward. Here is my latest version. Let me know if I should throw in a github repo so it's easier to read

Re: [GENERAL] WIP: CoC

> """ A safe, respectful, productive and collaborative environment is free of > non-technical or personal comments related to gender, sexual orientation, > disability, physical appearance, body size or race. """ I really think you should leave out the whole " gender, sexual orientation, disabi

Re: [GENERAL] WIP: CoC

nconvience to a lot of people" are rarely good reasons to dismiss a valid > objection to a term. I left the door open for that intentionally – we are more okay with changing new undecided terms than old terms. I should add cost in there. > Also, why did you have a quote at the to

Re: [GENERAL] WIP: CoC

> That has nothing to do with the Code of Conduct, though. The community > accepting Tom saying "no" to Feature X is vastly different than the community > not calling Tom out for being mean. > The CoC is about the later situation and not the prior; and the community > should call Tom out. (

Re: [GENERAL] WIP: CoC

Jim, > That has nothing to do with the Code of Conduct, though. The community > accepting Tom saying "no" to Feature X is vastly different than the community > not calling Tom out for being mean. > The CoC is about the later situation and not the prior; and the community > should call Tom out

Re: [GENERAL] WIP: CoC V2

Josh, > tl;dr; > * Modified #2 to be less harsh. > * Modified #3 with TGL and James comments > * Did not remove examples as I believe they are vital to the success > I saw Regina's post, I believe it is good for context but I also believe that > something concise and to the point is the better

Re: [GENERAL] Code of Conduct: Is it time?

women. Thanks, Regina From: Chris Travers [mailto:chris.trav...@gmail.com] Sent: Tuesday, January 12, 2016 3:05 AM To: Regina Obe Cc: Buford Tannen ; Joshua D. Drake ; Brian Dunavant ; Scott Mead ; Adrian Klaver ; Gavin Flower ; PostgreSQL General Subject: Re: [GENERAL] Code of Conduct:

Re: [GENERAL] Code of Conduct: Is it time?

Chris, >> For a Coc – I think it should be light, but make it clear that we do not >> tolerate strangers coming into our group and demanding us to accept their >> code, cause we want to be welcoming and show we have at least 15% of code >> contributions from women. > One of the dangers of

Re: [GENERAL] Code of Conduct: Is it time?

> On 12 January 2016 at 09:25, Chris Travers wrote: >> One of the dangers of a CoC is that there are many potential issues >> which may or may not become real problems. I think if we try to be >> clear on all of them, then we risk creating codes instead of a general >> expectation of what we

Re: [GENERAL] WIP: CoC

> If the attacker goes public, we point people at the exchange that happened > where Tom has presumably already discussed the reasons that the > patch/feature/&c isn't being accepted. If someone wanted to out someone, they would study them carefully. They would find Tom's buttons and push the

Re: [GENERAL] WIP: CoC

nalyze why all of us had such opposing view points and couldn't even agree with each other. Thanks, Regina From: James Keener [mailto:j...@jimkeener.com] Sent: Tuesday, January 12, 2016 9:20 AM To: Regina Obe ; 'Psql_General (E-mail)' Subject: RE: WIP: CoC Wow. I mea

Re: [GENERAL] WIP: CoC

> everyone should be excellent to one another, as defined in a general CoC I think CoralineAda has debated extensively why being excellent is not sufficient. https://modelviewculture.com/pieces/codes-of-conduct-when-being-excellent-is-not-enough I personally don't have the patience to

Re: [GENERAL] WIP: CoC

ntra buy calling his Coc a Vagina. I was beginning to feel like everyone was against me. Love, Regina From: Bret Stern [mailto:bret_st...@machinemanagement.com] Sent: Tuesday, January 12, 2016 11:01 AM To: Regina Obe Cc: 'James Keener' ; 'Psql_General (E-mail)'

Re: [GENERAL] WIP: CoC V5

This looks much better than earlier editions. I think this one I could avoid violating without too much trouble. When we talk about community commons, does that include physical spaces? I'm trying to visualize what "safe" means in a virtual space and I'm drawing a blank picture. Thank

Re: [GENERAL] WIP: CoC V5

> On 13 January 2016 at 03:10, Tom Lane wrote: >> The "disparaging remarks" part of this could easily be taken to forbid >> technical criticism of any sort, eg "this patch is bad because X,Y, >> and Z", even when X,Y, and Z are perfectly neutral technical points. >> "Of any kind" doesn't impr

Re: [GENERAL] WIP: CoC V5

> On 13 January 2016 at 03:10, Tom Lane > wrote: >> The "disparaging remarks" part of this could easily be taken to forbid >> technical criticism of any sort, eg "this patch is bad because X,Y, >> and Z", even when X,Y, and Z are perfectly neutral technical points. >> "

Re: [GENERAL] WIP: CoC V5

e don't constitute personal attacks. I don't know. Thanks, Regina From: Regina Obe [mailto:l...@pcorp.us] Sent: Wednesday, January 13, 2016 9:08 AM To: 'Chris Travers' Cc: 'Geoff Winkless' ; 'Psql_General (E-mail)' Subject: RE: [

Re: [GENERAL] plv8 binaries for PostgreSQL 9.5 on Windows

> On 01/11/2016 05:50 PM, Igal @ Lucee.org wrote: > Where can I find binaries for plv8 for PostgreSQL 9.5 for Windows? I've posted PostgreSQL 9.5 Windows binaries for PLV8 http://www.postgresonline.com/journal/archives/360-PLV8-binaries-for-Postgre SQL-9.5-windows-both-32-bit-and-64-bit.html Th

Re: [GENERAL] Let's Do the CoC Right

David et. Al, Sorry for top-posting but it's late, and I'm using lame outlook. I haven't said anything recently, because I decided to open a bag of popcorn and enjoy the Coc debate. If you read my earlier posts, you should know that I am vehemently against anything that sounds like http://contr

Re: [GENERAL] Let's Do the CoC Right

David, Again sorry for cutting thread. I just get the digest. >> I am especially disgusted by the people behind >> http://contributor-covenant.org. They have done nothing but to silence the >> voices of minorities. That's being kind to them. > Interesting. Got a link for context? I Googled,

Re: [GENERAL] Let's Do the CoC Right

Geoff, Are you a woman of color of Black descent? You seem to have the same exact opinions that I do. How can that be? Thanks, Regina -Original Message- From: Geoff Winkless [mailto:pgsqlad...@geoff.dj] Sent: Friday, January 22, 2016 2:06 PM To: Postgres General Cc: David E. Wheel

Re: [GENERAL] Let's Do the CoC Right

This is mostly in response to David's recent comments. I should say David, you are really beginning to make me feel unsafe. By unsafe I mean my mental safety of being able to speak truthfully without fear of being kicked out of a community I love. I do not think we need a Coc and if we do, it's o

Re: [GENERAL] CoC [Final v2]

Josh, Two changes I would like to the Coc as it stands: > * Participants must ensure that their language and actions are free > of personal attacks and disparaging personal remarks. Change the word "must" to "try to". You yourself said some people have called you sexist and against obese peopl

Re: [GENERAL] A motion

I hate to say so folks, but I think Roxanne and Adrian and all those others that said similar things are right. We have created a sustained disruption in a mailing list that is supposed to be about purely technical PostgreSQL topics. It's bad for a Coc to start off by everyone involved in cont