Terence works at Heroku maintaining the Ruby stack and a slew of OSS projects such as Bundler and Resque, as well as helping with the Rails Girls movement. When he's not going to an awesome Heroku or Ruby event, he lives in Austin, TX, the taco capital of America, where everything is three times bigger!
(Terence loves Friday hugs, EVERY DAY OF THE WEEK! Give him a big one when you see him!)
Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue (#319) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backtward incompatible changes.
This is a talk about the journey of taking over Resque and we'll cover the work being done as well as the discussion of balancing the two parts:
For the 1.x series, we'll go over the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll end with how the community can help with things going forward.
Hihih! I would like to work in bacon and saunas into my talk! I have never given this talk before.