I'm conducting an analysis of major PHP and Python frameworks and CMS systems, and I would like someone who is an expert in Symfony to complete the attached spreadsheet as completely as possible. Please note that I am looking for Pros *and* Cons, so even if you love Symfony, please be as objective and critical as you can. If it's great in some area, then give it a 5 and describe why it's great. If it could be better, give it a 2 or 3 (or 1 if horrible) and describe why it could be better, etc. I really want an honest analysis. Please use Microsoft Excel. And please note that I need this by tomorrow. If you're very familiar with Symfony, it shouldn't take you more than an hour or so. The attached spreadsheet shows a partial example of what is needed using the PHP-based CMS Drupal (you should delete the grid contents and fill it in yourself, of course).
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables):
a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Symfony for PHP, Excel