On 2 August 2015 15:26:00 BST, Niklas Keller <m...@kelunik.com> 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] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
