Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115489 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 10272 invoked from network); 19 Jul 2021 13:19:32 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Jul 2021 13:19:32 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5C7E3180532 for ; Mon, 19 Jul 2021 06:44:31 -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,FREEMAIL_FROM, 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-vk1-f179.google.com (mail-vk1-f179.google.com [209.85.221.179]) (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 ; Mon, 19 Jul 2021 06:44:30 -0700 (PDT) Received: by mail-vk1-f179.google.com with SMTP id m33so3808425vkf.6 for ; Mon, 19 Jul 2021 06:44:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2zuBcccXSW6x1jjCHx5fbtOH6qW0xuDBHgMpa72Lh8I=; b=odn5No9ysYumPTxANCZgaKE7v6D8PNhJ64uabb01rePaj1huYh4cndMOYxzHkRbld0 rI9I1U+NLwhd4JynQB2/ttVvdUmtdVJDAiVGW0cyWBwSemv/LzqUC9l6UxkwtVjEFKZA QAEGXar0Ywj6c3PgjnHmGUg4qZO1FgupPZMpZ6CPgyWBZSRkibhoDaMxOah13UqCX3o5 nFlrRjnZyZieZNski1JlPfMOr8zuNgqDY/e6flEOMjvjzX0Fh8kFDlcTpXg/hRi2MVOn P47OjrQlrcp6JSy3R3IYszeyDYD3Z6ERTLd2MKqqOPPj+sKMkddvHir6ulGWZy/TkC24 29SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2zuBcccXSW6x1jjCHx5fbtOH6qW0xuDBHgMpa72Lh8I=; b=dhbkZFJX6Ec4cGw7fOEsW088WFhPlzmvJvYlkvVl6GBnK6CFf2Ta31u0ZKMhn6BY97 ZAf7DvYmvAHIyMjjzO4mMm1+JzK1QjbEMfLTIra3ypItZsZsMmoyjW69wH6dHuJ3Eilw 4pnyJYxAcsN5v+fkNtq5ceK1Md2x+e+LV8E3Ai7bwfErTRPO9l1e3xTBg5Hjg6GrG0AS Xp+Bbm4b0mwoE5gbD/wqfhscp6AX5qo9D62gv9OmE91T5KZ5ulGegyaZ0AGxv4kDVgBE PngutJe4jiRm3FXWOngRkjFINmwKec1exW2FKoY5awUR8RHJzFiGglWaknWPEAiH6Hi/ zslQ== X-Gm-Message-State: AOAM531dKybyRFA1ql7TCRCmMhVxuk4yOLwddUihM8besbCIw5bbxKh3 kysdpfo3csjUdOeEUh31ZmSfNlbnvKlkdwrBxsM= X-Google-Smtp-Source: ABdhPJzz4h27bfLeFZ8Io2Yw8t5mHp6Ith3Ve/d3hooAFPgkfokCBvfXTkz81E54K2tTKJgM1rIEWsEgU4ZEJbudRUg= X-Received: by 2002:ac5:c956:: with SMTP id s22mr15880344vkm.2.1626702269126; Mon, 19 Jul 2021 06:44:29 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab0:678c:0:0:0:0:0 with HTTP; Mon, 19 Jul 2021 06:44:28 -0700 (PDT) In-Reply-To: References: <96487D08-8573-4308-A11C-3118113C03DA@gmail.com> <0ddf2ddc-762e-7ce6-2c3c-e2b0f55e584f@processus.org> <2a76525c-6d11-b9af-9d41-ff9fb18e4843@processus.org> Date: Mon, 19 Jul 2021 18:44:28 +0500 Message-ID: To: Kalle Sommer Nielsen Cc: Lynn , Pierre , Tobias Nyholm , Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Request for karma to vote on RFCs From: office.hamzaahmad@gmail.com (Hamza Ahmad) Hello all, Tobias wants to obtain a right that lets him represent the community in the RFCs' approval. Tobias, as for the feature requests, you can discuss and propose your own ideas. You can also obtain RFC karma to propose your ideas and contribute to the language. As for the people that are going to give the final vote, PHP maintainers need to make a proper policy for this process. I am going to give a basic idea. They can better brainstorm. The person that wants to have the voting rights may qualify for the following: 1. The person may have RFC karma already. 2. After obtaining an RFC karma, it may have been active on the mailing list for a specific time period. 3. It may have n number of bugs solved and merged. 4. It may have worked with senior developers of php at least on the n number of RFCs. 5. Optionally, it may have some of his own RFCs approved or rejected with minimum percentage. 6. Every person that gets voting rights may have fulfilled the conditions above. When it qualifies for the above conditions, it can apply for the voting karma. The people with the voting rights can recognize its efforts and contributions for the language and finally allow a voting karma. The karma will be rewarded with a simple majority after a vote. The conditions that I have suggested above assess following: 1. The person is well aware of PHP and its built system. 2. The person is able to resolve bugs, add new features and improve existing ones. 3. The person well understands PHP's nature and is able to form the ideas accordingly. Tobias's scale of qualification will motivate a large number of people to ask for the voting rights, and they have the equal right to get the right to vote. It doesn't matter a core developer maintains n number of libraries. The thing that matters is the understandability of the core. If one is able to contribute to the language and its efforts are visible to the core developers and the community, it may have a voting right. Yes, having developed numerous libraries can be an edge. Nobody will object because one receives a karma according to a set policy. Additionally, when there emerges a policy, it will motivate people to partake in the discussions, practice their hands on the PHP core and leverage the company of senior developers. Power to you all. Best On 7/19/21, Kalle Sommer Nielsen wrote: > Den man. 19. jul. 2021 kl. 13.14 skrev Lynn : >> Currently there are people with voting permissions that do vote, yet do >> not interact with RFCs or the mailing list. Regardless of the reasons one >> may have for wanting to vote, the requirements given should be applied >> equally if this is the argument. > > If this is a problem, then why has the voting RFC not been amended to > require such commentary? That seems like a productive first step in > solving the issue instead of complaining about it not happening > automatically > >> Yes, and I love it when I see new users interact with the mailing list, >> even when in the end the questions or arguments changed nothing to the >> RFC. It shows that people are probably invested. How do you measure >> investment behind the scenes though? How often has someone decided to not >> post anything on the mailing list because after testing a bunch of changes >> proposed, it worked and required no comment? > > How can I take that into consideration if no one lets me know about > that? This argument sounds more to me like an illusion, I cannot read > minds nor am I into experimentation on the matter, I cannot consider > what I do not know (similarly to the problem you pointed out above). > >> Would every user that one day would want to have voting rights post a "yes >> I agree" message in every thread in order to show they contribute in >> discussions? > > That is not what I was implying and I am certain you know that. I > specifically mean the discussions, not the voting itself. Taking > Tobias here as an example, why is there no feedback from him on the > RFCs like[1][2][3] (which was recent as in 8.1, this is just a list > from a quick glance which may or not be accurate), they seem to me > like an good way he could have given feedback based on the work he put > forward that he had been involved with. > > Why is it that political power should just be given without actually > taking part of the project and problems here at the PHP project? To me > that comes off as laziness. "I just want to vote, but take no > responsibility of maintaining the PHP project" > > [1] https://wiki.php.net/rfc/curl_user_agent > [2] https://wiki.php.net/rfc/fsync_function > [3] https://wiki.php.net/rfc/fibers > > > -- > regards, > > Kalle Sommer Nielsen > kalle@php.net > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > >