Hi Joshua, Thanks for the posting. That was a good list of areas to cover. Specially about speakers/events/third party plugins etc. How would you sum it up? Would it be right to summed up as anything that could affect the Postgresql as a brand should be protected? This is of course also an opportunity to include many more people within the community. The only problem is that the list is getting to large to implement for *the first drop*. It could end up just as point of discussion. To kick start it. I hope someone will look at the primary issues that concerns the team the most. Including those you and others have mentioned and just get it out of the door. No doubt these will be reviewed and edited or added in due course. How does that sound? Good luck. Farjad Farid -----Original Message----- From: Joshua D. Drake [mailto:jd@xxxxxxxxxxxxxxxxx] Sent: 06 January 2016 17:01 To: Jim Nasby; Melvin Davidson; FarjadFarid(ChkNet) Cc: James Keener; Karsten Hilbert; pgsql-general@xxxxxxxxxxxxxx Subject: Re: Code of Conduct: Is it time? On 01/06/2016 08:13 AM, Jim Nasby wrote: > (BTW, if your concern on enforcement is about control, not only can > people be removed from mailing lists and the like, but there actually > is a Postgres legal entity that could start legal proceedings if it > ever came to it.) As a Director for 2 of the "legal" entities this idea is a rough road. As a volunteer organization we would have a very hard time bringing legal proceedings for a violation of a CoC. Realistically we are talking about a person bringing legal proceedings against another person of whom are contributors to the "PostgreSQL Project". That said, there is no reason this can't be enforced. A hacker who has code committed to the tree has a vested ID interest in that code. It took time, heart, commitment, and tough skin. They may not have been compensated for that time, if they had been compensated they also have skin in the game with whoever compensated them. Now change the first sentence to: A community organizer who spends months organizing a postgresql event has a vested ID interest in that event. A pug leader who spends time every month organizing a postgresql meeting has a vested ID interest in that meeting. An extension writer .... A speaker .... A DBA who fought hard to get PostgreSQL into their DC..... If the big yellow guillotine comes down on their ability to contribute and stains the shirt red. It will matter. Enforcement isn't that hard. It is just a committee who ultimately answers to -core. Sincerely, JD -- Command Prompt, Inc. - http://www.commandprompt.com/ 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@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
