Well, what worries me is that someone will take over Cap from Jamis - lots of someones. There's nothing to prevent many people from forking the code. However, at that point we'll be choosing between abc_capistrano, def_capistrano, xyz_capistrano, etc. Unfortunately, Jamis didn't designate anyone to take over for him so I think there will be many people willing to do the job but no one overseeing the effort. Seems like the situation is pretty ripe for chaos to me. It would be OK for some open source projects but Capistrano is just too important for this to happen. Of course, there's no way to prevent it. In the meantime from the users perspective we'll have no way of knowing which fork of Capistrano is the "good" fork...
I did try checking out Vlad but unfortunately all of the tutorials, faqs, migration from Capistrano docs etc give 404's when you try to access them from http://rubyhitsquad.com/Vlad_the_Deployer.html. So... I don't know... Thanks, Ken On Feb 26, 2009, at 12:19 PM, Patrick Crowley wrote: > > I think we'll be fine. :) > > Someone will probably take over Cap from Jamis. And Vlad is a good > alternative if that doesn't happen or Cap gets worse over time. > > -- Patrick > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
