Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107458 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 37612 invoked from network); 9 Oct 2019 20:56:08 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 9 Oct 2019 20:56:08 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id E01AC2D2073 for ; Wed, 9 Oct 2019 11:38:50 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.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,SPF_HELO_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-yw1-xc32.google.com (mail-yw1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Wed, 9 Oct 2019 11:38:50 -0700 (PDT) Received: by mail-yw1-xc32.google.com with SMTP id 129so1186145ywb.8 for ; Wed, 09 Oct 2019 11:38:50 -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=WRfgEX5JERsrE/1AgKQaNqw5RfV0FM6/cN0eqEcs1ow=; b=Y/gCgqM5DBlAyy63FOUzIT5dQOdPvIICOe4TdgODXU9I6/otprJ7Wp7EkwU5Hxoyfa ZMtIEfZEGxvj1tD3NFOEawMdcx2gsH/0Vf0B6G+UfV1/NGp4wH1dQEety2FwEQwhXhGz 1yguD65pAbLjxHQ4Mzm78gnK0wm8nXygmxreiw2xHD03SItwt2rTCaHogFHea055j4KW AUpjGSpDHDim/jDllGM1a9X3zTA1MvOGWZAal0tTwXCVW5+clnsmF/dLYc12m3Bla88X i353voZ/qSWxtCtxKYz9QxEO0QzBPk0dDhztrGd81l9ZiHTMyj2CHyUjslRDZCphnBuG I0Dg== 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=WRfgEX5JERsrE/1AgKQaNqw5RfV0FM6/cN0eqEcs1ow=; b=ouvN1t0BNZ8X3fTZ7HHvxHGW1xOvuqYbEApEtz2oEDPHEaugrM0CJw8Q46N8SXs0zc 1MYQUeTDpJAOzTuT6opqfD/Rx5UFtL2S35bDr9dtUMeHV7B/DpQuWukyUwMrk8htWXvK uNcA9fYPge9e5+4443BpDKBK0f7msWAwSj1eXZjPG5cEoEyPOyL6LMCcS6w03vPeXzQ/ n3bzue3/EJLgW3SQciPf2iKMn+ihRWnwL4DaPJ5hrSQpuFliVd7HGAuYKUP1U0O2aqz9 WlL6Q5ONzrMoBY8jr5qqTdqHt3hWx2YataTKeVkjMP6hoNNLMNsQhQD/1HOTlp8Q/9r5 4SsQ== X-Gm-Message-State: APjAAAUNanJVObR7GiT9ehjiNu3JsgVtK7j3aacDBt0vqH/XXlPNegAn JaVjvtd+ERB52anLt9eFsCQDzA== X-Google-Smtp-Source: APXvYqzAQbKI+4bxMX7VaKvmrBZTmehbAysxyrpMh3TNvdLyEQgW5mu3v+N1K6Y+83tz2jrvZGZ4rg== X-Received: by 2002:a81:334c:: with SMTP id z73mr3703212ywz.242.1570646329568; Wed, 09 Oct 2019 11:38:49 -0700 (PDT) Received: from ?IPv6:2601:c0:c67f:e34e:f8e3:72ed:6838:abec? ([2601:c0:c67f:e34e:f8e3:72ed:6838:abec]) by smtp.gmail.com with ESMTPSA id t82sm763715ywc.26.2019.10.09.11.38.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Oct 2019 11:38:48 -0700 (PDT) Message-ID: <67A49D41-A65F-4C07-82B2-1C19F17B2200@newclarity.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_D3B8CB43-2F55-4E8B-A513-BB26BAC64E5C" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Wed, 9 Oct 2019 14:38:47 -0400 In-Reply-To: Cc: php internals To: Larry Garfield References: <5d976928.1c69fb81.db3a8.78daSMTPIN_ADDED_MISSING@mx.google.com> <413d377a-4ce1-a521-0cb4-5bb37e84c257@gmail.com> <6DFA91F7-0005-453E-A314-A5DFE1A4D3D3@newclarity.net> <82012CD7-088D-4010-922E-AD54186AE37A@newclarity.net> X-Mailer: Apple Mail (2.3445.104.11) X-Envelope-From: Subject: Re: [PHP-DEV] Internals "camps" From: mike@newclarity.net (Mike Schinkel) --Apple-Mail=_D3B8CB43-2F55-4E8B-A513-BB26BAC64E5C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Oct 9, 2019, at 12:58 PM, Larry Garfield = wrote: > And developing such guidelines absolutely positively cannot happen on = a public asynchronous mailing list. I've been through such processes = enough times to know that is the worst possible way to do it. When I first saw this email I thought you were proposing IRL "camp" ala = a symposium/convention/assembly where "delegates" from the internals@ = list were to get together face-to-face and collaborate on moving PHP = forward. I think people might be a lot more willing to work together = for mutual benefit if they were working in the same room rather than on = their own in front of their keyboards. Maybe that would be a way to move forward with some of the log jams = here? Basically an initial meeting and then a plan to do it = periodically in the future (annual or bi-annual?) -Mike= --Apple-Mail=_D3B8CB43-2F55-4E8B-A513-BB26BAC64E5C--