Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107771
Return-Path: <derick@php.net>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 20464 invoked from network); 6 Nov 2019 13:45:42 -0000
Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12)
  by pb1.pair.com with SMTP; 6 Nov 2019 13:45:42 -0000
Received: from php-smtp3.php.net (localhost [127.0.0.1])
	by php-smtp3.php.net (Postfix) with ESMTP id D87982D2026
	for <internals@lists.php.net>; Wed,  6 Nov 2019 03:35:20 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,
	URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS30827 82.113.144.0/21
X-Spam-Virus: Error (Cannot connect to unix socket
	'/var/run/clamav/clamd.ctl': connect: Connection refused)
Received: from xdebug.org (xdebug.org [82.113.146.227])
	by php-smtp3.php.net (Postfix) with ESMTP
	for <internals@lists.php.net>; Wed,  6 Nov 2019 03:35:20 -0800 (PST)
Received: from localhost (localhost [IPv6:::1])
	by xdebug.org (Postfix) with ESMTPS id 04BEA10CA53;
	Wed,  6 Nov 2019 11:35:18 +0000 (GMT)
Date: Wed, 6 Nov 2019 11:35:18 +0000 (GMT)
X-X-Sender: derick@singlemalt.home.derickrethans.nl
To: Nikita Popov <nikita.ppv@gmail.com>
cc: PHP internals <internals@lists.php.net>
In-Reply-To: <CAF+90c-k6SXe9yiqbrUUgwcmz9mtfnQty5_BqxFDgcU-sWEvuA@mail.gmail.com>
Message-ID: <alpine.DEB.2.21.1911061134480.1055@singlemalt.home.derickrethans.nl>
References: <CAF+90c-k6SXe9yiqbrUUgwcmz9mtfnQty5_BqxFDgcU-sWEvuA@mail.gmail.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Envelope-From: <derick@php.net>
Subject: Re: [PHP-DEV] GitHub RFC workflow
From: derick@php.net (Derick Rethans)

On Sat, 2 Nov 2019, Nikita Popov wrote:

> In particular, I would like to start with the following fairly limited
> proposal:
> 
>  * RFCs may still be submitted directly against the wiki, using GitHub is
> optional. For small and straightforward proposals this might be easiest.
>  * After an RFC pull request has been opened against the GitHub repository,
> the RFC needs to be announced on the internals mailing list.
>  * Before voting starts, the proposal must be mirrored to the wiki (as is
> now done with https://wiki.php.net/rfc/union_types_v2), and the vote is
> held on the wiki.
>  * Once voting ends, the RFC pull request on GitHub is closed (not merged)
> with an Accepted or Declined label.

I think this makes perfect sense!

cheers,
Derick