PHP Contributor Etiquette

I was the first to publically +1 the Code of Conduct RFC. I'd love to see a policy that fosters diversity and inclusion, because damn the PHP crowd is startlingly similar. But, after hearing the arguments, I can't endorse the code as written. It's too focused on process and punishment. I believe we need to look at this from a definition of rights and responsibilities. This is my attempt.

PHP Contributor Etiquette

PHP exists because programmers, admins, and writers from all over the world volunteer their time and talent. Through mostly digital media, these volunteers collaborate to improve PHP. It's a social system revolving around intensely technical details. Like any social setting, there is a need to define the code of ethical behavior and conventions of communication. Our etiquette aims to foster an environment where all voices are welcomed and heard:

(I) You are a contributor to, and representative of, PHP if you:

• Join any of the PHP communication channels (mailing lists, IRC channels, Twitter feeds, or Facebook group) and start or reply to a conversation.
• Post comments on php.net or bug/feature requests on bugs.php.net.
• Submit comments, issues, or patches to PHP or its extensions through Github.
• Attend any conference authorized to use the PHP logo.

(II) As a contributor to PHP, you have the right to:

• Participate in conversations without fear of harassment
• Present your thoughts and ideas
• Submit changes to PHP, its extensions, and documentation
• Walk away (both in person and digitally)
• Become a community moderator through the vote of other collaborators

(III) As a representative of PHP, you are responsible for:

• Your contributions:
• Adhere to submission guidelines
• Timely respond to inquiries about your submissions
• Your words:
• Be understanding: everyone's perspective is different
• Be polite
• Be concise
• Discuss the position, not the person
• Your behavior:
• Actively listen to those who are speaking
• Affirm what you hear
• Remain calm (strive for equanimity)
• Keep your voice down (NO CAPS)
• Stay out of other's personal space
• Heed the advice of community moderators

Community moderators are stewards of the community's interest in collaboration. They proactively encourage collaborators to adhere to our etiquette. They provide advice and guidance to individuals and mediate dispute between collaborators. They listen without judging. They keep specific details in confidence.

To reach a moderator, email moderators@php.net.

To become a moderator, email moderators@php.net. In your own words, describe why you want to moderate (this your purpose statement). Include a bio. Existing community moderators will help you shape and polish your purpose statement and bio, then present your application for an anonymous vote. With a 4/5 confidence, you will become a community moderator. You may request a copy of the tally, with specific email addresses scrubbed.