If you’re among the early adopters of Ruby 1.8.2, you will have noticed that rake chokes when attempting to run all the tests in a suite. Thankfully, Dave Halliday was quick to device a fix, which you can apply right away while we await a new release of Rake from Jim Weirich.
I’ve introduced the new [RESEARCH] prefix to ticket summaries in addition to the existing [PATCH]. By applying the [RESEARCH] prefix, you’re sharing a patch with the world that either needs additional testing, suggestions, or development before being ready for trunk inclusion. We have a new report as well to show the research patches of which there are currently five.
I’m regularly getting requests from people who wants to start up Rails development, but are looking for a way to kick-start the affair by retaining one or more experts. Some make good candidates for referring to the firms listing themselves on the Commercial Support page while others are looking to hire developers into their team on either a contract or full-time basis.
It’s for the latter scenario that I’ve started the Available for Hire page on the wiki. If you’re a single developer looking for work with Ruby, please do add yourself to that page if you feel your skill set is at a level where you could consider yourself “capable” with Rails.
Defining “capable” is always hard, but you should probably at least have made significant contributions to the framework and/or have one or more Rails projects under your belt. Such a project can very well be a demo application, though. It needs not be commercial work.
I’ve received quite a few alternative suggestions for a logo since we unveiled the direction Hicks was taking the identity. They all discarded the work that was going on and went in another direction entirely. So that wasn’t going to fly. What could fly, though, is a variation on the theme already established. That’s what hangon have done after he realized that being rude weren’t getting him anywhere:
What a much more productive use of your discontent. I actually quite like this variation. What do you think?
Across all versions and distributions forms, Rails have now rounded 10,000 downloads since the first version was released just five months ago. That’s an incredible achievement for a new framework to reach in such a short period of time, but if things go as they should, we should be celebrating 100,000 downloads in another five months (world domination doesn’t occur by modesty, now does it ;)).
Thanks to all the contributors who helped make Rails a desirable package. Thanks to all the companies that took a chance with a new kind of productivity. Thanks to all the many users who made it interesting to release new versions.
And of course thanks to the live community hanging out on #rubyonrails and firstname.lastname@example.org. Keeping the energy at a staggering high day by day.
Andreas Schwarz has long been one of the most vocal speakers for making sure Rails could be keep the data of its applications secret and safe. So what could be more natural than for him to share his knowledge in a new Rails manual entitled Securing your Rails.
It’s still a work in progress, but already packed with useful information.
Reading code written by veterans has always been one of the best ways to learn the way of the arts. And of course, so is it with Rails, which is why I’m particularly pleased to see the trend of sharing your code using the fantastic Trac application take hold. In addition to open repositories for Hieraki and RForum, I’ve just today added another two:
- Collaboa: The community application running cocoa.se by Johan.
- EliteJournal & RecipeBox: The weblog and recipe software by Scott Baron.
The work originally started by Joey Gibson on the MS SQLServer adapter around RubyConf is now finally nearing completion. The adapters have been charged with adding the LIMIT-condition and that made it possible to do the “SELECT TOP X” style that SQL Server needs without dirty hacks.
So the current sqlserver adapter in Subversion is actually quite functional and passing almost all of the unit tests. DeLynn Berry has accepted the responsibility for tying up the loose ends.
At the same time, Maik Schmidt has been busy finishing the DB2 adapter, which is already available as a patch on Trac. This baby is passing everything but the DB-specific OFFSET test, so you should happily be able to use that right away.
So it looks like Active Record will finally see the adoption of new adapters in the next release. On the horizon is a long-awaited Oracle adapter by Jim Weirich and a FrontBase adapter by Eric Ocean.
The Rails wiki has taken a few beatings, but now it’s running in high class with proper rollback protection, so we should now have a stable host to fill with content. So what better place to start than to extract all the missing content from the two backups we have that might contain missing pages:
- Static backup of changes from late November to late December
- Dynamic backup that might contain missing pages in the latest move
The easiest way to figure out what’s missing is to go look for your own content. If you miss some of that, then please do retrieve it from one of the backups. But that shouldn’t hold enterprising individuals back that want to help with the restoration. Dig in!
Collaboraid recently had a visit with their client on that major intranet project for the still concealed client. Here they learned just how much of a difference it makes to work in a truly productive environment:
Yon, my colleague, would demo the work-in-progress to someone, and—as expected—we’d uncover some room for improvement here and there. But what turned out to be really fascinating was that most of the time, I was able to fix the problem on the spot, and we could re-test the improved version 10 minutes later.
Larger things, we’d do in out hotel rooms later that same night (after dinner and drinks with the client, of course). That’s what the power and productivity of Rails is like. In addition to just saving time, it also helps spur people’s imagination in constructive ways, when they see the kinds of changes that are possible on the fly like that.
Collaborative development and participatory design have long been the hallmarks of the Scandinavian school of software development. How wonderful to see it practiced using Rails.