Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117881 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 99596 invoked from network); 8 Jun 2022 20:00:42 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Jun 2022 20:00:42 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EE0A018037E for ; Wed, 8 Jun 2022 14:46:47 -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=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-wr1-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 8 Jun 2022 14:46:47 -0700 (PDT) Received: by mail-wr1-f46.google.com with SMTP id u8so25650414wrm.13 for ; Wed, 08 Jun 2022 14:46:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=pNKPSkd369wPosS6z/XwCxIzcVOg3zR9Do220knSnFw=; b=DB3GJ3ZC7taEZgHXIlz0LSfQhNYqqfgchj5hzxGmJGvOped3hDWLPr0XJ4WvuPdFK6 9op5u4LAdtgldENK5a64U0b6Z/SD8Qd8caflU0q98OP7i3MIlW0D7vA9YS8YXmrctldE NFO+XwundlwAIuJy3qLaXd7HXcO9UIFs7P1LVui1L4n1AiSVSX7dX/rvoQccUik2JPnK RURcq54okPWl1uy530LAKRLWk4xiUNSZYkMfM1kiVOzg5QO8RSQ1kf38zmq2UeCJ9zzN 2hpnKg9iFMUXljwRdqtP8VE1g0A/+NSlKUblSZZWTO404eRT71gp9rEKn71yIErIFgmF 5MYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=pNKPSkd369wPosS6z/XwCxIzcVOg3zR9Do220knSnFw=; b=ORxjtV0REyQvQLHjp8oLcZ2+jQip+VKKmrloXoIo69uSDSAiSaxjFsWyT/Qsm2apqO Pu+waC+fLZ/Owf4NMtjpYCYE3aZGdqEz0EG4t96QwwAMX1Ta1RWflYG13PGKwaxhCUEP 3va8Ib3Z5JqhsyvxlJEenJSwmCF8l4HlGE3WISV+kVZlcdsjneXrrOS4sNr01N90lWd7 Cm98L8K9IC/EsO5lXIKGXqVQYUfSTcZtW/9l241E2xVBYWB7OuPq88hWDE0/agagXBkf 0yXAl5nvuH9l0RRvOOC6St97dBv/Cj87jZepyWoE6ul0oW2ufzVTZnxlwAjJwYU1zYsy hGZQ== X-Gm-Message-State: AOAM532vDTCjE4Aw2L0ly9386Z8o17xrskG0hi8pqItG9oLTVdqX3s1e YeURNnQtl4/5gqBnopUUE9krUCIbMII= X-Google-Smtp-Source: ABdhPJzdv29iNswGtb+1jBmuUH4WDqHbqABXAYgQszui71uceeXyitoPg0FMbyODEctUcVar0FJwiA== X-Received: by 2002:adf:fa81:0:b0:20e:69df:5f06 with SMTP id h1-20020adffa81000000b0020e69df5f06mr35527087wrr.188.1654724806371; Wed, 08 Jun 2022 14:46:46 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id n3-20020a1c2703000000b0039c4b518df4sm16167807wmn.5.2022.06.08.14.46.44 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Jun 2022 14:46:45 -0700 (PDT) Message-ID: <3c315975-4e23-e4b7-48b8-cecd883c1776@gmail.com> Date: Wed, 8 Jun 2022 22:46:43 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Content-Language: en-GB To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Re: [RFC][Under discussion] Create a global login system for php.net From: rowan.collins@gmail.com (Rowan Tommins) On 08/06/2022 20:22, Aaron Junker wrote: > But I have two questions: > > 1. What kind of majority in votes will this RFC need to get accepted? > 2. Am I allowed to vote on my own RFC? While this is a somewhat unusual RFC, because it's a change to the project / infrastructure, not the language itself, it should still follow the rules here: https://wiki.php.net/RFC/voting Question 1 is straight-forward: "The primary vote of an RFC, determining overall acceptance of the proposal, may only have two voting options and requires a 2/3 majority. ... [Secondary] votes may have more than two voting options and may be decided by simple plurality."  So the overall RFC requires a two-thirds majority; the others can be simple plurality (but you should probably make that explicit on the voting form). Question 2 is also covered on that page, although the wording is a bit odd. The proposer of the RFC is not *disqualified* from voting, but they are not automatically *eligible* to vote. So, if you can vote on RFCs in general, you can vote on this one. Specifically, as noted at https://wiki.php.net/rfc/howto "Note that RFC karma does not automatically give you karma to vote." Regards, -- Rowan Tommins [IMSoP]