Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119958 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 19923 invoked from network); 12 Apr 2023 14:09:23 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Apr 2023 14:09:23 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id AF68C1804D4 for ; Wed, 12 Apr 2023 07:09:22 -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,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS8468 78.32.0.0/15 X-Spam-Virus: No X-Envelope-From: Received: from mint.phcomp.co.uk (freshmint.phcomp.co.uk [78.32.209.33]) (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 ; Wed, 12 Apr 2023 07:09:22 -0700 (PDT) Received: from addw by mint.phcomp.co.uk with local (Exim 4.92) (envelope-from ) id 1pmbA0-0005nz-8w for internals@lists.php.net; Wed, 12 Apr 2023 15:09:20 +0100 Date: Wed, 12 Apr 2023 15:09:20 +0100 To: PHP Developers Mailing List Message-ID: <20230412140920.GD2480@phcomp.co.uk> Mail-Followup-To: PHP Developers Mailing List References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Organization: Parliament Hill Computers Ltd User-Agent: Mutt/1.10.1 (2018-07-13) Subject: Re: [PHP-DEV] Moving PHP internals to GitHub From: addw@phcomp.co.uk (Alain D D Williams) On Wed, Apr 12, 2023 at 04:52:52PM +0300, Alex Wells wrote: > Based on those issues and PHP, I propose moving the discussions elsewhere - > to some kind of modern platform. Since this is quite a big change in the > processes used, I imagine an RFC would be needed. But before I do that I > want to measure the reactions. If it goes well, I'll proceed with an RFC > draft. Please: No. The nice thing about email is that stuff just hits my mailbox and I deal with it when I have time. I have my MUA (mutt) always running, I do not want to have something else to monitor. Your points: * having to subscribe. An easy one off task. * Archives: already done * Having to learn rules, bottom posting. All communities have rules. As you say: not hard * Not way of editing: just send a follow up. * No formatting. What is wrong with plain text, it is how PHP is written ? * No reactions. If people are interested they will reply. I agree that one flaw with email is that it is not good at remembering things, that is why people do things like writing RFCs. Note: I mainly lurk on this list, only occasionally making comments. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html #include