Can there be a final position on this point ? I mean something like an internal or open (whatever) discussion that will conclude with the definitive rules for plugins authors. Today I really don't know anymore how to name my plugin xD
On Jan 8, 2:08 pm, Fabien POTENCIER <[EMAIL PROTECTED] project.com> wrote: > Pierre Joye wrote: > > >>> I think we ask the wrong question. I think the problem is not about > >>> prefixes at all. It's about: > >>> - usefulness > >>> - opensourceness (?) > >>> - quality > >>> - documentation > >>> - commitment (to maintain and evolve the plugin) > >>> - tests > > > All these points are correct (obviously...). However arguing that > > having hundred of different (meaningless) prefix is a very dangerous > > situation and brings nothing but confusions. Indeed we are talking > > about one channel at a time (be the forge or in symfony itself). I > > don't really see why it is so hard to understand. Many projects > > already made this bad experience and they all took the choice of a > > common prefix to avoid naming clashes and other bad side effects. Why > > Symfony simply can't continue on the right way regarding the naming > > convention? > > Ok, I was not clear on my position: Let's keep sf prefix for all plugins. > > > > > -- > > Pierre > >http://blog.thepimp.net|http://www.libgd.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
