Hi Owen, Haha, thanks for calling me an expert - although I'm really far from that :D
You're right yeah, of course a project like this needs contributors too, not only users. I for myself am currently not the best at understanding hobo internals, since I did a lot of work in the past months not related to hobo, rails or even ruby (unfortunately). I'm trying to catch up though - struggling with time management I'm somewhere between understanding hobo, getting better in ruby meta programming, following rails and writing my own apps and sites. Hopefully I can help more in the next months, since most of my other work is done now. What I really like is that some (I think thats actually you Owen?) use Hobo on a win32 platform and can help people doing the same, thats pretty cool, and a widespread community is very important. In my experience (in #rubyonrails for example) the hardest part of bringing-people-to-hobo is to convince them that it is not some sort of inflexible scaffolding like other projects... On Sun, Dec 14, 2008 at 05:41:12AM -0800, Owen wrote: > > But we won't be successful unless we can eventually get experts like > you, Sol, to be contributors and build a critical mass. I am an > architect and designer, not a day-to-day coder. We are starting to > build expertise in our team (e.g., Tola and Edmund), but you guys are > still the key. > > I have had over 25 years experience as an entrepeneur building mission- > critical applications with small teams, beating out the Big Guys many > times using the right tools and having the right teams. So I think I > have a good gut feel for the potential here. > > We are very excited we can help in our small way. Many of the recent > Hobo enhancements were critical to success on the first phase of a > large project for the US Department of Agriculture. (See the tutorial > http://cookbook.hobocentral.net/recipes/11-replicate-the-look-and-feel-of) > > There are many, many modules to this application, so It won't go into > production for several months. But we will keep feeding back into > Hobo generic enhancements as we go. For example, the recent > enhancements to LifeCycles and Permissions.. > > We hope that you all will do the same and contribute as you can. With > the global recession, it is even more important to be able to build > apps quickly and to be able to turn on a dime... > > -Owen > > n Dec 14, 8:18 am, sol <[email protected]> wrote: > > very cool to hear that Barquin has such remarkable long term goals! :) > > > > On Dec 14, 2:02 pm, Owen <[email protected]> wrote: > > > > > Glad you got it. I have frequently had a problem with rubygems.org, > > > but it usually comes back soon. > > > > > Our goal for Barquin's support and input to Hobo is to make it so you > > > DON'T have to be a rails expert to use Hobo. > > > > > We look at Hobo as much more than a "Plugin". Hope you all do too. > > > Unfortunately, the Holy Grail is still down the line a bit... > > > > > Owen > > > > > On Dec 14, 5:46 am, Eric-news <[email protected]> wrote: > > > > > > On 13 dec, 23:00, Eric-news <[email protected]> wrote: > > > > > > > --> ruby script/generate hobo --add-gem --add-routes > > > > > Rails requires RubyGems >= 1.3.1 (you have 1.2.0). Please `gem update > > > > > --system` and try again. > > > > > > > ~]# gem update --system > > > > > Updating RubyGems > > > > > Nothing to update > > > > > > This one was easily solved by running 'update_rubygems' as root. Now > > > > the hobo-command runs smoothly. > > > > > > -- > > > > Eric > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
