Code discussion in PRs is fine. Architecture/big picture/planning
discussion doesn't really fit there. It doesn't really fit anywhere
once the volume gets past a certain point. We ran into the same problem
in Drupal; we don't have a solution yet. It will suck either way. :-)
On 01/19/2013 02:30 PM, Lukas Kahwe Smith wrote:
Ahoi,
in general i prefer discussions in PRs. imho less bikeshedding, more code.
however yes if this list would actually be used more actively and people would
indeed reply on here, then there would be no reason to close this list.
regards,
Lukas
On 19.01.2013, at 20:58, Thomas Lundquist <thoma...@redpill-linpro.com> wrote:
On Sat, Jan 19, 2013 at 08:37:02PM +0100, Jordi Boggiano wrote:
On the other hand, I do read this low traffic list, and I would be quite
happy if actual dev *discussions* happened here rather than on github.
Amen to that.
Maybe what we need to do instead of closing the ML is to close all
issues that are not about bugs or clearly defined feature requests and
redirect here if they are likely to require a discussion.
And that.
Thomas.
--
--
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
