Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115511 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 86433 invoked from network); 20 Jul 2021 07:42:46 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jul 2021 07:42:46 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2405C1804D0 for ; Tue, 20 Jul 2021 01:07: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=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,FREEMAIL_REPLY, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-ed1-f50.google.com (mail-ed1-f50.google.com [209.85.208.50]) (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 ; Tue, 20 Jul 2021 01:07:57 -0700 (PDT) Received: by mail-ed1-f50.google.com with SMTP id x17so27353506edd.12 for ; Tue, 20 Jul 2021 01:07:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N9sObQKjz6/TUnrGHwcXBAbiXyciOZp1XK+HHxkoRl0=; b=sr84VUD1eSN6V8TtJ2EHz9H4rSalEXVsmGPAuAp/kP/ElKEo/765mG7ZMSqqIXNQ4C f7VBwcx5dIeRZyVwVck37IkJPzDo2VwvwVE9oyPMyjJb4KjpqD39OUzSdC/fiQXPC8y2 bxSrdG0ylU0ZlzWydcPI9HXihi12okCCP0NPaAqFb+HES9sZYnFJQhJ4Tcn9G48nkcRo BJWRC990Exldn7p3q/SUUO+8a08eCghWKEWwPFiIdf2B0VufYYw6/5CmK8yEkrL3eJPq hGRxjyuJuhpef8ojl54QCpOfAjp7Pie3Db/BxL4xqdk35XTEPny6ixy1flHdWoZLUnWi fQuA== 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=N9sObQKjz6/TUnrGHwcXBAbiXyciOZp1XK+HHxkoRl0=; b=QHTm6Zyy0iBzsU4OSdO4sEDuJV/lJLHrvTvAJ6y7RBaamm3zGXsGEwq1r90NSZ3rzN MJgunvY+GzhKUH9f278t6HeiI4Mklk49U75S237ziBTeg2G1FQXekYt2ukhBn2oQMDVB CiT3KJ6ncfeDrN+caA7tH2ath+vDipmgkKBbK0WzCPtJkNwT+REfLDB0Ox75UPZjxEcN 7oTzRmF0fudM/ELYRlJDNYGsSA82bN8vm9QnJD59oj69ztkhrjmgX9349cROr6o5xFQM 3dcd6wPt+QpO3mxdhO8k34a/ZRKI3ntniY2qmBvneAP4rC4/SQPnML2dO4CcR4yeoGiB GVvQ== X-Gm-Message-State: AOAM530AFOwWvENmv3IEfL0c6on1hGjyCrgQaMWhiHK60Hp+8XAY3n2c z3u4B8WkT4idXbieA0t/oLGAMQGHIN33OGagRv4= X-Google-Smtp-Source: ABdhPJzqL1eWe3R00NqBRHx9FLtdGGLocyWac5eyp7KFO0TWR1+bDUBOEIA7WCpHn61sqBEreBGTScwBFY4bVh3l0CY= X-Received: by 2002:aa7:de92:: with SMTP id j18mr8775790edv.141.1626768475540; Tue, 20 Jul 2021 01:07:55 -0700 (PDT) MIME-Version: 1.0 References: <96487D08-8573-4308-A11C-3118113C03DA@gmail.com> <9d55f768-41d2-d970-8417-aa786d86b984@heigl.org> In-Reply-To: Date: Tue, 20 Jul 2021 01:07:43 -0700 Message-ID: To: Andreas Heigl Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000001dd2cc05c7898d91" Subject: Re: [PHP-DEV] Request for karma to vote on RFCs From: jordan.ledoux@gmail.com (Jordan LeDoux) --0000000000001dd2cc05c7898d91 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 19, 2021 at 11:23 PM Andreas Heigl wrote: > Hey All > > Am 19.07.21 um 17:02 schrieb Andreas Heigl: > > Hey All > > > > Am 19.07.21 um 16:34 schrieb Levi Morrison via internals: > >> On Mon, Jul 19, 2021 at 2:38 AM Nikita Popov > wrote: > >>> > >>> On Sun, Jul 18, 2021 at 8:48 PM Tobias Nyholm > > >>> wrote: > >>> > >>>> Hey. > >>>> I would like to get karma to be able to vote on RFCs. I understand > that > >>>> voting karma isn=E2=80=99t usually given out to people who write the= ir first > >>>> mailing list entry. > >>>> > >>>> But I do believe I qualify as =E2=80=9CLead developers of PHP based = projects > >>>> (frameworks, cms, tools, etc.)=E2=80=9D > >>> > >>> Hey Tobias, > >>> > >>> My response here is basically the same as the last time the topic cam= e > up: > >>> https://externals.io/message/110936#110937 Voting is just the very > last > >>> step of the RFC process, at which point the proposal can no longer be > >>> influenced. If you have feedback about a proposal based on your > extensive > >>> experience in PHP's open source ecosystem, then the discussion phase > is the > >>> time to provide it, while it can still influence the proposal, as wel= l > as > >>> other people's view of the proposal. > >> > >> I second this. > >> > >>> At least in my personal opinion, I think it's important that people > granted > >>> voting rights as community representatives have at least some > historical > >>> involvement in RFC discussions. > >> > >> I agree with this, but have no specific objection to granting Tobias > >> voting karma, as this is underspecified; how long should they > >> participate? What kinds of involvement are appropriate? Being > >> underspecified is not really their fault, and I don't feel like it > >> would be an abuse to grant them voting karma, but do think it would be > >> an abuse to deny them voting karma indefinitely because "we" don't get > >> around to specifying it. It should be less of a decision on a > >> case-by-case basis and more of a checklist. > >> > > > > Sounds like we need an RFC to make it clearer how voting karma for the > > RFC process will be granted in the future. > > I have created a draft for an RFC to implement future rules for granting > voting karma. > > If you want to contribute to that, feel free to open a PR against it[1]. > > To be able to make the future karma grants more trnasparent this needs > input from everyone: Opponoents as well as proponents! > > I'm looking forward to a fruitful conversation and to a great RFC that > can move us to more transparency. > > Cheers > > Andreas > > [1] > > https://github.com/heiglandreas/rfc/blob/main/implement_future_rules_for_= granting_voting_karma.md > > -- > ,,, > (o o) > +---------------------------------------------------------ooO-(_)-Ooo-+ > | Andreas Heigl | > | mailto:andreas@heigl.org N 50=C2=B022'59.5" E 08=C2=B0= 23'58" | > | https://andreas.heigl.org | > +---------------------------------------------------------------------+ > | https://hei.gl/appointmentwithandreas | > +---------------------------------------------------------------------+ > > As someone who only subscribed to internals a week ago, I hope you take my feedback with a grain of salt Andreas, but as this discussion has showed, this is the part of the process that my input might be valuable in. > The requester should search a proponent of their case that then proposes the request for voting karma to the dedicated discussion medium for such requests. The proposal should include the reasons why the proponent thinks the requester fullfills the above stated requirements. This makes sense for a variety of reasons. The first and most concrete being that *verifying* the credentials and history of every person who applies for karma could be restrictively time consuming if it were done in a totally open format. However, my first thought on reading this was "if I was still just an observer in internals and asking for voting karma, I would feel a little strange about emailing someone off the list directly *and* about figuring out who to message that way". Perhaps this could be paired with like... not a mentor program, but sort of a list of people on the list who are willing to field such requests? > After this request there will be a two week period in which objections and approvals will be brought in. When there are more approvals than objections the voting karma will be granted. This should be clarified. I think you intended something to the effect of " After this request there will be a two week period in which objections and approvals will be brought in. Once this period is over, if there are more approvals than objections the voting karma will be granted." The original phrasing makes it ambiguous as to whether or not the entire two weeks must pass for every such case, and also seems to suggest that someone could be granted karma with a vote of 1-0, since there would be more approvals than objections. --- Another aspect that I thought about after reading your draft was a way to structurally avoid concerns about stacking. I don't believe that there would necessarily be overt efforts to grant karma to individuals to push certain concerns to the side, however it might be worth considering if the process could promote a variety of opinions and backgrounds. Even if such a situation were considered unlikely, it could be worth writing such a process with that in mind if the process involves a sponsor. As I said earlier, it makes sense for many reasons to require a sponsor to get voting karma, however this may unnecessarily make the applicant associated with their sponsor or their sponsor's history and contributions (which could be a positive or negative to one person or the other). It also makes it less likely that a perspective which is totally unrepresented gets sponsored. This could also be a positive thing, as not all perspectives are truly relevant or constructive to all the processes. But it might be worth considering these impacts explicitly. It's also worth considering if people believe that this is a process that will be iterated on or if there is a desire to get it right the first time and stick with it. Perhaps if the intent is to iterate, or at least explicitly revisit the criteria, the RFC could include an expiration at which time a vote to either keep or change the process could be held, which gives everyone clarity and certainty about the structure over a given period. Those are my immediate thoughts on your rough draft. Jordan --0000000000001dd2cc05c7898d91--