I've got two more, which I'll write up on today / tomorrow. Sent from my Nexus One On Nov 15, 2010 8:10 AM, "Lukas Kahwe Smith" <[email protected]> wrote: > > On 12.11.2010, at 10:42, Lukas Kahwe Smith wrote: > >> Hi, >> >> Just a reminder to submit topics for next weeks meeting. >> >> Once again here are the notes from last week: >> http://trac.symfony-project.org/wiki/IRCLogs20101111 >> >> One thing I ask people submitting stories, try to invest a bit of time into the background infos. Make sure that you identify different subtopics and proposals with clear identifiers so that they can be referred to during the IRC meeting. >> >> I will write up some more guidelines and hints as part of the official Symfony2 docs in the coming days. > > > i havent written these guidelines yet. but i wanted to make clear that nobody should keep an important topic for discussion to themselves because they do not have the time or interest to write up a detailed proposal. > > i am also saying this because so far there have not been any proposals sent for this thursday, which makes me wonder if either i scared people off with the above, that people didnt think the meeting is useful, or that simply right now there are no issues to discuss. > > i do see a few topics of relevance personally though: > 1) Console dependency injection: https://github.com/fabpot/symfony/pull/70 > 2) Base form templates adjustment: https://github.com/fabpot/symfony/pull/100 > 3) Allow multiple routing requirement with xml loader: https://github.com/fabpot/symfony/pull/88 > 4) Extension helpers: https://github.com/fabpot/symfony/pull/133 > 5) Security layer and different authentication sources: I think Thibault also identified an issue when using different authentication sources, there was a pull request but it was lost in yesterday's github outage. > 6) Flash messages and i18n: http://groups.google.com/group/symfony-devs/browse_thread/thread/514d9653cf068725/1c4f2753c553cf4b#1c4f2753c553cf4b > > Actually 3) might just need a clarification what was broken with the patch, so that a new patch can be written. > > Anyway, since I proposed these meetings, it kinda feels wrong if I then also dominate the list of topics. > > regards, > Lukas Kahwe Smith > [email protected] > > > > -- > 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 [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > 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 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
