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. Thanks, Regina From: Chris Travers [mailto:chris.trav...@gmail.com] Sent: Wednesday, January 13, 2016 2:47 AM To: Joshua D. Drake <j...@commandprompt.com> Cc: Tom Lane <t...@sss.pgh.pa.us>; Brian Dunavant <br...@omniti.com>; Psql_General (E-mail) <pgsql-general@postgresql.org> Subject: Re: WIP: CoC V5 Still trying the Danish "Make Love not Codes" approach (Love being the plural of the Danish Lov meaning law). 1. The CoC is to provide community guidelines for creating and enforcing a safe, respectful, productive, and collaborative place for any person who is willing to contribute in a safe, respectful, productive and collaborative way. This CoC is only about interaction via community channels or relating to community commons. Your personal lives outside the PostgreSQL community are your own. 2. Please be respectful of others. Understand that the community is about collaboration. We are here to build and further a software project, so let's work together. 3. Please try to assume that perceived slights are the result of genuine miscommunication or different perspective not personal attacks. Assume others are being reasonable. 4. Please respect the common work and the need for high quality of code. Understand that the review process is an opportunity for discussion and improvement. Work to further the community and the software, and assume that others are doing the same. 5. The CoC committee, those they designate may take action as needed to facilitate or, as necessary, take action to enforce the community principles and conduct embodied in this CoC. For affiliated projects, the maintainers of the project or those they designate may fill the same role instead. ===== I am going to reiterate my view that a rules approach is not going to really prevent problems and those who want to harass others can often use codes of conduct as weapons to do so. I would rather see something as general as possible.emphasizing what we want rather than what we want to avoid. On Tue, Jan 12, 2016 at 10:37 PM, Joshua D. Drake <j...@commandprompt.com <mailto:j...@commandprompt.com> > wrote: tl;dr; * Moved #2 to #3 and #3 to #2 * Added wording for assuming positive intent to #2 PostgreSQL Global Development Group (PGDG) Code of Conduct (CoC): 1. The CoC is to provide community guidelines for creating and enforcing a safe, respectful, productive, and collaborative place for any person who is willing to contribute in a safe, respectful, productive and collaborative way. 2. A safe, respectful, productive and collaborative environment is free of personal attacks and disparaging remarks of any kind. 3. The CoC is not about being offended. One should always assume good intentions. As with any diverse community, anyone can get offended at anything. 4. Any sustained disruption of the collaborative space (mailing lists, IRC etc..) or other PostgreSQL events shall be construed as a violation of the CoC and appropriate action will be taken by the CoC committee. 5. The CoC is only about interaction with the PostgreSQL community. Your private and public lives outside of the PostgreSQL community are your own. -- Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564 <tel:503-667-4564> PostgreSQL Centered full stack support, consulting and development. Announcing "I'm offended" is basically telling the world you can't control your own emotions, so everyone else should do it for you. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org <mailto:pgsql-general@postgresql.org> ) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Best Wishes, Chris Travers Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in. http://www.efficito.com/learn_more
