Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119829 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 83851 invoked from network); 7 Apr 2023 10:58:21 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 7 Apr 2023 10:58:21 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 440C0180211 for ; Fri, 7 Apr 2023 03:58:20 -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.5 required=5.0 tests=BAYES_20, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, 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-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (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 ; Fri, 7 Apr 2023 03:58:19 -0700 (PDT) Received: by mail-ej1-f51.google.com with SMTP id qb20so7597969ejc.6 for ; Fri, 07 Apr 2023 03:58:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680865098; x=1683457098; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=g9a/kqRP1cucSIbl5zio9mY5Zdflsv66pI/DnYbr27c=; b=svFivLlMKN8pZm/YoUD1bTqqraNpM/C+FAyGILhu+36kprkjWMXP6411FepxwQz7Z0 NERPcktICQHTuBRqywVBr/a5vMzJp3SU3/OX0t9mtm06Xe6WxwM4aPOVx0+17gJYiFkx +0bt2cLketG7q5spuofob1UybRx7wNjEFcZg1qIby9SwJunjxjyobqdO/yR/611JatQW 05Os9mCHNAmTEj+wMcwlvk2wadCVfnuxVtXcnNoMAYkJKtNzfeprHltSVGXvHWclTvDB CgBWM4bDqqDAweGxr/mwwPgLSE9bi9S8pUQHwQz3JHKxbMIYjDJl3bEgV9T6pjZqT3aI jjEQ== X-Gm-Message-State: AAQBX9fom7qUW7/QnGtMP91AjuAtN1ssb8eheHe2P8JoSpG7ZWbScsR7 qCfM50L2qUrTZRE9VhnjDAQE0vk778Y/lckQhUk5V6BeuHo= X-Google-Smtp-Source: AKy350aDMEfdm+ur4M3mugj5/R77jauiCug3+mMkpekV8E78XKp30bqB5ceFoPkrFteb+VT+7TWrGy38cT573mLNwLw= X-Received: by 2002:a17:907:9714:b0:926:5020:1421 with SMTP id jg20-20020a170907971400b0092650201421mr1032679ejc.9.1680865098292; Fri, 07 Apr 2023 03:58:18 -0700 (PDT) MIME-Version: 1.0 Date: Fri, 7 Apr 2023 11:58:07 +0100 Message-ID: To: PHP internals list Content-Type: multipart/alternative; boundary="00000000000019622305f8bce733" Subject: [RFC] PHP Technical Committee From: bukka@php.net (Jakub Zelenka) --00000000000019622305f8bce733 Content-Type: text/plain; charset="UTF-8" Hello, Here is a proposal for an introduction of the PHP Technical Committee: https://wiki.php.net/rfc/php_technical_committee The main purpose of this RFC is to have better decision process when technical conflicts between developer arise. This was created in collaboration with other people involved in PHP core development and the PHP Foundation. Larry has done a lot of work in rewording the text and he is also a co-author of this RFC. Feel free to comment here or if you have just some wording suggestions there is also a PR in my util repository for easier collaboration on the text: https://github.com/bukka/php-util/pull/1 . So feel free to comment / send suggestion there as well. Regards Jakub --00000000000019622305f8bce733--