People (for now) should just use the latest stable release from Jamis.
(...)
In a few months we'll know better who's really taking up the effort and
should be able to push another stable release.
Precisely. Easy forking merging back using Git+Github gives probably
best ideas who's up for
Just wanted to jump in and say that I would be up to help in any
capacity I can. I can't really code in Ruby worth squat, but I offer
whatever I am able to do.
On Feb 26, 3:44 pm, Lee Hambley lee.hamb...@gmail.com wrote:
Ahh :)
That explains why I could never get my gem to install anywhere :)
Just a quick note -- I would not be overly worried with some chaos
regarding Github forks. It'd be great to see different/separte ideas
implemented.
Of course, there should be http://github.com/capistrano/capistrano/tree/master
as canonical. Sinatra [http://github.com/sinatra/sinatra/] has it
On Fri, Feb 27, 2009 at 18:00, Mike Bailey m...@bailey.net.au wrote:
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
On 27.02.2009, at 18:00, Mike Bailey wrote:
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.
Because the result will be people continuously asking
On Fri, Feb 27, 2009 at 12:51 PM, Mathias Meyer
pomonra...@googlemail.com wrote:
On 27.02.2009, at 18:00, Mike Bailey wrote:
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
Hi,
it's great to see you picking it up so soon :)
Capistrano changed the mental model of deployment forever, for lots of
people, inside Rails community and outside of it.
I cannot help with improving the codebase, but would gladly help with
further work on documentation/tutorials, as I did
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
Hi
I am just glad someone is willing to step in so quickly.
I think capistrano and webistrano is both great products but with an
original focus on ruby/rails applications. I believe that with a bit
of effort ( a bit more in webistrano) it could easily be made to be
more generic. Currently I have
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
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
Hey Jamis,
I never actually bothered to check, I figured it was served from the github
gem server -- completely agree with your last statement about people not
really taking much interest in hacking the core before, there's no reason
that people should go messing with it for no real reason now...
On 2/26/09 2:18 PM, Lee Hambley wrote:
Hey Jamis,
I never actually bothered to check, I figured it was served from the
github gem server -- completely agree with your last statement about
people not really taking much interest in hacking the core before,
there's no reason that people
Lee Hambley wrote:
My only concern would be that there is no more single place to go to get
a copy, get info and learn about it, a bunch of similarly named forks,
with similar feature sets would just cause trouble :)
I don't think this will happen as the 'blessed' version will pretty fast
On 2/26/09 2:27 PM, Jonathan Weiss wrote:
Lee Hambley wrote:
My only concern would be that there is no more single place to go to get
a copy, get info and learn about it, a bunch of similarly named forks,
with similar feature sets would just cause trouble :)
I don't think this will
+1 for a capistrano user on github...
Does anyone know what happens, if Rubyforge, and Github gems both exist,
which do you end up with... the newest, I suppose?
- Lee
2009/2/26 Jamis Buck ja...@37signals.com
On 2/26/09 2:27 PM, Jonathan Weiss wrote:
Lee Hambley wrote:
My only concern
On 2/26/09 2:39 PM, Lee Hambley wrote:
+1 for a capistrano user on github...
Does anyone know what happens, if Rubyforge, and Github gems both exist,
which do you end up with... the newest, I suppose?
Github gems are not searched unless you explicitly configure for them.
Furthermore, github
Ahh :)
That explains why I could never get my gem to install anywhere :)
- Lee
2009/2/26 Jamis Buck ja...@37signals.com
On 2/26/09 2:39 PM, Lee Hambley wrote:
+1 for a capistrano user on github...
Does anyone know what happens, if Rubyforge, and Github gems both exist,
which do you
I'm actually working on a couple of Capistrano new features.
I contacted Jamis on January and he gave me some good ideas about how
implement them.
Unfortunately, it seems I finished them too late.
All the features are available in my Capistrano fork on github.
+1 (or is it +2 ?)
I don't see anyone else offering, and you are certainly two of the
more qualified candidates :-)
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to
capistrano-unsubscr...@googlegroups.com
For more options, visit this group at
20 matches
Mail list logo
