Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107098 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 63773 invoked from network); 15 Sep 2019 08:11:51 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 15 Sep 2019 08:11:51 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 8624C2D02E4 for ; Sat, 14 Sep 2019 22:48:25 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_40,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPOOFED_FREEMAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No Received: from mail-vs1-f49.google.com (mail-vs1-f49.google.com [209.85.217.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Sat, 14 Sep 2019 22:48:25 -0700 (PDT) Received: by mail-vs1-f49.google.com with SMTP id v10so17993072vsc.7 for ; Sat, 14 Sep 2019 22:48:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=e5YP7RCvZlUAI/pyCvnNmHGsCGzXDHwG/AibXlk4l2Q=; b=oW8ICkCzpG/JHMV2t7NEl4+p95qf/UX3cMToBlJVoWWQrVN7ifqpj8360YUnrM5j6x INdXWU3ze7cJpOuWgpcqU1Xlwbo/9Sdp5lGAE28AcCauc4F35vzVuBUdBMB6TFzXJ8ma bqY7HLZsQ5JiG4ib0vGFm6T6C2UTFu5UqsDdhSsMGZwzCWRbPo8Z3aGvBCOigCXxcdux 3qr6UjLXfBUVfmq9MXmEzFMWLTd1CPu4oOnXbjDqoxKtTog5nr6f96xrdQdwUa29p2gt SMnAP9IDoY2+t4mDEMvyUwfM+pM1171mnrIf7MhUApyaFaYq/B/zDQx1oFS7hO8OD60l WF3w== X-Gm-Message-State: APjAAAW1S/d358Il7AZWOWMlvgySOpXMGozB7sgfvm67EXLdNJao7t78 GwL0ZNdqZ7PdadCR2o7oFqeEHOJEvgc= X-Google-Smtp-Source: APXvYqz4/LF/EamyeroCpDnsf+9VxGvjq2A8OdU83APBk5J2oIy/xg7PMjR6KT6cScYo9GPxjefUJA== X-Received: by 2002:a67:2981:: with SMTP id p123mr19042030vsp.121.1568526504464; Sat, 14 Sep 2019 22:48:24 -0700 (PDT) Received: from mail-vs1-f54.google.com (mail-vs1-f54.google.com. [209.85.217.54]) by smtp.gmail.com with ESMTPSA id y15sm7139853vkb.42.2019.09.14.22.48.24 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 14 Sep 2019 22:48:24 -0700 (PDT) Received: by mail-vs1-f54.google.com with SMTP id z14so21224641vsz.13 for ; Sat, 14 Sep 2019 22:48:24 -0700 (PDT) X-Received: by 2002:a67:e985:: with SMTP id b5mr1394220vso.42.1568526503930; Sat, 14 Sep 2019 22:48:23 -0700 (PDT) MIME-Version: 1.0 Date: Sun, 15 Sep 2019 07:48:12 +0200 X-Gmail-Original-Message-ID: Message-ID: To: PHP internals , rasmus@php.net Content-Type: multipart/alternative; boundary="0000000000001671d60592910912" X-Envelope-From: Subject: Defining the PHP Group From: krakjoe@php.net (Joe Watkins) --0000000000001671d60592910912 Content-Type: text/plain; charset="UTF-8" Morning internals, There is confusion among the community, and contained in the documented history of PHP on the wider internet. The Wikipedia states that PHP is developed by the PHP Group, in saying this it is (must be) referring to internals as a whole, but our own documentation names members of the group - who aren't even around mostly. I think we need to clarify what exactly is the purpose of the PHP Group today, does anyone want to attempt to do that ? Whatever it's purpose, if it has one, we need to make clear at this time that there are no vetos: As Rasmus clarified, PHP is driven by the people who write PHP: No member of any group or company, historical or otherwise, has any veto powers, they cannot, and they must not behave as if they do. I would like to update the introduction to the Voting RFC: The development of PHP is community driven by the RFC process described in this document. Anyone may initiate an RFC for any subject. At the end of the RFC process a vote is held among PHP developers to determine if the proposal is to be accepted. Should a proposal be accepted, the developers of PHP are committed to making the change. In some circumstances, merging an implementation into the source code of PHP may be delayed because of shortcomings in that implementation. In these cases, resolution of these shortcomings is the responsibility of the proposer. Should a proposal be accepted without an implementation, it is the responsibility of the proposer to provide one. Does anyone object to any of those words ? Do we need to vote on changing the introduction (I'm happy to start an rfc for this, if necessary) ? Cheers Joe --0000000000001671d60592910912--