;mailto:pgsql-general@lists.postgresql.org>;
Pg CoC Committee<mailto:c...@postgresql.org>
Subject: Re: Proposed Translations of Updated Code of Conduct Policy
Hi,
Le mar. 19 juil. 2022 à 08:49, Stefan Fercot
mailto:stefan.fer...@protonmail.com>> a écrit :
Hi,
There's a typo in
t; Le samedi 16 juillet 2022 à 7:24 PM, Lucie Šimečková <
> luciesimeck...@outlook.com> a écrit :
>
> Hello all,
>
>
>
> Following the recent update of the English version of the Code of Conduct
> that clarified the term limits of CoC committee members, th
ot; by "(3) mandats consécutifs".
--
Kind Regards,
Stefan FERCOT
EDB: [https://www.enterprisedb.com](https://www.enterprisedb.com/)
--- Original Message ---
Le samedi 16 juillet 2022 à 7:24 PM, Lucie Šimečková
a écrit :
> Hello all,
>
> Following the recent update of
Am Thu, Feb 10, 2022 at 03:24:54PM +0500 schrieb Umair Shahid:
> > What happens if all members of the committee are impeached at once ?
> >
>
> That is one reason to strive for diversity in the CoC Committee - the
> chances of this happening are reduced to near-zero.
It may be near-zero for
Handlungen, die den beruflichen Status einer Person und/oder ihren Status am Arbeitsplatz, bei Kunden oder in der Community untergraben;
* Handlungen, die die Privatsphäre, die körperliche Unversehrtheit, das Wohlbefinden, das Zuhause und/oder die Familie der betroffenen Person bedrohen.
Ein Vorschlag:
> Inklusivität und angemessenes Verhalten
>
> Das PostgreSQL-Projekt steht jedem offen, der Interesse an
> der Arbeit mit PostgreSQL hat, unabhängig von seinem
> Erfahrungsstand mit der Software oder mit Technologie im
> Allgemeinen. Wir fördern die Entwicklung und Beiträge aller
>
The PostgreSQL Community Code of Conduct Committee has received a draft of
the German translation of the Code of Conduct Policy updated August 18,
2020 for review.
The English version of the Policy is at:
https://www.postgresql.org/about/policies/coc/
The translation was contributed
Hi,
not much to add besides thanks to both Alice and Guillaume.
Best regards,
Anthony
On Fri, Sep 17, 2021 at 6:57 AM Stacey Haysler
wrote:
> The PostgreSQL Community Code of Conduct Committee has received a draft of
> the French translation of the Code of Conduct Policy updated Aug
The PostgreSQL Community Code of Conduct Committee has received a draft of
the French translation of the Code of Conduct Policy updated August
18, 2020 for
review.
The English version of the Policy is at:
*https://www.postgresql.org/about/policies/coc/
<https://www.postgresql.org/about/polic
Hello,
The Chinese translation looks good.
regards,
Bo Peng
On Fri, 21 May 2021 09:58:12 -0700
Stacey Haysler wrote:
> The PostgreSQL Community Code of Conduct Committee has received a draft of
> the Chinese translation of the Code of Conduct Policy updated August 18, 2020
> f
On Sat, May 22, 2021 at 12:18 PM Peter J. Holzer wrote:
>
> On 2021-05-21 12:35:49 -0500, Ron wrote:
> > I see the attachments in your first email.
>
> Fascinating. I don't in the normal view but do see them in the MIME
> structure:
>
> I 1 [multipa/alternativ, 7bit, 180K]
On 5/22/21 5:18 AM, Peter J. Holzer wrote:
On 2021-05-21 12:35:49 -0500, Ron wrote:
I see the attachments in your first email.
Fascinating. I don't in the normal view but do see them in the MIME
structure:
I 1 [multipa/alternativ, 7bit, 180K]
I 2 ├─>
On 2021-05-21 12:35:49 -0500, Ron wrote:
> I see the attachments in your first email.
Fascinating. I don't in the normal view but do see them in the MIME
structure:
I 1 [multipa/alternativ, 7bit, 180K]
I 2 ├─> [text/plain, quoted, utf-8, 0.8K]
I 3
mailto:sta...@haysler.sh>>
*Subject: **Proposed Chinese Translation of Community Code of Conduct*
*Date: *May 21, 2021 at 9:58:12 AM PDT
*To: *pgsql-general@lists.postgresql.org
<mailto:pgsql-general@lists.postgresql.org>
The PostgreSQL Community Code of Conduct Committee has rece
Translation of Code of Conduct Policy*
*Date: *March 31, 2021 at 3:25:58 PM PDT
*To: *pgsql-general@lists.postgresql.org
The PostgreSQL Community Code of Conduct Committee has received a draft of
the Italian translation of the Code of Conduct Policy updated August 18,
2020 for review.
The English version
The
PostgreSQL Community Code of Conduct Committee has received a draft
of the Italian translation of the Code of Conduct Policy updated August 18, 2020 for review.
The
English version of the Policy is
at:
https://www.postgresql.org/about/policies/coc/
The
translation was created
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" ("здесь&qu
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
The PostgreSQL Community Code of Conduct Committee has received a revised 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:https://www.postgresql.org/about/policies/coc/The updated translation incorporates
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
Code of Conduct Committee
On Mar 3, 2021, at 11:40 AM, Boris Epstein wrote:
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
llo 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.
>
> Bes
ity 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:
> https://www.postgresql.org/about/policies/coc/
>
> The translation was created b
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
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 r
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:
> https://www.po
r Yegorov
PostgreSQL Code of Conduct - Russian Translation Feb 26 2021 - review.docx
Description: MS-Word 2007 document
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:https://www.postgresql.org/about/policies/coc/The translation was created by:Anastasia
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 f
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 English version of the Policy is at:https://www.postgresql.org/about/policies/coc/The patch was created by:Michael GoldbergThe
The PostgreSQL Community Code of Conduct Committee has received a draft of the
Japanese translation of the Code of Conduct Policy updated August 18, 2020 for
review.
The English version of the Policy is at:
https://www.postgresql.org/about/policies/coc/
The patch was created by:
Tatsuo Ishii
This message is being sent from the Community Code of Conduct Committee, with
the approval of the Core Team.
The PostgreSQL Community Code of Conduct Committee is approaching our first
year anniversary. As part of the Community CoC policy, the Committee membership
is to be refreshed
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
ss 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 to move us in that direction remains
unclear to me. I can't say I'm
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
blem 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 and this is
actually a hard pr
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 https
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/.
>
>
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
e 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 following a long
consultation process, the project’s Co
>>> 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
ng
> 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.
ce 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 objections to
specific wording. So to be honest the b
>
> 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
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.postgresql.org/about/policies/coc/.
>
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
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
t; > additional alternative.
> >
> > " 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 of conduct covers all interaction between
> > community m
pecifically 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 is meant to cover all interaction b
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 C
ommunity 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 Conduct for community
> interaction and participation in the project’s work and the communi
gt; 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 is meant to cov
y. 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 Conduct for communi
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
no problem with a code conduct. After all most people agree
that, even a mundane thing like crossing a road needs rules,
so something as complex as human interactions also needs rules.
That's my two cent worth of contribution.
Best Regards
Farjad Farid
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 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
lue.
"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).**" [emphasis mine]
Hence I think
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
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
disr
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 se
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 mechan
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
unpopular stance, but in no way directs it at the
> postgres user base or on a postgres list. The "attacked"
> person is on this mailing list. IMHO this "attacker" must choose between
> continuing to voice their opinion, and belonging to the Postgres community.
>
The prote
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
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
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 Postgre
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
.
'Civil' and 'civility' are more modest words with more modest goals that are
perhaps easier to capture in language. When it comes to a code of civil
conduct, less is more. If you use more than the words of the ten commandments
you almost certainly have gone too far. I have yet to see a posting
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
own conclusions about my motivations, just as I'll
> make my own conclusions about yours. I'm not going to engage with you
> on either, though.
>
With regard to the concerns about authoritarianism, I have to defend the
Code of Conduct here.
It's not anything of the above. The Post
o 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
disrepute."
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
1 - 100 of 302 matches
Mail list logo
