Sorry - I didn't know if we should place topics here or if pending symfony-dev topics would count. Here is what's on my mind:
* composer: I have used it, I don't totally have my mind wrapped around it, but it's cool and - as Fabien said - this is a problem that I think really needs to be solved for 2.1. As an added bonus, ZF2 is tackling this problem right now as well, so if there were ever a possibility to work together, we have half a chance. So, I guess the "discussion" would be putting together some sort of plan to get the distribution problem tackled. * http://groups.google.com/group/symfony-devs/browse_thread/thread/eed0feb5650d27d3- No responses on it yet, but it's a simplification that I'd like to see for 2.1 Cheers! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Tue, Sep 13, 2011 at 8:45 AM, Christophe COEVOET <s...@notk.org> wrote: > Le 13/09/2011 15:37, Lukas Kahwe Smith a écrit : > > On Sep 10, 2011, at 09:14 , Lukas Kahwe Smith wrote: >> >> On Sep 9, 2011, at 14:48 , Fabien Potencier wrote: >>> >>> +1 for IRC meetings every other week. >>>> >>> >>> ok .. then lets get back into the routine next thrusday: >>> http://symfony.com/doc/**current/contributing/**community/irc.html<http://symfony.com/doc/current/contributing/community/irc.html> >>> >>> please send in topic proposals >>> >> >> really? >> >> nobody has a topic they want to discuss at the IRC meeting next thursday? >> >> regards, >> Lukas Kahwe Smith >> m...@pooteeweet.org >> >> >> >> The config component. There is a pending PR adding support for extra > info. I reviewed it again one week ago and asked for others to provide their > feedback but there was no answer so the IRC meeting could be a good place: > https://github.com/symfony/**symfony/pull/1099<https://github.com/symfony/symfony/pull/1099> > > Another point: the way we go to 2.1 about pending PRs. I reviewed most of > them a week ago asking for Fabien's review for a bunch of them, and for > changes for some others. Most of them are not merged yet so there should be > a discussion about their status (or about the way we decide about their > status). > > Note that I will probably be a bit late for the meeting. > > -- > Christophe | Stof > > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > 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+unsubscribe@**googlegroups.com<symfony-devs%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/**group/symfony-devs?hl=en<http://groups.google.com/group/symfony-devs?hl=en> > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
