Elephpant Etiquette (v1.1)

We, the international community of PHP contributors, affirm our need to maintain cordial online collaborative spaces and do adopt this etiquette as our guide in doing so.





(I) Collaborative Spaces

Our online collaborative spaces are the nerve center of PHP evolution. We all share these spaces and are all responsible for keeping them welcoming, friendly, and focused. We define these spaces as:

The PHP mailing lists

The PHP IRC channels

The PHP Twitter feed

The PHP Facebook page

The PHP Github accounts and the PHP SVN documentation repositories

The PHP.net documentation, including comments

The PHP bugs and feature request database Anyone who contributes to any of these channels is a de facto contributor.

(II) Contributors' rights and responsibilities

As a PHP contributor, you have the right to:

Converse in our collaborative spaces without fear of harassment

Present your own thoughts and ideas

Submit changes to PHP, its extensions, and documentation

Walk away of your own volition

Become a community moderator through the vote of other contributors

As a contributor, you also represent PHP and are responsible for:

Your contributions:

Adhere to submission guidelines



Timely respond to inquiries about your submissions



Remember that constructive criticism isn't personal

Your words:

Be understanding



Be polite



Be concise



Speak honestly with constructive language



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 We encourage contributors to apply this etiquette outside our collaborative spaces.



(III) Community moderation

Our collaborative spaces are moderated. 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 contributors. They listen without judging. They keep specific details in confidence.



Community moderators exist to resolve conflicts in the most harmonious possible manner. They enjoin contributors to corrective behaviors. They can recommend censure for repeated or egregious missteps of etiquette.



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



To add or remove a moderator requires a 4/5 majority vote by the deliberative body of electors holding voting karma. Contributors without voting karma may lobby karma holders, but there is no means for direct voting. All votes for community moderators are anonymous.



To become a moderator, email moderators@php.net. In your own words, describe why you want to moderate (this your purpose statement). Include a relevant bio illustrating your diplomatic prowess. Existing community moderators will help you polish your application into an RFC and shepherd it through the voting process.



Community moderators are themselves contributors, but are expected to model the etiquette without fail. Any contributor may petition to remove a moderator. To remove a moderator, email moderators@php.net with your petition. Existing moderators will help you shape your petition into an RFC and shepherd it through the voting process.



Moderators are facilitators and shepherds. Moderators do not cull applications or petitions.

Reactions:

Yes, I do believe PHP internals needs a guide to etiquette. But, no, not a code of conduct. Internals is a decades (plural) old cathedral-like meritocracy . There is no benevolent dictator. There is no functional oversight group. No rigorous process (like Go has ) will work in the internals ecosystem.Anthony's draft sets the stage, but I don't think it'll draw the crowds. For that, we need a moderate approach that emphasizes the definition of acceptable behavior while limiting the authoritative scope. Here's my second attempt at a custom-fit "code of conduct" roughly based on the one from Go