Updating existing plugin packaging scripts

[var-foo]

It looks like the make_package.* files are going to be a bit out of date since we moved to git. It looks for .svn files to clean up before it zips the plugin. We should probably update that to delete the .git folder instead.

Really, it looks like we have a lot of work to do here, but I'm not sure what the best approach is at this point. I think it would be great to extend the plugin installer to be able to just clone the plugin right off of this repository, or maybe break each plugin out into its own repo as mentioned in #3

[var-foo]

I'm not totally sure because I need to do some more research, but at this point, it looks like we can use composer to import plugins. This is going to affect the plugin ecosystem from top to bottom. Does anyone have anything to say about this?

[scottux]

The plugin system has always seemed a bit 'much' - typically we just pull in a class file and an example, although some are a bit more involved with js/css/image assets. If they are to continue including examples - we may have to integrate their documentation and examples somewhere.

[var-foo]

I think they should include their own examples. I wouldn't want to have to edit 2 different repositories just to get a plugin out the door.

Maybe we can do something with the install that puts a link in the examples index, but we can keep the example files themselves inside the plugin folder. I think it would be beneficial to try to keep the plugins as independent as possible.

[olegabr]

plugin examples can be incorporated programmatically, by scanning the plugins directory for exmples pattern.