Just released rufus-scheduler 2.0.18. Thanks to Andrew Davey the 'cron' bit of the scheduler now understands "L" as in "Last day of the month".

Neg, a tiny and un-awesome PEG parser library just reached 1.1.0. This new release brings better error messages in case of unconsumed input and some helper for the translator feature (the thing turning raw parse trees to domain oriented trees).

neg is a neg narser, it could have been a peg parser, but it didn't make it to the exam.

ruote, a Ruby workflow engine, just released its 2.3.0, many small improvements on every front.

I just released rufus-scheduler 2.0.12, a thread-based scheduler. The main new feature is a :mutex attribute to prevent overlapping among scheduled blocks.

JSON has nice railroad diagrams detailing its syntax, a Parslet-based JSON parser shouldn't be too much work. It could even make an introduction to Parslet.

Version 2.2.0 of ruote, a workflow engine, is out. This tool follows workflow definitions to route work[items] among workflow participants.

just released rufus-jig 1.0, a Ruby HTTP client that groks JSON (and has some helpers for CouchDB)

It started in a notebook and ended somewhere between state, rules, aspects and transitions to the door. It's called volute.

version 2.1.11 of ruote, a workflow engine has been released. Many updates are included, and the web interface, ruote-kit, got seriously reworked.

Sudhindra Rao and Munjal Budhabhatti explain in their "Rocking the Enterprise with Ruby" talk at the RubyKaigi how they are building (and delivering continuously) a system orchestrating Rackspace datacenters

rufus-json is a ruby gem that lets you choose your JSON {en|de}coding backend. It has a preference for yajl-ruby, but is happy with json, json-pure and active-support.

rufus-tokyo is a FFI (and more) library for Tokyo Cabinet|Tyrant. It's time to retire it, there are better options now.

In ruote and decision tables, I show how to make ruote workflows and rufus decision tables work together.

Granted, you can do workflow with state machines, but there's still work to do in order to have a "workflow engine". There are also alternatives. The post "state machine != workflow engine" answers some questions and open up some more. At least, a set of links to Ruby state machine implementations concludes the post.

rufus-scheduler 2.0 a rewrite of rufus-scheduler (cron, at, in, every scheduling from within ruby). Now comes with an EventMachine mode.

rufus-decision 1.1 was just released. Decision tables are an elegant / naive way of representing some domain logic. Rufus-decision interprets decision tables (in their CSV representation) and produces an output based on matching fields in the input data.

rufus-lua embeds Lua inside of a Ruby application, via Ruby FFI.

rufus-tokyo is a ruby gem for handling Tokyo Cabinet databases. It's based on the ruby-ffi gem (mri, jruby and rubinius) and makes cabinets look like hashes. Version 0.1.0 has just been released. Source is on the GitHub.