Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118666
Return-Path: <tim@bastelstu.be>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 48310 invoked from network); 19 Sep 2022 21:50:19 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 19 Sep 2022 21:50:19 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id A6C0A180384
	for <internals@lists.php.net>; Mon, 19 Sep 2022 14:50:18 -0700 (PDT)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS24940 176.9.0.0/16
X-Spam-Virus: No
X-Envelope-From: <tim@bastelstu.be>
Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Mon, 19 Sep 2022 14:50:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be;
	s=mail20171119; t=1663624216;
	bh=JIZpSXCoFfOGYKRaNncwrjTa8hampezPR9gL1crnxN0=;
	h=Date:Subject:To:Cc:References:From:In-Reply-To:From;
	b=J2T/EeEh2hvdTGRw8ZQ7ZPDaLmSZ91gZ3niYy4gULuxswK47H7ETtCwMkBdY3+6iS
	 vRvBD/XiaWkQDOcM0wYnQyOrhe/EkXEWBzy9sIbrxvGigRZqcn19QP0EKnXnqaS7V4
	 Kk9t5J+4jjvmb+OgLAl78kurdzmMuTxVVs6yFvvFxLkktTZAjYr33+Mb+G5vgC2GL9
	 ZNJyF77OsA+TA4VmzDeeXJgff+2o02AwA/zAObk6mYsbEVUYsacKluvom32TfY/hTt
	 yZCeSva3NtKVksmAwOcOON/9K9vTQPVHXYMQdwtdFmG+GAJA+z+uWKAIBWQipYwL7Q
	 tHgdftFs6kxnw==
Message-ID: <8ad11ab3-672d-18af-3b75-3255a0c7ac53@bastelstu.be>
Date: Mon, 19 Sep 2022 23:50:16 +0200
MIME-Version: 1.0
Content-Language: en-US
To: juan carlos morales <dev.juan.morales@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
References: <CANMwmbN8_Km+urXbNO7oWvNteYA2mTPNYyRgfaoypEK1Cw4F0A@mail.gmail.com>
 <f84e6740-20c6-45fa-d286-a132a9c92543@bastelstu.be>
 <CANMwmbMN25w0xdpaSJ23GHdpkCJb+b0-k8JfBnfDfzEP2Fbh4w@mail.gmail.com>
In-Reply-To: <CANMwmbMN25w0xdpaSJ23GHdpkCJb+b0-k8JfBnfDfzEP2Fbh4w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] RFC json_validate() - status: Under Discussion
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=)

Hi

On 9/19/22 23:26, juan carlos morales wrote:
>> It appears the discussion came to a halt. How do you plan to proceed
>> with your RFC?
> 
> Thanks for the heads up email Tim.
> 
> People, following the procedure, this is a "heads up" email to all of
> you regarding this RFC. If no significant issue/complain raises, then

The RFC still contains a non-empty "Open Issues" section. This needs to 
be resolved before the vote starts.

I would also recommend inserting a closed voting widget (or multiple, if 
you want to have additional votes for the details), so that it's clear 
for everyone how exactly the vote will look like.

Best regards
Tim Düsterhus