10 years of CFWheels / Welcome Adam / CFWheels 2.x

March 23rd, 2016 by Tom King

A bit of history:

It’s slightly hard to put an exact date on it, but this year (probably) celebrates 10 years of CFWheels!

Obviously, in the internet age, 10 years is an awfully long time. The first mention I can find if from Pete Freitag’s “Get Wheelin” blog post celebrating CFWheels 0.1 in November 2005. Rob Cameron, the original author moved over to Rails full time a few years later: you can catch up with him at http://ridingtheclutch.com/. Over the years there have been a lot of contributors – whilst our GitHub repo hasn’t quite got that (very) early history, since Jul 23, 2006, we’ve had:

• 2825 commits (Per Djurner has the dubious claim to fame of the first commit, and at time of writing, the most recent too :))
• 22 Branches
• 43 Releases
• 76 forks
• 453 issues

Whilst there was a “bit of a break” around 2012/13, Wheels has been going from strength to strength. Contributors have changed and moved on, and so have core team members. Our thanks go out to all of them!

Welcome Adam!
We’re very pleased that Adam Chapman (@chapmandu) has agreed to join the CFWheels core team! He’s been a long-time supporter of wheels, we’re very glad to have him on board. We expect great things AC…. great things. 🙂 You can find Adam’s blog here.

CFWheels 2.x:

Lots of chat at the moment about the next major release of CFWheels – please do get involved on the Google group if you’ve got ideas. At the moment, amongst lots of micro improvements, we’re looking at:

• integrating the ColdRoute plugin into the core:  ColdRoute allows you to define RESTful resources through new expressive routing helpers and controller conventions. It also allows you to organize controllers and views into subfolders via “namespaces” or “modules.”
• improving wheels as a true RESTful service provider: you can already return JSON, XML and lots of other good stuff, but we’re looking to improve things like setting custom headers, and really controlling your APIs response
• improving the plugin architecture, and generally looking a more “modular” way of doing things.
• dropping CF8/9 support; dropping Railo (as you should all be on Lucee now!!)
• better Commandbox support: we’ll be looking at CLI type stuff to make getting going with wheels even quicker.

Got an idea? Get on the Google Group and let us know!

Posted in Community | 1 Comment »