Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41602 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20855 invoked from network); 31 Oct 2008 20:13:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Oct 2008 20:13:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=parasane@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=parasane@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.228 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: parasane@gmail.com X-Host-Fingerprint: 209.85.198.228 rv-out-0506.google.com Received: from [209.85.198.228] ([209.85.198.228:32742] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 65/5A-00587-8F66B094 for ; Fri, 31 Oct 2008 15:13:46 -0500 Received: by rv-out-0506.google.com with SMTP id g37so1434875rvb.23 for ; Fri, 31 Oct 2008 13:13:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=x5grXHVkpawBxJ83M0DFry7XOqZIIdSFJGSqvtEdS/g=; b=uCFZgfwo9wkYPt8O6osSlLiH9IG1mIXdR5PJ8ibtDh2j7oJ3s4TYKofoW7gK3jAG+z vd/SQE7j+/riQU4Cn3BdzhcXOJjilGKiAU7mZltOnDNISalrIExubNMWgJJ9N8uRUfwU WUu4nM4s5T8BzPRgxULVF+wW0o0u64SxBcVYI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=nWVI/HhdX2Mm/iPrvB6EFPUwB6/pHdlxRDo5LfXaWh4JgRKzoxlTp4h7ENwYG6zi6T NpIhmGgx2JeDG6O/+AcG1rUy7HQOxHBfBVXkHPaaR0sCCUILam5sGs7gsIaIsVyCMHQ9 QAWRIduQlnBmquY0v5Imk1vw0A3bAGJtqJuC8= Received: by 10.141.4.3 with SMTP id g3mr6909191rvi.116.1225484021758; Fri, 31 Oct 2008 13:13:41 -0700 (PDT) Received: by 10.141.190.3 with HTTP; Fri, 31 Oct 2008 13:13:41 -0700 (PDT) Message-ID: Date: Fri, 31 Oct 2008 15:13:41 -0500 Sender: parasane@gmail.com To: "Rasmus Lerdorf" Cc: "Hannes Magnusson" , "Lukas Kahwe Smith" , "PHP Development" In-Reply-To: <490B639A.8050905@lerdorf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2077BA98-A58A-4EBD-8088-413654E878BC@pooteeweet.org> <490B5CC5.8040808@lerdorf.com> <7f3ed2c30810311252x7c4f1cb9ydd41a273f4089311@mail.gmail.com> <490B639A.8050905@lerdorf.com> X-Google-Sender-Auth: 8da7257839091350 Subject: Re: [PHP-DEV] keeping traffic on this list manageable From: danbrown@php.net ("Daniel Brown") On Fri, Oct 31, 2008 at 2:59 PM, Rasmus Lerdorf wrote: > > This is the same as just making internals@ read-only. Once we have an > internals-core, many core people will just unsubscribe from the internals > list. I know I probably would. And once the core developers no longer read > it, it becomes php-general2 and it ends up excluding people from the > development process. I'd also be concerned about patch submissions. Would we leave that on internals@ still, or create yet another list, patches@? -- http://www.parasane.net/ daniel.brown@parasane.net || danbrown@php.net Ask me about our current hosting/dedicated server deals!