Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120744 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 26762 invoked from network); 4 Jul 2023 23:42:36 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 4 Jul 2023 23:42:36 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D25321804B0 for ; Tue, 4 Jul 2023 16:42:35 -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.0 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE, 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-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 4 Jul 2023 16:42:35 -0700 (PDT) Received: by mail-ed1-f53.google.com with SMTP id 4fb4d7f45d1cf-51d9890f368so6779016a12.2 for ; Tue, 04 Jul 2023 16:42:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20221208.gappssmtp.com; s=20221208; t=1688514154; x=1691106154; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RUuZ5IKm/XYkxaDZxA91NfC867tpJrzlNDBvT1m7bP8=; b=MFi4LGOfRBvVZXPOEW7h+bDqlTkRu53ZeAEFOw/ZK/PSzpHY3vfH6Zb/3PHzdImUrm b/fWComTBB6YV0fwCxwsrrRe6SaDGAcfUkanh9jwKD/HOFUEWA20HGngeauyN3KW2bvl YgVgMQSVD3B16lIRcLt4loFqSppVIeEz+48sd3YdmhFSSf8tZNk9wy0ZzFKcR+pJ0w3s sY/hQNwsK8ogdvgo+KMLz9DCKH1t0LZVE0DU3UkzArVTrJJWtXS2c5v/S58Khkmumls+ ACyTcVp5U2GxZ/Vf0MgAqn/apMhHLkJtmwfQgSLsJXvHlLB1Y4iKVbDdiL+YQnrj/v0C wR0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688514154; x=1691106154; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RUuZ5IKm/XYkxaDZxA91NfC867tpJrzlNDBvT1m7bP8=; b=d+YfBiaGoOD/8J0iZk/eDAj7vm2BIOmQ38cqHtFgEQzkacgKdRBXtC+lSpfeO7LJSn JlfgFuu/gZgDrapff4OkbbZJCCd4Ah/fqTCZ6d0yn1LuScQgDe3+kBnZeBc+7Ez95MqP MnanSkRPm6yKPocVZVmivd/FHB6NeyNkJ43xLeRGgZsHJtNhNSb8j205/vE24GlK9DMl sMMNH5y5Kr4XeU38A7fbuouQJchuhlBIlrP8yCtF4SxG2hsChk5D8ClwMvsTuysyO+rR gln1e1fV/Xdv45lOmZlkf8b61OzFDBBcfb0xGmw9P3E1Cp+5PTkLwgo0VmXVevKeHbkf vFeg== X-Gm-Message-State: ABy/qLaUKfuA1eRdJy8LO1ABu7gkXfq8UZHuda+z4m15jG0307CNqgtI eN1uibgp8U7heF49l4QQpcwazOkuFeK1lRYy0FIpPQ== X-Google-Smtp-Source: APBJJlEyeV4FQ2AfGDW2/pBfi7tnKCdUokZRLcsy5sRRuepY76HcOgTKSEJmr5PwmgjaDvuzfblyaRg9JWiYXS0t0Uw= X-Received: by 2002:aa7:d742:0:b0:51d:aa00:bdd4 with SMTP id a2-20020aa7d742000000b0051daa00bdd4mr10232488eds.24.1688514153604; Tue, 04 Jul 2023 16:42:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 5 Jul 2023 00:42:22 +0100 Message-ID: To: Nuno Maduro Cc: PHP Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Request karma privileges to vote on PHP RFCs From: Danack@basereality.com (Dan Ackroyd) On Tue, 4 Jul 2023 at 20:30, Nuno Maduro wrote: > > Hi Internals, Hi Nuno, > I believe having a Laravel core team member on the list of members with > voting rights would be incredibly valuable to the internals team. All open source projects value contributions to their project really highly compared to pretty much everything else. There is nothing stopping you spending time and helping to improve RFCs or fix issues. You don't need any karma or permission to do that. > I have a strong connection with the Laravel community, I think presenting the voice of a large number of downstream users would be useful. Instead of giving a personal vote for yourself, how about we*, the PHP project, think about setting up a vote for the 'Laravel project' as a voting entity? The idea being, your users can come together and give feedback as a single voice, in some public source the Laravel project publishes e.g. laravel.com/net.php.wiki/rfc/some_rfc_name/feedbackrather than having the whole burden of interacting with internals be solely on yourself. I've been meaning to say some stuff about communication between internals contributors and downstream users for a while now. I'll try and finish that email, but I think setting up something like that, would be a better path than the one we're currently on. To note, it will probably take some time to figure this out. I'm reasonably sure people will have opinions. Possibly quite a few. cheers Dan Ack * not that I actually am the PHP project, but I'm probably part of it.