Robert, this is why important discussions need to be covered in the weekly
reports. Also, you're not describing the status quo. The ML currently isn't
being used anymore.

--
Bernhard Schussek
Blog: http://webmozarts.com
Twitter: http://twitter.com/webmozart


2012/12/17 Robert Hafner <ted...@tedivm.com>

> I think closing this mailing list will make it that much harder for people
> who aren't part of the "inner circle" or the dedicated developers to
> actually contribute to the project. Github doesn't send out emails to
> everyone over every issue, requiring anyone who wants to help to constantly
> check the website for new issues and pull requests, and doesn't make it
> very clear where certain issues will end up. There have been a few cases
> where issues have been brought up here where I felt that really helped- the
> technical discussion still happened on Github, but attention was brought to
> those issues from here.
>
> This list may not be ideal, but I think shutting it down would be a sign
> that outside contributions are not as encouraged.
>
> -1 (assuming I get a vote, not really sure how that works).
>
> Robert
>
>
> On Dec 17, 2012, at 6:25 AM, 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


Reply via email to