Re: [RFC] Policy on 3rd party code

> So banning "full" frameworks is my attempt at steering clear of the appearance of > that kind of favoritism. Showing favoritism for Composer or Xdebug is, well, there's no > competition to complain. PHPUnit is technically not the only testing framework on the market, but it > has north of 90% share (and is used internally by some of the few others). But showing favoritism > between Drupal, Wordpress, TYPO3, Concrete5, and Joomla gets a lot dicier. > I think we are overloading the word "framework" here. I would suggest something along the lines of the following definitions: A Web Application Platform: A fully-functional application written in PHP, often and perhaps exclusively with the purpose of building websites with little to no coding (excluding the notion of custom extensions or plugins to the application). A PHP Framework: A collection of libraries bundled together that, by themselves, are not a functional application but rather as a whole provide the scaffolding to build an application on top of via code. I personally can understand the argument against PHP proper seeming to endorse a Web Application Platform, but I think its entirely reasonable for PHP to internally use A PHP Framework if it happens to make the lives of people easier. Coogle