Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110662 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 56066 invoked from network); 18 Jun 2020 16:28:00 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Jun 2020 16:28:00 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A149118054B for ; Thu, 18 Jun 2020 08:13:58 -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=3.2 required=5.0 tests=BAYES_40, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 18 Jun 2020 08:13:58 -0700 (PDT) Received: by mail-lj1-f170.google.com with SMTP id n23so7683325ljh.7 for ; Thu, 18 Jun 2020 08:13:58 -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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WMlCSFHlaDbJtQsMdlK/X7DYIOEb3okfQsjRNY0er3c=; b=hgA7d+f7J7qbACPLh+UjPzdsvLuL0eds0e5PHv6GgZzoqSKHGlHVlciSQPgJpNn/bd lx/tlSLmz4xb1H/boFC+TOy0b0GXo5p1sMKBB58AJI8I5qbFlbWX/jAuHGfcBoWU+o+0 0Xvmnw7YpY4Es/7bOsd3a7WhBCjXOig3mZIvsAA03qLq6m6TAPAjH8SEEbGeiM8kIB8K tzPGY1/rJFVZbG9+hzlrhw24x+nPuclFcmbXzzxz0rfdRdEG1ppnraUEMynJWox5sY6S 4FSaHTQmffvy1OAisbBnLSY2hRA1qjMJryEUYINeFEb0vOPE3XEU5kOM+/rHWfYyGR/r WOWw== X-Gm-Message-State: AOAM532L8sufJQMRDXnW2QbQKU1gcIAQJWRFHWeZTVLY5JBCNHR2m5Bc txv29mJEHAQIPGyYoB+L9yPNNxUobV5SurMLjYjhpQ== X-Google-Smtp-Source: ABdhPJzd87yopoimJxbdicXusjxRaPbZJUDE20oUMyDxj0akWIt30k0hjUKriKZxHfKFEubqV3AOxonajD9p9lTf4ho= X-Received: by 2002:a2e:6c17:: with SMTP id h23mr2733083ljc.48.1592493236705; Thu, 18 Jun 2020 08:13:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 18 Jun 2020 10:13:45 -0500 Message-ID: To: Ben Ramsey Cc: Theodore Brown , internals Content-Type: multipart/alternative; boundary="000000000000ae6c0105a85d3911" Subject: Re: [PHP-DEV] [RFC] [VOTE] Shorter Attribute Syntax From: pollita@php.net (Sara Golemon) --000000000000ae6c0105a85d3911 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 17, 2020 at 7:23 PM Ben Ramsey wrote: > I don=E2=80=99t understand this question: > > > Are you okay with re-voting on the attribute syntax for PHP 8.0? > > I recommended this as a front-line question so as to remove any hint of impropriety about the vote. For example, where the first round of the secondary vote sits right now (15/15/4) we only have 44% in favor of any specific change. That doesn't nearly meet the 2/3rd requirement. By having a "pre-vote" to agree on reselecting the syntax, we have a CLEAR 2/3rd majority saying, "Yes, let's revisit this specific question again". With that clarified, making the decision on what specific syntax we want is less contentious. I had *hoped* that we wouldn't have a party split on the primary vote, that people who wanted <<>> would still favor a reconfirmation of the syntax since it was specifically cited that this would be a point to come back to, but atm that's how things turned out. Is this a vote to see if we want to re-vote on the attribute syntax? I > think this is worded awkwardly, and I=E2=80=99m not sure what the outcome= of a > yes or not vote means for this question. > > Yeah, the wording is awkward, but so is the situation. /shrug I hope the above clarifies it. > If I vote =E2=80=9Cno,=E2=80=9D should I still vote in the secondary vote= , or is voting > =E2=80=9Cno=E2=80=9D effectively the same as choosing `<<>>` for all thre= e choices in > the secondary vote? > > On the primary, you should vote yes if you believe it's worth revisiting the topic, or no if you feel the people have spoken and alligator syntax means alligator syntax. Regardless of primary vote: You should vote on the secondary according to your preference of syntaxes. -Sara --000000000000ae6c0105a85d3911--