Hi, So we had our first meeting: http://doodle.com/4cnzme7xys3ay53w
Logs: http://trac.symfony-project.org/wiki/Symfony2IRCMeetingLogs 1) IRC meeting process We agreed that the doodle URL to vote on the agenda priorities will not be published until after the proposal phase has closed 24 hours before the meeting. Furthermore it was decided to add a section to the official manual with some instructions on the meetings. Lukas volunteered to take care of that. 2) Handling different output formats The general consensus was to not add "context" support to the DIC and instead look towards finding best practices that Bundle authors can follow to ensure that their controllers are flexible enough to handle different output formats. Jordi offered to write a proof of concept until next week to "a view-class best practice integrated at the framework level so the best practice is easier to implement and follow". One major concern by Fabien was to not complicate things for beginners. Furthermore it was stated that there is a need to expand the documentation on how to define and use custom view's (volunteers needed http://trac.symfony-project.org/ticket/9245). Finally there is a need to define additional view's to handle JSON/XML/etc response types to be added to core (volunteers needed http://trac.symfony-project.org/ticket/9246, http://trac.symfony-project.org/ticket/9247). 3) Security Component It was decided to "move listeners with parameters to non-shared services" (volunteers needed http://trac.symfony-project.org/ticket/9248). Also "adding a way to add listeners in between of existing ones" was considered to be a useful feature (volunteers needed http://trac.symfony-project.org/ticket/9249). Finally it was proposed to "start getting together a list of events and default listeners on it", for which it was suggested to check Spring (volunteers needed http://trac.symfony-project.org/ticket/9250). 4) Default config format The general consensus was that having a mix of different formats wasn't necessarily bad and that XML is easier to read for DIC configs, but that YAML should be the recommended for app level configuration. It was also agreed that there should still be made some effort towards enabling authors to easily validate Extension configurations (volunteers needed http://trac.symfony-project.org/ticket/9251). Jordi offered to convert a complex DIC config in order to illustrate if in fact complex DIC configurations are really harder to read in YAML. Finally it was said that it would make sense to invest in conversion tools to make it easier for people to migrate provided configurations to another format (volunteers needed http://trac.symfony-project.org/ticket/9252). Please expand in case I missed something (especially the tickets could use some more explanations). This is a lot more tedious than I thought :) 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] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
