Re: Re: Move internals discussion to a better medium

Step one: Get a proper mail client. In the mail you sent one can't see what's from you and what you actually just quoted. All is marked as quote. E-Mail is great. It is a push service and I as the receiver can handle as it matches my work flow. Applying custom filters, highlighters, have a threaded view or linear. I also have the discussion while offline while traveling etc. There aren't many other system which can handle this amount of participants and discussions in a good way, especially if we don'T want to have a lock in of our process on a specific vendor. Switching mailing list server, if there is any need, is trivial. johannes P.S. sorry or this bad full quote On Sun, 2015-08-02 at 12:38 +0000, Dor Tchizik wrote: > On Sun, Aug 2, 2015 at 3:38 PM Dor Tchizik <dor@tchizik.com> wrote: > > > On Sun, Aug 2, 2015 at 3:32 PM Markus Malkusch <markus@malkusch.de> wrote: > > > >> 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 <news://news.php.net/>? > >> > > > > No threads, no searchability, no ability to respond. > > > > > >> > >> > 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). > > > > > > Like I said, GitHub is an example, the actual medium can be discussed. > > Also, what's being discussed on internals are issues. Definitely. > > > > > >> 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. > >> > > > > "Any developer worth their salt has a GitHub account". Also, disregarding > > the fact that GitHub going loco is not likely (because there are other big > > players on the market), even a privately hosted (but publicly visible) > > issue tracker for PHP, with a modern interface is still infinitely better > > than the mailing list. > > > > > >> > >> > - GitHub issues can reference other issues (currently impossible with > >> > the mailing list > >> > >> Let's reference something then > >> <news:E6.64.22108.E69F7B55@pb1.pair.com> > >> > > > > I don't know how you see it, I got a mailto: link to > > that address. > > > > > >> > >> > - 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. > >> > > > > Perhaps, but an issue tracker gives you that feature for free, and you > > don't need to implement it (good search is hard). > > > > > >> > >> Markus Malkusch > >> > >