Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107118
To: Stanislav Malyshev <smalyshev@gmail.com>, Joe Watkins <krakjoe@php.net>,
 PHP internals <internals@lists.php.net>, rasmus@php.net
References: <CAOwTYAu5vCGMw4Dp0v90fGD9OGm6X0dc42iJV35bk1Df_yr_2w@mail.gmail.com>
 <3cb49f31-34c1-3c81-3bc4-5cf3b6f52d99@gmail.com>
Message-ID: <81ddcae0-51e4-62b4-5990-38d796d666e2@gmx.de>
Date: Sun, 15 Sep 2019 22:05:19 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <3cb49f31-34c1-3c81-3bc4-5cf3b6f52d99@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Defining the PHP Group
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 15.09.2019 at 21:33, Stanislav Malyshev wrote:

>> Do we need to vote on changing the introduction (I'm happy to start an =
rfc
>> for this, if necessary) ?
>
> I don't think RFCs were meant to essentially remake all project
> governance structure. They were meant for solving technical questions,
> not governance model.

Then we should undo all changes (as far as possible) caused by the RFCs
listed in the Process and Policy section[1], probably starting with the
Voting (aka. RFC) process RFC itself, which by the way, states as
introduction since its very first version from 2011 (emphasis mine):

| This document describes the procedure to propose an *idea* for
| adoption by the PHP community and decide if the community accepts or
| rejects the idea.

Thanks,
Christoph

[1] <https://wiki.php.net/rfc#process_and_policy>