Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87502 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22808 invoked from network); 2 Aug 2015 12:32:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Aug 2015 12:32:07 -0000 X-Host-Fingerprint: 78.52.11.62 f052011062.adsl.alicedsl.de Received: from [78.52.11.62] ([78.52.11.62:23200] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/E0-09373-6CD0EB55 for ; Sun, 02 Aug 2015 08:32:07 -0400 Message-ID: To: internals@lists.php.net,Dor Tchizik Content-Type: text/plain; charset="ISO-8859-1" Date: Sun, 02 Aug 2015 14:32:01 +0200 User-Agent: KNode/4.14.8 Content-Transfer-Encoding: 7Bit References: Lines: 26 MIME-Version: 1.0 X-Posted-By: 78.52.11.62 Subject: Re: Move internals discussion to a better medium From: markus@malkusch.de (Markus Malkusch) Dor Tchizik wrote: > Currently, PHP discussions are held on the various mailing lists, managed > by an old mailing list system, without any proper alternative interface to > follow and respond outside of mailing. What wrong with ? > I propose that internals discussion to be moved (eventually entirely) to a > different medium, where the example I have in mind is GitHub issues That's an issue tracker (and to be honest not one of the best). I don't see any benefit there. Furthermore participating requires a github.com registration whereas this medium is free to use. And you know what happend to the last big player (namely sourceforge)? Github can go loko as well. > - GitHub issues can reference other issues (currently impossible with > the mailing list Let's reference something then > - GitHub issues are searchable. You have tags. Newsserver are searchable as well. At least you could wrap the current infrastructure easily into a search engine. Markus Malkusch