CUNY Academic Commons

Sorry if you think of me as a bug-tracker tyrant. My real concern is less about whether tickets and requests are in a one-to-one relationship, and more about adding new plugins just because they are neat. As I have said before, adding a plugin to the site essentially means that our team has adopted the plugin, once our users start activating it.

As for these:
- The G+1 and FB gallery plugins seem fine.
- Ultimate Follow Me - Do we already have one of these kinds of plugins? In some cases there is an argument for having more than one member of a class of plugins, but probably not in this case.
- The Google Maps plugin looks neat, though again I would like to know what other GMaps plugins we're running, and whether (hopefully) this would allow us to get rid of one or more of them. They are notoriously buggy.
- Spam Free WordPress - The author's description is a bit obnoxious, but the plugin looks fine.
- iFrame - I say no. First, there are security issues with allowing arbitrary iframes to be embedded. Second, we already have methods for safely embedding many kinds of content, making this plugin redundant.

Thanks, Boone. And I don't think of you as a tyrant. I probably should have used either the "Documents" portion of this site or Basecamp for this conversation. Tickets have very practical purposes in our development workflow and I'm keenly aware that the proper use of them enables you to organize your work.

I see your point about adopting plugins, but I've also found our users to be pretty understanding when certain plugins no longer work. I'm not sure that we can/should commit to supporting all plugins/plugin functionalities without caveats.

Having said that, I'm completely on board with your desire to remove reduncancies. At the same time, I'd just like us to keep our eye out for new plugins that might be of interest.

I will add separate tickets for G+1, FB Galleries, and Spam Free WP.