+1: I am for closing this list down as well. Issues that are not suited to be discussed in github issues can use the "Users mailing list" (http://symfony.com/community)
On Dec 17, 2012, at 10:11 AM, Bernhard Schussek wrote: > +1 > > -- > Bernhard Schussek > Blog: http://webmozarts.com > Twitter: http://twitter.com/webmozart > > > > 2012/12/17 Fabien Potencier <fabien.potenc...@gmail.com> > On 12/17/12 3:48 PM, Larry Garfield wrote: > The main advantage of a mailing list is that it is push based. You can > reach/notify everyone "relevant" at once (for some definition of relevant) > via email more effectively than any other medium. That of course has scaling > issues, but if we're gong to close the list please make sure that there is a > full replacement and that includes a push mechanism. > > I agree with you but the reality is that today, most discussions happen on > Github anyway. So, this mailing-list is already by-passed most of the time. > Keeping it open gives a false sense of being at the right place for following > technical discussions and decisions. > > Fabien > > > -- Larry Garfield > > Fabien Potencier <fabien.potenc...@gmail.com> wrote: > > Hi all, > > As you might have noticed, the number of discussions on this > mailing-list dramatically dropped since we switched to Github. In fact, > most technical discussions now happen on Github (issues or PRs). And > this is probably for the best as we can have code highlighting, email > notifications, ... > > So, I propose to close this mailing-list and make Github our primary and > only way to discuss technical issues. > > Fabien > > -- > Fabien Potencier > SensioLabs CEO - Symfony lead developer > sensiolabs.com | symfony.com | fabien.potencier.org > +33 1 40 99 80 80 > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > > > > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > > > > > -- > -- > If you want to report a vulnerability issue on Symfony, please read the > procedure on http://symfony.com/security > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to symfony-devs@googlegroups.com > To unsubscribe from this group, send email to > symfony-devs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > > -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
