I would suggest that plugins are the best place for all additional development of symfony. That way the core stays as lightweight as possible and users can choose what elements suite their development practices. For exmaple the control pannel is now a plugin and the audit could be part of this.
I think that some form of continuous integration system would also be useful? Ali On 05/09/07, Kiril Angov <[EMAIL PROTECTED]> wrote: > > > Now when I think about it, should this be part of symfony itself? A > symfony tasks that will be easy to run as 'symfony codelint' or > something along those lines. Do people think this is important > especially for larger teams where you want to be sure standards are > being followed? > > Kupo > > Alexander Deruwe wrote: > > On 29 Aug 2007, at 20:29, Tristan Rivoallan wrote: > > > >> On 8/29/07, Jack Bates <[EMAIL PROTECTED]> wrote: > >> > >>> I wonder if any code already exists for checking symfony's code > >>> standards? > >>> > >> pear's codesniffer can provide a very good basis for implementing > >> this. > >> > >> http://pear.php.net/package/PHP_CodeSniffer > >> > > > > I'm using symfony's coding standards for my project too. Jack, are > > you working on this? If not, I might put some extra time in this - > > but I'd hate to be duplicating efforts. > > > > Perhaps someone already has symfony coding standard Sniffs? > > > > > > Alexander > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
