I would like to keep the current namespaces. Symfony is composed of components and bundles. It makes sense to categorize them accordingly.
Namespaces are a case-by-case thing. If we're violating a best practice by including a Bundle namespace, the best practice should be changed. k On Feb 5, 2011, at 6:28 AM, Bulat Shakirzyanov <[email protected]> wrote: I agree with Benjamin, think Doctrine\Common and Doctrine\ORM On Sat, Feb 5, 2011 at 9:18 AM, Benjamin Eberlei <[email protected]>wrote: > I disagree that we don't follow the best practice. Bundle is actually the > Category namespace. > > That separates the code (component vs bundle) much better. > > greetings, > Benjamin > > On Sat, 05 Feb 2011 04:46:15 +0100 > Fabien Potencier <[email protected]> wrote: > > > Hi all, > > > > Some time ago, we decided the best practice for bundle namespaces: > > > > Vendor\NameBundle > > > > like in: > > > > Sensio\BlogBundle > > > > But the Symfony bundles are different as they still have the Bundle\ > > category: > > > > Symfony\Bundle\FrameworkBundle > > > > The more I think about it, the more I think this is not a good idea: > > > > * First, because Symfony itself does not respect its best practices, > > which is weird; > > > > * Then, because at some point, each bundle will be hosted in its own > > repository; so the need to differentiate between a bundle and a > > component will be less important. My idea is for the symfony repository > > to only contain the components and each bundle will have its own > repository. > > > > So, what about removing the Bundle\ and Component\ categories altogether? > > > > Symfony\FrameworkBundle -> dedicated repository > > Symfony\DoctrineBundle -> dedicated repository > > > > Symfony\Form -> in the components repository (the current symfony one) > > Symfony\Security -> in the components repository > > ... > > > > I was not in favor of dropping the Bundle\ category but now that the > > decision has been taken, I think we should remove it everywhere. > > > > Fabien > > > > -- > > Fabien Potencier > > Sensio CEO - Symfony lead developer > > sensiolabs.com | symfony-project.org | fabien.potencier.org > > Tél: +33 1 40 99 80 80 > > > > -- > > 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]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- *Bulat Shakirzyanov* | Software Alchemist *a: *about.me/avalanche123 *e:* [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 -- 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
