Hi All, I'm a little suspect of the Webistrano/Macistrano guys taking over development, as I feel particularly that Webistrano limits the capabilities of capistrano and limits it usefulness for non-rails projects. Whilst there's still a market for simple-one-push rails deploys, with accountability; But I would be hoping for some kind of reassurance that Web/Macistrano would remain separate projects, and would not affect capistrano in any way.
I do feel that someone that knows the Capistrano internals should take over, I'd have volunteered, except my skills lay in using Capistrano, for complex deploys; not particularly in changing internals, and fixing bugs, and those sorts of things. Whoever takes it over should be prepared to start living in IRC, and start up a drive to get documentation written... and try and drive it as *the* way to handle deployment. Even since Net::SSH-Multi - my interest in capistrano has slipped a little, as for the most part, my deploys aren't very compatible with the capistrano notion of a single app over a few roles of servers. I'm looking forward to whatever happens with Capistrano, Jamis has left us with an exceptional bit of code, we owe it to him to make the right decision about where to take it next. I will be forking copies of the libraries on Github, to make some changes to the way cap logs out to the screen, some things that have come up from time to time on the mailing list, about problems with how, and where capistrano logs, as well as some stuff I want to do with the output to the screen (does that count as logging?) Before we all fork-off and make our own changes, I fear that there will be no go-to-guy for a 'right' version of capistrano that scares me a lot, as it raises the barrier to entry far higher than it needs to be... (will_paginate... Vs. mislavs_will_paginate anyone?) - Lee 2009/2/26 Simone Carletti <[email protected]> > Thanks for your feedback Karel! > > I agree that Capistrano needs more documentation and I'm happy to hear > someone else is available to contribute. > I must confess I didn't notice your message before, I'm going to post a > reply at http://groups.google.com/group/capistrano/msg/654e5e84d45f9098 > > Talking about the future of maintainership, I'm going to contact Jonathan > directly to accelerate the process. > > It would be wonderful to get a feedback from Jamis about this topic. > I'm a bit concerned about how we can carry on development without the need > to force people to change gem name or repository. > > -- Simone > > > On Thu, Feb 26, 2009 at 11:36 AM, Karel Minarik > <[email protected]>wrote: > >> Karel >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
