Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90431 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47711 invoked from network); 10 Jan 2016 02:54:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jan 2016 02:54:14 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.44 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 74.125.82.44 mail-wm0-f44.google.com Received: from [74.125.82.44] ([74.125.82.44:33975] helo=mail-wm0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A7/C3-14657-3D7C1965 for ; Sat, 09 Jan 2016 21:54:12 -0500 Received: by mail-wm0-f44.google.com with SMTP id u188so177504684wmu.1 for ; Sat, 09 Jan 2016 18:54:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nlrD5Dxuzacg095Ei//xKjabjWEPIuqNzlbwLmQCZjY=; b=fyWRI2xpWRAc3dbOfvdeLflEWnlAehLfqkbapeGBgE58k61Y5NvkEZ16hKz88zoKxg FORJ2e4Gi1c+TNkZO3m+a/xJqu7YMVeusYJQlwY7wplImsRBIA/XIX4euIGfjbm2PLx1 9qUsQI8UjoR5EI3G7F1hOGn389+8c96MR6S4Skg8nJJWkfQZgcL2WkMaUQfdnJuhouiT J/19n8RknOJ+BjioEhcQ5Z0qH9XgxvMFCl3k1HPntv8lOF8GI6lxcofYCOgdq9Fxb/L8 QT5zmII9nTtbg6uNbrXWAnio5P3h7i1INJbkAZpMld/UEY/ghAMtu3JC0bwkAwGRPQAi kpKg== MIME-Version: 1.0 X-Received: by 10.194.23.163 with SMTP id n3mr5219844wjf.135.1452394448402; Sat, 09 Jan 2016 18:54:08 -0800 (PST) Received: by 10.27.86.202 with HTTP; Sat, 9 Jan 2016 18:54:08 -0800 (PST) In-Reply-To: References: Date: Sun, 10 Jan 2016 03:54:08 +0100 Message-ID: To: Anthony Ferrara Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7b5da6e12bc1810528f1efbe Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: tyra3l@gmail.com (Ferenc Kovacs) --047d7b5da6e12bc1810528f1efbe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Jan 4, 2016 at 10:06 PM, Anthony Ferrara wrote: > Hey all, > > I have created a new RFC for the PHP Project to adopt the Contributor > Covenant as the official Code of Conduct for the project > > https://wiki.php.net/rfc/adopt-code-of-conduct > > Let me know what you think or if there are any concerns > > Thanks > > Anthony > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > just wanted to mention that the jenkins project just adopted a slightly modified version of the Contributor Covenant version 1.3: https://jenkins-ci.org/conduct/#code-of-conduct from what I can tell what seems to be changed that they adjusted the rights to those who already have them: "The Jenkins board has the right and responsibility to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. Plugin and other maintainers also have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct." versus "Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful." Adjusted the definition of their maintainers and contributors, explicitly defined where does the "This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community." apply. They also explicitly stated how to report problems and what is the process handling those reports. They went with the full privacy path, and used their pre-existing government body to handle the reports, which is something we don't have (closest thing we have is the PHP group, but members of that are mostly inactive and doesn't really have extra governing power over others). https://jenkins-ci.org/conduct/ https://jenkins-ci.org/blog/2016/01/07/official-code-of-conduct/ ps: I'm not suggesting anything here, just dropping the info so maybe there is something we can use/learn from it. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --047d7b5da6e12bc1810528f1efbe--