wp-cli/wp-cli — pull request #230 by scribu (2012-12-03 16:54:42+00:00)
Title: Future of community commands

The original usecase for community commands, as I understand it, went something like this:

> Sally uses plugin X and would love for that plugin to implement a wp-cli command. But, instead of waiting for the plugin author to do that, he can implement it herself and get it bundled into wp-cli as a community command.

Therefore, ideally, the list would be empty right now, as each command would have moved into it's respective plugin.

The list of community commands has not grown or shrunk at all since the very beginning of wp-cli, which is why I'm bringing the approach into question. On the other hand, maybe wp-cli doesn't have enough clout yet.

One idea I had was to move the community commands into a separate repo, which users could install separately.

Here are a few examples of other commands being packaged as standalone plugins (they don't offer anything else besides the wp-cli commands):

* [humanmade/hm-dev](https://github.com/humanmade/hm-dev/blob/master/hm-dev.plugin.php)
* [linepress/wp-cli-scaffold](https://github.com/linepress/wp-cli-scaffold/blob/master/index.php)