Capistrano is stable and mature. I can't understand the suggestion that it might die. What could cause that?
I use Capistrano on a daily basis in my paid work and on personal projects. I've invested a lot of time writing Cap tasks. I don't want its behaviour to change and require me to redo that work. With 371618 rubygem downloads from rubyforge to date[1], I suspect there are many others in my position. I've included below a listing of the number of commits per contributor in the git repo. I can't see an *obvious* successor there. I think Jamis would have told us if he had. Rather than decide now which fork people should follow, why don't we take a different approach? Those who are interested in providing gems could make them available under their username on github. Users who feel the need can choose a fork based on merit (and recommendations by people they trust). They could then install an alternative like so: sudo gem uninstall capistrano sudo gem install mbailey-capistrano --source http://gems.github.com gem which capistrano # => /usr/local/lib/ruby/gems/1.8/gems/mbailey-capistrano-2.5.6/lib/capistrano.rb (Note that I don't currently have any intention of maintaining a gem. But you can copy the gemspec from my fork if you want to.) It may well be that mattmatt-capistrano turns out to be the best fork for the most people. But rather than create capistrano-capistrano on github, why not let each fork compete on it's merits. - Mike maculike2:capistrano mbailey$ git log | grep Author | sort | uniq -c | sort -r 460 Author: Jamis Buck <[email protected]> 12 Author: Ryan McGeary <[email protected]> 11 Author: David Heinemeier Hansson <[email protected]> 4 Author: esad <[email protected]> 4 Author: Mathias Meyer <[email protected]> 4 Author: Carlos Kozuszko <[email protected]> 3 Author: Mark Imbriaco <[email protected]> 1 Author: yan <[email protected]> 1 Author: grantr <[email protected]> 1 Author: Wincent Colaiuta <[email protected]> 1 Author: Walter Smith <[email protected]> 1 Author: Tim Harper <[email protected]> 1 Author: Phillip Goldenburg <[email protected]> 1 Author: Paul Paradise <[email protected]> 1 Author: Paul Gross <[email protected]> 1 Author: Mike Bailey <[email protected]> 1 Author: Mark Zuneska, Daniel Berlinger and Evan Closson <[email protected]> 1 Author: Lewis Mackenzie <[email protected]> 1 Author: Kerry Buckley <[email protected]> 1 Author: Jørgen H. Fjeld <[email protected]> 1 Author: Jon Evans <[email protected]> 1 Author: John Trupiano <[email protected]> 1 Author: Jesse Newland <[email protected]> 1 Author: Jeff Forcier <[email protected]> 1 Author: Geoffrey Grosenbach <[email protected]> 1 Author: François Beausoleil <[email protected]> 1 Author: Fabio Akita <[email protected]> 1 Author: David Abdemoulaie <[email protected]> 1 Author: Dave Turnbull <[email protected]> 1 Author: Carlos Kozuszko <[email protected]> 1 Author: Brendan Schwartz <[email protected]> 1 Author: Bob McWhirter <[email protected]> 1 Author: Ben Lavender <[email protected]> 1 Author: Andrew Carter <[email protected]> [1] http://gems.rubyforge.org/stats.html On Thu, Feb 26, 2009 at 3:48 AM, Jonathan Weiss <[email protected]> wrote: > > Cheers, > > > You all probably read the sad news, Jamis is stepping down as the > Capistrano and Net::SSH maintainer. Capistrano and the accompaning tools > are essential to many deployment setups and it would be sad to see > Capistrano die. > > Mathias Meyer and I are quite familiar with the Capistrano code base (we > wrote Webistrano, Macistrano, and a couple of smaller extensions). We > can see ourselves taking over maintainership for Capistrano and Net::S*. > > We already have some small extensions and patches that we could bring in > and would be happy to keep Capistrano alive. > > If you are also interested in continuing the development of Capistrano, > feel free to post here or get in touch with us. > > Jonathan > > -- > Jonathan Weiss > http://blog.innerewut.de > http://twitter.com/jweiss > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
