Although the plugin author makes effort by packaging and releasing his stuff to the community, not every plugin author will be able to support and maintain his work on the mid or long term. As everyone here knows, the coding part is only a slice in the lifetime of a piece of code, a tiner slice than maintenance part.
Releasing a piece of open source software is a commitment to its users, if you're unable to support and maintain your plugin, then don't release it in the first place. No amount of CI magic beans can substitute for a plugin author who actually looks after his plugin,
I think the community will get more benefits if we think a bit more "global" - plugins are a (big) part of rails, not finding a way to bring love to them is bad for rails itself.
I think that the best option will be for one of the plugin directories to offer CI for plugin authors. -- Cheers Koz _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
