Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87520 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76755 invoked from network); 2 Aug 2015 16:57:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Aug 2015 16:57:59 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.180 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.180 mail-wi0-f180.google.com Received: from [209.85.212.180] ([209.85.212.180:33978] helo=mail-wi0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 62/72-55344-61C4EB55 for ; Sun, 02 Aug 2015 12:57:59 -0400 Received: by wibud3 with SMTP id ud3so109479472wib.1 for ; Sun, 02 Aug 2015 09:57:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type:subject:from:date:cc :message-id; bh=Spzj0Qx2+TWyKN/AYUQfLzh9jojoY+YH9/Ji7ZIoprI=; b=ohgfMK0tQHfKtzBZCV4PCKDrunYk81sHLheT9SYxWJcUW4+g2U9VsMOseH9F0Cj1Sk yCtlxJNR7t8EqvCzqJ7KdxJkSHQJsWpNa7+oO/E52fXSmwWx4S3ukcN345/enneZJ/eT +Qd5fyo++xI6CQHIj7gDHZu9sq20yEQL8lRsxNRDMfZRXXW3BHDuwxxox6Lb038lvT0O nwkBE9MiCnyn4ljxMnOFODcxcYLtUKphZOlB4F4E/l3xsmrH9Am072VGK18nXLwcnvou uWPIgd/jJ3E3yho31i7Vi3T6hlNay7NtNo2fj0Pn7yjhITDujfMz9yRnlXhMxIX0C9AK nsgw== X-Received: by 10.180.215.8 with SMTP id oe8mr11253827wic.0.1438534675185; Sun, 02 Aug 2015 09:57:55 -0700 (PDT) Received: from [192.168.0.6] (cpc68956-brig15-2-0-cust215.3-3.cable.virginm.net. [82.6.24.216]) by smtp.gmail.com with ESMTPSA id lm16sm9020512wic.18.2015.08.02.09.57.53 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Aug 2015 09:57:54 -0700 (PDT) User-Agent: K-9 Mail for Android In-Reply-To: References: <37DC5EF1-35B4-45A7-9065-5A7866336B06@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Date: Sun, 02 Aug 2015 17:57:41 +0100 CC: PHP Internals Message-ID: <69EAE189-5095-45B3-93D6-DFDE4A05509A@gmail.com> Subject: Re: [PHP-DEV] Re: Move internals discussion to a better medium From: rowan.collins@gmail.com (Rowan Collins) On 2 August 2015 15:26:00 BST, Niklas Keller wrote: >How about a tool like Phabricator? I've never used Phabricator, but it does look like a nice project management tool. I first heard of it in reference to Wikimedia migrating a whole bunch of teams to it as a unified tool. However, it's perhaps relevant to note that I can see nothing in their migration plans that implies the mediawiki-l and wikitech-l mailing lists will be retired, suggesting that they still see a use for good old-fashioned e-mail groups. I think part of the problem with concentrating on how easy it is to filter down to specific tasks is that what new users actually need is the opposite: an overview of what's going on, and a place where broad topics won't be closed as an Invalid Task. That then serves as an entry into more specific task-based activity. If every thread on PHP Internals was converted to a tree of linked Issues in a database of thousands of threads, how would you know where to begin? And how would busy core devs avoid missing an important discussion happening on an Issue which mutates from a user's bug report to a breaking change in the language? I'm not saying what we have now is perfect for that, but a post to Internals can draw attention to the one bug in hundreds where that has happened, and allow the wider issue to be discussed separately from the line-by-line code review of a patch. Regards, -- Rowan Collins [IMSoP]