Thank you, Valeria. I have forwarded your comments to Anastasia and Alexander.
Regards,
Stacey
Stacey Haysler
Chair
PostgreSQL Community Code of Conduct Committee
On Mar 11, 2021, at 2:03 AM, Valeria Kaplan wrote:
Looks good.
1. Just to note that the word "here" ("здесь") on page 2 isn't a
Looks good.
1. Just to note that the word "here" ("здесь") on page 2 isn't a hyperlink
(it is supposed to link to the Code of Conduct page).
2. Spelling of PostgresQL > PostgreSQL on page 7 should be corrected
Thank you for all your work.
Valeria
On Thu, Mar 11, 2021 at 3:49 AM Stacey Haysler
All of the comments are forwarded to the original translation team for review.
We really appreciate how many people are offering ideas for this translation!
Regards,
Stacey
Stacey Haysler
Chair
PostgreSQL Community Code of Conduct Committee
On Mar 3, 2021, at 2:09 PM, Valeria Kaplan wrote:
Hi, Boris - A redline or similar mark up in a standard document format (.odt,
.pages, .doc, etc.) is the most common method. As long as it is readable by a
human and the edits are easy to see, we can probably work with it. Thank you!
Regards,
Stacey
Stacey Haysler
Chair
PostgreSQL Community
Hi Alexander,
Attached. Overall I agree with most of your comments.
Perhaps, whoever did the initial translation could take a look and finalise
it. It's quite hard to review it in this format with so many comments.
Thanks,
Valeria
On Wed, Mar 3, 2021 at 7:22 PM Alexander Lakhin wrote:
> Hello
Hello Stacey,
I took a quick look and it looks OK overall. I could go over it in more
detail - but before I do, is there a code control procedure I need to
follow to offer edits, etc?
Thanks.
Regards,
Boris.
On Fri, Feb 26, 2021 at 7:51 PM Stacey Haysler wrote:
> The PostgreSQL Community
Hello Valeria,
03.03.2021 20:23, Valeria Kaplan wrote:
>
> attached are my comments (I used Alexander's file for ease of review).
>
Thanks for your comments!
Please look at my responses.
I hope we'll finalize the translation soon.
Best regards,
Alexander
PostgreSQL Code of Conduct - Russian
Hi All,
attached are my comments (I used Alexander's file for ease of review).
thank you,
Valeria
On Mon, Mar 1, 2021 at 2:26 PM Alexander Lakhin wrote:
> Hello,
>
> 27.02.2021 03:51, Stacey Haysler wrote:
>
> The PostgreSQL Community Code of Conduct Committee has received a draft of
> the
Hello,
27.02.2021 03:51, Stacey Haysler wrote:
> The PostgreSQL Community Code of Conduct Committee has received a
> draft of the Russian translation of the Code of Conduct Policy updated
> August 18, 2020 for review.
>
> The English version of the Policy is at:
>
сб, 27 февр. 2021 г. в 01:51, Stacey Haysler :
> If you have any comments or suggestions for the translation, please bring
> them to our attention no later than 5:00 PM PST on Friday, March 5, 2021.
>
Greetings.
I looked through the text and made some comments.
--
Victor Yegorov
Had a read through, no comments.
Thank you, Michael and Emil!
On Thu, Feb 25, 2021 at 6:54 PM Stacey Haysler wrote:
> The PostgreSQL Community Code of Conduct Committee has received a draft of
> the Hebrew translation of the Code of Conduct Policy updated August 18,
> 2020 for review.
>
> The
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
On Fri, Sep 14, 2018 at 4:17 PM, Tom Lane wrote:
> There's been quite a lot of input, from quite a lot of people, dating
> back at least as far as a well-attended session at PGCon 2016. I find
> it quite upsetting to hear accusations that core is imposing this out
> of nowhere. From my
On 2018-09-20 16:13, Bruce Momjian wrote:
> On Thu, Sep 20, 2018 at 05:20:55PM +0200, Chris Travers wrote:
>> I suspect most of us could probably get behind the groups listed in the
>> antidiscrimination section of the European Charter of Fundamental Rights at
>> least as a compromise.
>>
>>
On Thu, Sep 20, 2018 at 05:20:55PM +0200, Chris Travers wrote:
> I suspect most of us could probably get behind the groups listed in the
> antidiscrimination section of the European Charter of Fundamental Rights at
> least as a compromise.
>
> Quoting the English version:
>
> "Any
On Wed, Sep 19, 2018 at 11:31 PM Bruce Momjian wrote:
> On Wed, Sep 19, 2018 at 11:24:29AM +1000, Julian Paul wrote:
> > It's overly long and convoluted.
> >
> > "inclusivity" Is a ideologue buzzword of particular individuals that
> offer
> > very little value apart from excessive policing of
On Thu, Sep 20, 2018 at 5:11 AM Craig Ringer wrote:
> 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
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
On Wed, Sep 19, 2018 at 11:24:29AM +1000, Julian Paul wrote:
> It's overly long and convoluted.
>
> "inclusivity" Is a ideologue buzzword of particular individuals that offer
> very little value apart from excessive policing of speech and behaviour
> assumed to be a problem where none exist.
>
>
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
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/.
>
> Please take time
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
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
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
On Wed, 19 Sep 2018 16:30:56 +0200
ERR ORR wrote:
> A CoC will inevitably lead to the project taken over by leftists,
Here we go again.
SteveT
Steve Litt
September 2018 featured book: Quit Joblessness: Start Your Own Business
http://www.troubleshooters.com/startbiz
Tatsuo Ishii writes:
> Now that CoC is out,
> https://www.postgresql.org/about/policies/coc/
> I would like to start the translation work. Can somebody suggest me
> how I can proceed?
Sure, translate away. Probably the -www list is the place to discuss
questions like where it would appear on
Keep pg open and free. This smells of PC police. This community can police
itself
Sent from my mobile device. Please pardon my brevity and typos. I am not
responsible for changes made by this device’s autocorrect feature.
Fred Pratt
AmerisourceBergen
Manager – IT Infrastructure
Micro
>>> Do we want official translations of this? We allow local communities
>>> do their own manual translations. However CoC is so important, I feel
>>> like we need more for Coc. Good thing with CoC is, it is expected that
>>> it would be stable (at least I hope so) and translation works when
>>>
On 18/09/18 20:27, 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/.
Please take time to read and understand
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
On Tue, Sep 18, 2018 at 8:35 PM Tom Lane wrote:
> Stephen Frost writes:
> > I would ask that you, and anyone else who has a suggestion for how to
> > improve or revise the CoC, submit your ideas to the committee by
> > email'ing c...@postgresql.org.
> > As was discussed previously, the current
Stephen Frost writes:
> I would ask that you, and anyone else who has a suggestion for how to
> improve or revise the CoC, submit your ideas to the committee by
> email'ing c...@postgresql.org.
> As was discussed previously, the current CoC isn't written in stone and
> it will be changed and
Greetings,
* Chris Travers (chris.trav...@gmail.com) wrote:
> I said I would stand aside my objections after the last point I mentioned
> them but I did not feel that my particular objection and concern with
> regard to one specific sentence added got much of a hearing. This being
> said, it is
On Tue, Sep 18, 2018 at 4:35 PM Tomas Vondra
wrote:
> 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
> >
>
> 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
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
> 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 and concerns were
taken into
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
On Mon, Sep 17, 2018 at 6:08 PM Steve Litt
wrote:
> On Mon, 17 Sep 2018 17:39:20 +0200
> Chris Travers wrote:
>
>
> > Exactly. And actually the first sentence is not new. The second one
> > is a real problem though. I am going to try one last time at an
> > additional alternative.
> >
> > "
> On Sep 17, 2018, at 4:57 PM, Steve Litt wrote:
>
> On Mon, 17 Sep 2018 08:27:48 -0700
> "Joshua D. Drake" wrote:
>
>>
>> At this point it is important to accept that the CoC is happening. We
>> aren't going to stop that. The goal now is to insure a CoC that is
>> equitable for all
On Mon, 17 Sep 2018 17:39:20 +0200
Chris Travers wrote:
> Exactly. And actually the first sentence is not new. The second one
> is a real problem though. I am going to try one last time at an
> additional alternative.
>
> " To that end, we have established this Code of Conduct for community
On Mon, 17 Sep 2018 08:27:48 -0700
"Joshua D. Drake" wrote:
> On 09/17/2018 08:11 AM, Dmitri Maziuk wrote:
> > 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
On Mon, Sep 17, 2018 at 5:28 PM Joshua D. Drake
wrote:
> On 09/17/2018 08:11 AM, Dmitri Maziuk wrote:
>
> 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
On 09/17/2018 08:11 AM, Dmitri Maziuk wrote:
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
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
On Sun, 16 Sep 2018 16:00:31 +1200
Mark Kirkwood wrote:
> a SJW agenda.
> the angry militant left.
Some people just can't stop themselves.
Which is a big reason for CoCs.
SteveT
Steve Litt
September 2018 featured book: Quit Joblessness: Start Your Own Business
Dear All,
If we allow friendship and fellowship to flourish everyone benefits. That
doesn't mean we should drop our standards or quality.
It is worth remembering that all human beings are social animals(basic logic)
so even the most logical person could get offended and turn off from
On Sat, 15 Sep 2018 16:12:36 -0700
Adrian Klaver wrote:
> https://marshmallow.readthedocs.io/en/dev/code_of_conduct.html
Personally I don't give a toss about politolosophy, I think idiocy, no matter
how well-meaning, is still idiocy and is probably contaguious via
"normalization of idiocy".
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
On Sat, Sep 15, 2018 at 8:11 PM Tom Lane wrote:
> Martin Mueller writes:
> > Which makes me say again "Where is the problem that needs solving?"
>
> We've re-litigated that point in each burst of CoC discussion for the
> last two-plus years, I think. But, one more time:
>
> * So far as the
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
On 9/14/18 11:13 AM, Robert Haas wrote:
On Fri, Sep 14, 2018 at 11:10 AM, Dave Page wrote:
That wording has been in the published draft for 18 months, and noone
objected to it that I'm aware of. There will always be people who don't like
some of the wording, much as there are often people who
On 9/14/18 11:21 AM, Peter Geoghegan wrote:
On Fri, Sep 14, 2018 at 11:06 AM, Dimitri Maziuk wrote:
Personally I would like that. Others might prefer an invitation to
unsubscribe or forever hold their peace, I could live with that too, but
I believe explicit opt-ins are preferable to opt-outs.
Martin Mueller writes:
> Which makes me say again "Where is the problem that needs solving?"
We've re-litigated that point in each burst of CoC discussion for the
last two-plus years, I think. But, one more time:
* So far as the mailing lists alone are concerned, we likely don't really
need a
That is quite true: the very high quotient of helpful prose and very low
quotient of inappropriate language is striking--much like the TEI list of which
I long have been a member, and unlike the MySQL list, which has a non-trivial
(though not serious) boorish component.
Which makes me say
On Sat, Sep 15, 2018 at 12:11:37PM -0400, Melvin Davidson wrote:
> How about we just simplify the code of conduct to the following:
> Any member in the various PostgreSQL lists is expected to maintain
> respect to others and not use foul language. A variation from
> the previous sentence shall be
On Sat, Sep 15, 2018 at 04:24:38PM +, Martin Mueller wrote:
> What counts as foul language has changed a great deal in the last two
> decades.
> You could always tie it to what is printable in the New York Times, but that
> too is changing. I could live with something like “Be considerate,
Date: Saturday, September 15, 2018 at 11:12 AM
To: Tom Lane
Cc: Bruce Momjian , Chris Travers ,
James Keener , Steve Litt ,
"pgsql-generallists.postgresql.org"
Subject: Re: Code of Conduct plan
How about we just simplify the code of conduct to the following:
Any member in the various
How about we just simplify the code of conduct to the following:
Any member in the various PostgreSQL lists is expected to maintain
respect to others and not use foul language. A variation from
the previous sentence shall be considered a violation of the CoC.
On Sat, Sep 15, 2018 at 11:51 AM Tom
Bruce Momjian writes:
> There is a risk that if we adopt a CoC, and nothing happens, and the
> committee does nothing, that they will feel like a failure, and get
> involved when it was best they did nothing. I think the CoC tries to
> address that, but nothing is perfect.
Yeah, a busybody CoC
On Sat, Sep 15, 2018 at 11:32:06AM -0400, Bruce Momjian wrote:
> There is a risk that if we adopt a CoC, and nothing happens, and the
> committee does nothing, that they will feel like a failure, and get
> involved when it was best they did nothing. I think the CoC tries to
> address that, but
On Sat, Sep 15, 2018 at 08:44:10AM +0200, Chris Travers wrote:
> The protection there is a culturally diverse code of conduct committee who can
> then understand the relationship between politics and culture. And just to
> note, you can't solve problems of abuse by adopting mechanistically
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 on a vaguely-defined group
On Sat, Sep 15, 2018 at 4:47 AM James Keener wrote:
>
>
> The preceding's pretty simple. An attacker goes after an individual,
>> presumably without provocation and/or asymetrically. The attacked
>> person is on this mailing list. IMHO this attacker must choose between
>> continuing his attacks,
The preceding's pretty simple. An attacker goes after an individual,
> presumably without provocation and/or asymetrically. The attacked
> person is on this mailing list. IMHO this attacker must choose between
> continuing his attacks, and belonging to the Postgres community.
>
> What's tougher is
On Fri, 14 Sep 2018 07:19:59 -0700
"Joshua D. Drake" wrote:
> 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 on
> actions outside of the
On Fri, 14 Sep 2018 10:10:38 -0400
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
On Fri, 14 Sep 2018 13:18:12 +
Martin Mueller wrote:
> 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.
No, it's not. Talk to anyone
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 PostgreSQL but also their
On 09/14/2018 01:17 PM, Chris Travers wrote:
> And frankly I am probably being paranoid here though I find paranoia is a
> good thing when it comes to care of databases and computer systems. But I
> do worry about the interactions between the PostgreSQL community and the
> larger world with
On 9/14/18, 12:50 PM, "Joshua D. Drake" wrote:
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
On Fri, Sep 14, 2018 at 11:06 AM, Dimitri Maziuk wrote:
> Personally I would like that. Others might prefer an invitation to
> unsubscribe or forever hold their peace, I could live with that too, but
> I believe explicit opt-ins are preferable to opt-outs.
I think that it's a legitimate position
On Fri, Sep 14, 2018 at 7:47 PM Peter Geoghegan wrote:
> On Fri, Sep 14, 2018 at 10:31 AM, Dimitri Maziuk
> wrote:
> > So let me get this straight: you want to have a "sanctioned" way to deny
> > people access to postgresql community support channel?
>
> Yes.
>
> > "Because
> > somebody who may
On Fri, Sep 14, 2018 at 11:10 AM, Dave Page wrote:
> That wording has been in the published draft for 18 months, and noone
> objected to it that I'm aware of. There will always be people who don't like
> some of the wording, much as there are often people who disagree with the
> way a patch to
Greetings,
* Dimitri Maziuk (dmaz...@bmrb.wisc.edu) wrote:
> On 09/14/2018 12:46 PM, Peter Geoghegan wrote:
> > On Fri, Sep 14, 2018 at 10:31 AM, Dimitri Maziuk
> > wrote:
> >> So let me get this straight: you want to have a "sanctioned" way to deny
> >> people access to postgresql community
On 09/14/2018 12:46 PM, Peter Geoghegan wrote:
> On Fri, Sep 14, 2018 at 10:31 AM, Dimitri Maziuk
> wrote:
>> So let me get this straight: you want to have a "sanctioned" way to deny
>> people access to postgresql community support channel?
>
> Yes.
A question to TPTBs, then: once The Great
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
On Fri, Sep 14, 2018 at 10:31 AM, Dimitri Maziuk wrote:
> So let me get this straight: you want to have a "sanctioned" way to deny
> people access to postgresql community support channel?
Yes.
> "Because
> somebody who may or may not be the same person, allegedly said something
> somewhere that
While agreeing that there are good arguments that we are a "community" in a
prescriptive sense, I don't think the discussion about whether we
constitute a community is relevant. For at least 25 years "community" has
been applied to virtually any group of people, much to the chagrin of those
such
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
On 09/14/2018 12:14 PM, Peter Geoghegan wrote:
> No CoC can possibly provide for every conceivable situation. Somebody
> has to interpret the rules, and it has to be possible to impose
> sanctions when the CoC is violated -- otherwise, what's the point?
> There are several checks and balances in
On Fri, Sep 14, 2018 at 7:19 AM, Joshua D. Drake wrote:
> Sure and that is unfortunate but isn't it up to the individual to deal with
> it through appropriate channels for whatever platform they are on? All of
> these platforms are:
>
> 1. Voluntary to use
> 2. Have their own Terms of Use and
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
On 09/14/2018 09:42 AM, Dave Page wrote:
> There are some fuzzy edges I guess (e.g. Slack), but in my mind it's always
> been anyone who participates in any of the projects communications channels.
Then you Sir are an evil ter'rist member of isis because your spoken
words are carried by the same
Greetings,
* James Keener (j...@jimkeener.com) wrote:
> > > I fail to see how that makes everyone here part of a community anymore
> > than
> > > I'm part of the "community" of regulars at a bar I walk into for the
> > first
> > > time.
> >
> > Does the bartender get to kick you out if you get
On Fri, Sep 14, 2018 at 3:37 PM, Joshua D. Drake
wrote:
> On 09/14/2018 07:14 AM, Dave Page wrote:
>
>
>
> On Fri, Sep 14, 2018 at 3:08 PM, Joshua D. Drake
> wrote:
>
>> On 09/14/2018 01:31 AM, Chris Travers wrote:
>>
>>
>> I apologize for the glacial slowness with which this has all been
On Fri, Sep 14, 2018 at 7:16 AM, Tom Lane wrote:
> [ Let's try to trim this discussion to just -general, please ]
>
> Robert Eckhardt writes:
> > On Fri, Sep 14, 2018 at 9:41 AM, Adrian Klaver
> > wrote:
> >> On 9/14/18 1:31 AM, Chris Travers wrote:
> >>> I really have to object to this
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
> 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.
> .
> 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
On Fri, Sep 14, 2018 at 4:51 PM Dave Page wrote:
>
>
> On Fri, Sep 14, 2018 at 3:43 PM, Joshua D. Drake
> wrote:
>
>> 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
Greetings,
(trimmed to -general, tho I don't know if it'll really help)
* James Keener (j...@jimkeener.com) wrote:
> > 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
On Fri, Sep 14, 2018 at 4:16 PM Tom Lane wrote:
> [ Let's try to trim this discussion to just -general, please ]
>
> Robert Eckhardt writes:
> > On Fri, Sep 14, 2018 at 9:41 AM, Adrian Klaver
> > wrote:
> >> On 9/14/18 1:31 AM, Chris Travers wrote:
> >>> I really have to object to this
On Fri, Sep 14, 2018 at 4:14 PM Dave Page wrote:
>
>
> On Fri, Sep 14, 2018 at 3:08 PM, Joshua D. Drake
> wrote:
>
>> On 09/14/2018 01:31 AM, Chris Travers wrote:
>>
>>
>> I apologize for the glacial slowness with which this has all been moving.
>>> The core team has now agreed to some
>
> 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
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." basically says?
>>
>
> No? What's the
On 09/14/2018 07:51 AM, Dave Page wrote:
If that business is publicly bringing the project into disrepute, or
harassing other community members and they approach us about it, then
it becomes our business.
If it's unrelated to PostgreSQL, then it's your personal business
and not
> > I fail to see how that makes everyone here part of a community anymore
> than
> > I'm part of the "community" of regulars at a bar I walk into for the
> first
> > time.
>
> Does the bartender get to kick you out if you get into a fight? Or if
> you're rude or inappropriate towards the
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
On 9/14/18 7:52 AM, James Keener wrote:
I fail to see how that makes everyone here part of a community anymore
than I'm part of the "community" of regulars at a bar I walk into for
the first time.
As I said, the rules can and should apply within the list, but
applying them outside the list
1 - 100 of 275 matches
Mail list logo
