I agree, I am going to stay current with documentation, and use this time to familiaris myself with the core, I'd love to take over having cut my teeth supporting in IRC (which I will continue to do)
I'm talking with Jamis now about taking over the capify site, so I can manage that aspect of it... I'll continue to host it as the go-to place, and whatever happens, I will be inviting those in control of the project (and/or its forks) to document & blog about it there... for a start i'm going to clone the existing site, and template to a wordpress blog, as its easy to setup, and my hosting is php-centric. I would prefer that a simple "gem install capistrano" is the way to go - for now, with the latest patches, I don't think that there's a need to fork it, and start messing with it yet, there actually isn't anything wrong with it... if Jamis could perhaps invite a couple of us as collaborators on GitHub, so we can control the main gem release, that would be ideal... I wouldn't mind access to do that, or at least to accept pull requests on behalf of the community... This thread is talking a lot of sense, and it really is up to anyone that wants to to step up and make some changes, I've actually recently being working with xmpp4r - and found their site to be a really valuable resource, I think with Capistrano on the verge of forking into a few spin-offs or otherwise... we could learn something from the information provided on their site... http://home.gna.org/xmpp4r/ I'm still hosting a poll about what we'd like for Capistrano on my blog... http://lee.hambley.name/2009/02/capistrano-feature-request-poll If you have an interest, please - I invite you to cast a vote. It is as much for me, and the things I plan to work on so that I can get to know the core better as for grand-plans-for-Capistrano. Please, continue to discuss, I think we're airing a lot of dirty laundry here and still making good plans for the future of the project. - Lee 2009/2/26 eibhinn <[email protected]> > > As another non-rails capistrano user, keeping it a flexible > commandline > tool is important. Since that seems to be understood, I'm all for > Mathias > and Jonathan stepping up. > > Git forks are great for experimentation, but `gem install capistrano` > better know where to go or we'll lose lots of newcomers. > > -- > Andy > > On Feb 26, 4:38 am, Mathias Meyer <[email protected]> wrote: > > On 26.02.2009, at 12:55, Lee Hambley wrote: > > > > > > > > > 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. > > > > I can understand your concerns, but it is not our intention to take > > Capistrano and replace it with a combination of Webistrano and > > Macistrano. I'm fond of both, but I regularly use just Capistrano > > myself, and work on lots of projects that use Capistrano in ways I > > hadn't imagined before, and that's totally cool. > > > > Capistrano will always be Capistrano, your one-stop deployment command > > line tool, everything else is more like an ecosystem surrounding > > Capistrano. We certainly have ideas where we'd like to take a > > Capistrano 3, but it will not be a big union of a web gui and a > > desktop tool. It will still be a neat command line tool called cap. > > > > > 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. > > > > That's what we've been doing for the last years, not always in public, > > but rest assured that that's what we're going for. As for IRC, I'm > > fine with getting on it more often in the future. > > > > > 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?) > > > > That's exactly what we want as well, we won't push ourselves on the > > community, for us it just made sense to take on the responsibilities > > to be those guys, because we spend a lot of our time working with and > > working on Capistrano. > > > > Hope that cleared things up a bit. We obviously proposed our idea to > > Jamis before we officially posted anything, and if we go forward with > > this, there will still be the same website, the same gem repository > > and the same Capistrano. > > > > Cheers, Mathias > > --http://paperplanes.dehttp://twitter.com/roidrage > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
