As a plugin author, you can deprecate your plugins (in the metadata section of the admin tab). You should deprecate your plugin when:
You can also add a deprecation message that will be appended to the default deprecation message. For instance if you deprecate a plugin because another one is better, you can redirect people to the new plugin: "Use the FooPlugin instead."
A deprecated plugin is still listed on the symfony website, and people can still download and install it.
Well, of course, we built Symfony Experts with Symfony http://www.Symfonyexperts.com/. When I say “we”, I mean myself and Darren Hoyt. Darren is the most talented graphic designer and usability expert that I have ever worked with. We have worked for various entrepreneurs since 2005, though this was the first time we were working on our own project, and free to do whatever we wanted. I think the results have been good so far.
We are building out a whole series of paid question and answer sites, all of them linked from Codewi.se http://codewi.se/. Symfony has been a fantastic framework for these projects. It allows for rapid iteration. We constantly get feedback from our users, and we constantly make changes to our sites, based on that feedback. Many of these suggestions cause us to make changes to the schema of our databases. Symfony helps us keep these changes well organized and structured: we write a database migration, we change schema.yml, and we regenerate our model classes. Think about the alternatives. If we were using one of the heavy Java frameworks, we’d have to tweak a dozen XML files, so every change to the database would be a royal pain. Or, on the other side of things, if we used no framework at all, our code would be an unholy mess of SQL that was constantly in transition. Symfony gives us the perfect balance of flexibility and structure.
The repository of plugins has become fairly rich and allows us to build simple sites quickly and easily. The E-Society http://www.theesociety.org/ would be an example. Here we built an online social network in a few weeks, using plugins to manage such things as users, and images, and all the files that the users might upload.
Mostly I’ve used MySql with Symfony. In terms of plugins, we use several, including:
Plus some others that I can not think of right now. sfGuardUser is really ingeniously done. I’ve yet to find a situation where its user model could not be made to handle the needed permissions.
We want to do what we can to provide financial support to the many wonderful developers who create these plugins, so we encourage them to sign up to receive donations from our site: http://www.Symfonyexperts.com/support_open_source/index
As our site grows, I hope it can become a source of useful funding for plugins.
Mostly I’ve used Propel as the ORM. It was the official Symfony ORM back in early 2008, when I started using Symfony. Of course, I look forward to switching to Doctrine, now that Doctrine is the official ORM.