Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90404 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46591 invoked from network); 9 Jan 2016 03:55:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jan 2016 03:55:10 -0000 Authentication-Results: pb1.pair.com header.from=bishop.bettini@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=bishop.bettini@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender) X-PHP-List-Original-Sender: bishop.bettini@gmail.com X-Host-Fingerprint: 74.125.82.41 mail-wm0-f41.google.com Received: from [74.125.82.41] ([74.125.82.41:38378] helo=mail-wm0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E7/AF-55593-B9480965 for ; Fri, 08 Jan 2016 22:55:08 -0500 Received: by mail-wm0-f41.google.com with SMTP id b14so197443294wmb.1 for ; Fri, 08 Jan 2016 19:55:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=cPHymqH9zcu1H+2Of3bfO90yjp88LEMlucBGsJwuYFM=; b=lGE0JMD0YCU/ZE20/uudHfuIq2JxCgE7OKI1C9kDBWFS/hnRaM4eO7R195XvaWXnw9 NGeIpc8qVYCHMvdymCQgSThfRSPsCW9yEHnM3PnTzqXyWcSx9CqUS+1E5YU4Ld5peTrX 1UUttC6slCgOuDFZjYb4DH2sHMs81Xx+agrnNiQQskngMziRBnzSzlwCzpHTVB8cGuzJ rtHwdzv53MbwI1T60m1dagzfhjC/YmzgY2Jei2nBsVaYAtYCAYpi7dDIxCzWrUgB1ZTV AYrn1NfWUg2sjS67J2JwNM/bS8jdQceWeVd56Fk4XoxOiQAbxR1cuaWPO7r8iwmOsJ2v yljw== X-Received: by 10.194.209.129 with SMTP id mm1mr87271709wjc.47.1452311704826; Fri, 08 Jan 2016 19:55:04 -0800 (PST) MIME-Version: 1.0 Reply-To: bishop@php.net Sender: bishop.bettini@gmail.com Received: by 10.194.45.230 with HTTP; Fri, 8 Jan 2016 19:54:35 -0800 (PST) In-Reply-To: References: Date: Fri, 8 Jan 2016 22:54:35 -0500 X-Google-Sender-Auth: B-ukpKYAEzRisfEYnBHYmtZLQYo Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary=047d7b3a840a44f9ef0528deab53 Subject: Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct From: bishop@php.net (Bishop Bettini) --047d7b3a840a44f9ef0528deab53 Content-Type: text/plain; charset=UTF-8 Hi Anthony, Presented for your consideration... PHP Contributor Etiquette : 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. Cheers, bishop --047d7b3a840a44f9ef0528deab53--