That was my thought. Have you guys traditionally asked people to maintain separate plugin repos in the past? I'm asking for two reasons:
- The GH account has a pending pull request for a Twitter plugin that I'm thinking about how to integrate. - I've seen community requests for things like Twitter support and I think it'd be nice to provide easy access to it. Would it be worth considering maintaining a cruisecontrol.rb-contrib repository that attempts to aggregate all of the add-ons, or would that just become tricky to maintain from our standpoint? There's a fair amount of infrastructure devoted to this in cruise_plugin.rb but I'm not clear on how much is stuff we've written vs. inherited from Rails' plugin installer, from which it seems (at first glance) to be derived. Either way it would be good to keep a relatively painless add-on process. Cheers, Brian On Sun, Jul 5, 2009 at 12:06 AM, Alexey Verkhovsky<[email protected]> wrote: > On Sat, Jul 4, 2009 at 1:16 PM, Brian Guthrie <[email protected]> wrote: >> >> CCRB follows an include-all-dependencies rule to make setup as simple >> as possible. Just to clarify, does that mean that when we integrate >> (say) a Twitter notification plugin that we also need to add the >> Twitter gem to our list of gem dependencies, and vendorize it >> accordingly? If so that's cool, it just sort of strikes me as odd. Of >> course, the alternative--making the user provide and link their own >> Twitter gem--is potentially a headache. > > I don't think this would be a god idea. You'll soon end up vendorizing > everything and the kitchen sink. Stuff like Twitter plugin is better off as > separate addons. > > -- > Alexey Verkhovsky > http://alex-verkhovsky.blogspot.com/ > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > _______________________________________________ > Cruisecontrolrb-developers mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > > _______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
