Provides various more convenient wrappers around Net::HTTP methods

Rake tasks for running your Jasmine suite via a local browser or through SauceLabs

Friendly command-line interface for Jing Dong Foundry.

Jetel - Custom made ETL for specific needs

High-level library for working with the Jing Dong Foundry API.

Jinx JSON plug-in.. See github.com/jinx/json for more information.

Personal fork, do not use.

Little library that encapsulates a (particular) standardised way of talking between a service and javascript. Probably not the best way of doing things, but it's been handy in a pinch.

Ruby Library for consuming the Fonolo web services for deep dialing

Ruby Library for the Whitepages API - http://www.whitepages.com

Local Database using JSON files

An easy, streaming way to generate JSON.

Rake tasks for little JavaScript projects

JSon Simple Specification

This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace

Helper to simplify RPX Now user login/creation based on Michael Grosser's rpx_now gem

This gem allows simple access to administration API of Kerio products

A Kiseru client for Trello

Used for access to KOBRA, API-account needed

Thor tasks to package chef solo cookbooks