Comments on: WordPress Core vs Canonical Plugins http://bluedogwebservices.com/wordpress-core-canonical-plugins/?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-core-canonical-plugins BlueDog Web Services Thu, 26 Jan 2012 21:06:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Peter Kahoun http://bluedogwebservices.com/wordpress-core-canonical-plugins/#comment-475 Peter Kahoun Sat, 21 Nov 2009 20:34:32 +0000 http://bluedogwebservices.com/?p=429#comment-475 I also think including (or promoting) feature-packages as separable plugins is the best way to go. (Other option is not to include such plugins into the main wp package but to promote them and offer them to simple automatic installation on the plugins page in administration.) Actually, it's hard for me to believe WP could turn to approach like this. I also think including (or promoting) feature-packages as separable plugins is the best way to go. (Other option is not to include such plugins into the main wp package but to promote them and offer them to simple automatic installation on the plugins page in administration.) Actually, it’s hard for me to believe WP could turn to approach like this.

]]> By: Utahcon http://bluedogwebservices.com/wordpress-core-canonical-plugins/#comment-474 Utahcon Tue, 14 Jul 2009 17:46:51 +0000 http://bluedogwebservices.com/?p=429#comment-474 One of the greatest advantages of WordPress is the fact that it is so lightweight and open. This is the reason there are so many plugins. By leaving the features to the users and community the WordPress Dev Team can focus on making the core product more reliable, secure, and faster. The users and community can then create a plugin to do anything they would like with the assurance that they don't have to accept something as, this is the way it is. I am all for WordPress sponsoring plugins as the semi-official plugins. Meaning these are the plugins most people use, and we will spot check that they still work, but you don't want the Core Dev Team spending more time making sure they don't break plugins. That is the job of the developer of the plugin. Automattic has always been open about their process of development and generous in getting betas and RCs available so that developers can in fact test their own plugins against the latest and greatest architecture. Furthermore the WordPress Dev Team should focus on not breaking current functionality, which would alleviate a lot of the breaking plugins. Great article. One of the greatest advantages of WordPress is the fact that it is so lightweight and open. This is the reason there are so many plugins. By leaving the features to the users and community the WordPress Dev Team can focus on making the core product more reliable, secure, and faster. The users and community can then create a plugin to do anything they would like with the assurance that they don’t have to accept something as, this is the way it is.

I am all for WordPress sponsoring plugins as the semi-official plugins. Meaning these are the plugins most people use, and we will spot check that they still work, but you don’t want the Core Dev Team spending more time making sure they don’t break plugins. That is the job of the developer of the plugin. Automattic has always been open about their process of development and generous in getting betas and RCs available so that developers can in fact test their own plugins against the latest and greatest architecture.

Furthermore the WordPress Dev Team should focus on not breaking current functionality, which would alleviate a lot of the breaking plugins.

Great article.

]]>