Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115517 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 2364 invoked from network); 20 Jul 2021 09:32:04 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jul 2021 09:32:04 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D0C801804D0 for ; Tue, 20 Jul 2021 02:57:15 -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.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-qt1-f175.google.com (mail-qt1-f175.google.com [209.85.160.175]) (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 02:57:15 -0700 (PDT) Received: by mail-qt1-f175.google.com with SMTP id j7so2067378qtj.6 for ; Tue, 20 Jul 2021 02:57:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Wa6mFbeaqT7hd/3O9bXMajYduydpxgCl6IO70wzNgjk=; b=Rt47CP1Y/F/OjDbMWm7J6rj7v5Fa6/EayhpIjBaeb0928uRoWIYj9MrvEg9CBMA0nb 9pnbfMq7xB2ZOhoT1XtEoN+WvsrUc6uot+fFob7ps/vVFF4a7+kaKIb4kP6FZFHG2yLX 3ody7JLVu+kkwLjZ7I0rH0+/xAnWM64/sJGGLRYFlHlSMVfGIXcXXFp/RBc99GpPS4YJ 3O0VpRtwKcYnBXQK/eD0veJecLSwLrWVK8C7QNzXDY6gDbe4io0ut0/cJVJihi/mdaA+ gVDvEW+QSXfepAXswaV2IdcncAPKqWOEcOIlmdoZ23bFbllcgz4GaFVF6wkfbF2Xduvh JgLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Wa6mFbeaqT7hd/3O9bXMajYduydpxgCl6IO70wzNgjk=; b=LqWMH8gHrayMP77UrnnL3L0IAUYDblHtF84gFtCCy02FX5x5iiWkrZWlkjg1451pGI yMzWjlA+i79ODI62pr36Pw3IlBURraqWuyUzcLieN+H6NmOlTed2qeNdsP+rmfRyJPQX sDexHcelamPLZSn2nf+NjGPFT9O37z6T5V0aoMo/8NnM4WOKUTcCCHYwxQAf1uCGCs08 d05zFn2QD/MAirCDvfTcjNchBuIxK+EPnPsDrMv66EcjiCF819EnqGf7zxQSA2DQMauM +zJbLubCX48SFyfy4PghbI4UaYR0EfQmleqrkpnRNMLKGuNEsfFAkl+cCkKW1xDJgAsh F7Yg== X-Gm-Message-State: AOAM533/xKR09MzEaH5vyDvfA7P7m8kNYPxTXe+D6v4WNKqJAF+G8IDo Gc20HK9opUqnJvjB/1DHcH4TbkvZPTPoNzoy X-Google-Smtp-Source: ABdhPJyswhuratCwhLYxgPNRqVSZNHISsNfaap9aL07683L6+9Prm0627id3NVDhJPzb32JkMysNRQ== X-Received: by 2002:a05:622a:1810:: with SMTP id t16mr10300472qtc.272.1626775033404; Tue, 20 Jul 2021 02:57:13 -0700 (PDT) Received: from [192.168.1.10] (c-24-98-254-8.hsd1.ga.comcast.net. [24.98.254.8]) by smtp.gmail.com with ESMTPSA id q3sm9255476qkn.14.2021.07.20.02.57.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Jul 2021 02:57:12 -0700 (PDT) Message-ID: Content-Type: multipart/alternative; boundary="Apple-Mail=_5E2BA408-9D33-4B2E-ADF6-3064923D39F3" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Date: Tue, 20 Jul 2021 05:57:12 -0400 In-Reply-To: Cc: internals@lists.php.net To: Andreas Heigl References: <96487D08-8573-4308-A11C-3118113C03DA@gmail.com> <9d55f768-41d2-d970-8417-aa786d86b984@heigl.org> X-Mailer: Apple Mail (2.3608.120.23.2.7) Subject: Re: [PHP-DEV] Request for karma to vote on RFCs From: mike@newclarity.net (Mike Schinkel) --Apple-Mail=_5E2BA408-9D33-4B2E-ADF6-3064923D39F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Quoting the RFC > the requester has contributed to the PHP sourcecode ecosystem. You mention what types of contributions apply, but give no indication of = quantity. If someone fixes one bug, does that give them voting rights? = I would assume not. So is it two bugs, 10 bugs, 100? > these contributions show a consistent effort How is "consistent" defined? How frequently and for what minimum time = period? > the requester has shown interaction with the main discussion medium of = the relevant part This is unclear to me. I assume "the main discussion medium" is more = than just the mailing list, otherwise you would have said the mailing = list, right?=20 And what does "relevant part" mean? Maybe some examples would help, = at least in reply. > the requester has a proponent that currently has voting karma Agreeing with Jordan LeDoux, these seems primed to make current voting = members a target for wanna-be voters.=20 Maybe this could discuss processes that would naturally bring people to = want to sponsor someone, such as (maybe?) recommending they first = "apprentice" under one or more people by helping document, helping fix = bugs, or working with them on an RFC?=20 > 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. Are you really suggesting that allowing someone new to vote would be = held out in the open, where the discussions about that person will get = recorded on externals.io and indexed by Google = for all to see, forevermore? =20 Seems like discussion about an individual should respect the long term = privacy of the individual a bit more, especially for those who will be = turned down.=20 > When there are more approvals than objections the voting karma will be = granted. How is voting to be done? Yay's and nay's on a mailing list? Or some = other way? =20 And voting right can be approved with 51% whereas most RFCs require 67% = to pass? I ask these questions so people who might be interested in getting = voting rights would have an objective roadmap for how to get there = otherwise it would seem to just be documenting an extremely subjective = process. (Which might be all you are attempting to do?) Anyway, #jmtcw. -Mike > On Jul 20, 2021, at 2:22 AM, Andreas Heigl wrote: >=20 > Hey All >=20 > Am 19.07.21 um 17:02 schrieb Andreas Heigl: >> Hey All >>=20 >> Am 19.07.21 um 16:34 schrieb Levi Morrison via internals: >>> On Mon, Jul 19, 2021 at 2:38 AM Nikita Popov = wrote: >>>>=20 >>>> On Sun, Jul 18, 2021 at 8:48 PM Tobias Nyholm = >>>> wrote: >>>>=20 >>>>> 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 = their first >>>>> mailing list entry. >>>>>=20 >>>>> But I do believe I qualify as =E2=80=9CLead developers of PHP = based projects >>>>> (frameworks, cms, tools, etc.)=E2=80=9D >>>>=20 >>>> Hey Tobias, >>>>=20 >>>> My response here is basically the same as the last time the topic = came 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 = well as >>>> other people's view of the proposal. >>>=20 >>> I second this. >>>=20 >>>> 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. >>>=20 >>> 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. >>>=20 >>=20 >> Sounds like we need an RFC to make it clearer how voting karma for = the >> RFC process will be granted in the future. >=20 > I have created a draft for an RFC to implement future rules for = granting > voting karma. >=20 > If you want to contribute to that, feel free to open a PR against = it[1]. >=20 > To be able to make the future karma grants more trnasparent this needs > input from everyone: Opponoents as well as proponents! >=20 > I'm looking forward to a fruitful conversation and to a great RFC that > can move us to more transparency. >=20 > Cheers >=20 > Andreas >=20 > [1] > = https://github.com/heiglandreas/rfc/blob/main/implement_future_rules_for_g= ranting_voting_karma.md >=20 > --=20 > ,,, > (o o) > = +---------------------------------------------------------ooO-(_)-Ooo-+ > | Andreas Heigl = | > | mailto:andreas@heigl.org N 50=C2=B022'59.5" E = 08=C2=B023'58" | > | https://andreas.heigl.org = | > = +---------------------------------------------------------------------+ > | https://hei.gl/appointmentwithandreas = | > = +---------------------------------------------------------------------+ >=20 --Apple-Mail=_5E2BA408-9D33-4B2E-ADF6-3064923D39F3--