I like the idea of having some sort of a process - it means, as Lukas said, that things are done intentionally, and it can encourage people to solidify their API's, tag, PHPDoc etc. Of course, we're all busy, so organizing that is another story.
But all of the above is really important for *all* quality bundles, regardless of whether or not their in the SE. So, perhaps that's something we think about with respect to the future symfony2 "marketplace" (or whatever the final main location for Symfony2 bundles ends up being). Obviously, that type of system was built into Symfony2Bundles.org, but it could be taken further in the future to really encourage high quality bundles. Per the SE, I'm +1 for JMSDebuggingBundle, at least in theory. I have to admin that I haven't used it in awhile and followed along with its development, but this would be a great addition. For those of you that aren't familiar with the bundle, it allows you to "ask for help" on an exception screen. Your exception message is transmitted back to an external server where an algorithm attempts to return links (official docs, blog posts, anything) that might help you find the root of your problem. Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Mon, May 16, 2011 at 10:15 AM, Gediminas Morkevicius < [email protected]> wrote: > I personally think that, what SE contains is enough for SE. Lets be honest, > FOSUserBundle looks more like FOSUserFrameworkBundle I think security > component is handling a half features allready.. > > > On Mon, May 16, 2011 at 5:07 PM, Lukas Kahwe Smith <[email protected]>wrote: > >> Hi, >> >> Back when the Standard Edition was first created it featured the >> FrameworkExtraBundle which quickly let to the question what should be >> bundled and how do we decide this [1]. Back then we decided to delay the >> topic until we are further along. I think the time has come to revisit this >> topic as it popup up in the PR for adding the JMSDebuggingBundle [2] >> >> Obvious contenders to me are: >> - JMSDebuggingBundle >> - FOSRestBundle >> >> Less obvious: >> - FOSUserBundle >> >> Probably not do 2.0: >> - some admin bundle >> >> I think we should have some sort of process where we basically elect >> Bundles as candidates and give some general feedback what sort of >> improvements we expect before the Bundle can be made part of SE. The logic >> being that for a single developer it will be hard to meet all the >> requirements especially if that developer isnt certain that the Bundle will >> actually be added (for example I would say that all such Bundles need to use >> reST for documentation, which is not the case for most Bundles out there, so >> the docs can be good just not in the right format). Furthermore this will >> help attract other developers to help out to round off the docs/tests and >> sanity check the API etc. Finally since this is just about electing a >> candidate if the expectations are not met the Bundle will simply not be >> added. >> >> regards, >> Lukas Kahwe Smith >> [email protected] >> >> [1] http://trac.symfony-project.org/wiki/IRCLogs20110310 >> [2] https://github.com/symfony/symfony-standard/pull/53 >> >> -- >> 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 > -- 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
