Project List

At any given time, I am up to my eyeballs in projects. This list is very, very incomplete. In fact, I have only included a few items so far, and only because I wanted to get the page started and did not want to forget these projects. More project information can be found in my Fossil Record, though that too provides an incomplete picture.

Original Software

These are cases where I have created a new software project from scratch and developed it to a point where it is worth releasing to the world.

Ruby Gem Maintainer


In the first half of 2012, I published a Ruby gem called "droll" (for "die roll") that I had developed for my own use as a roleplaying gamer. It is a library providing some sophisticated dice rolling simulation functionality, allowing for a number of complex operations in generating (pseudo-)random die roll results including "exploding" dice, selection of high or low values, counting dice that meet a threshold requirement, and other nifty capabilities that are familiar to many roleplaying gamers. Despite all that, it is not the most complex gem available by any stretch of the imagination, but I think it is a pretty decent effort.

In addition to the library itself, which provides the Droll class, the gem also comes with two user interfaces -- a command line dice rolling utility, and an IRC dicebot. I am happy with the results, and (as of this writing) it is in release candidate status. It is probably stable enough to drop the release candidate status, but I will give it some time for people to test it and get back to me on any possible issues. I will also continue to improve it, both because I use it heavily myself and because I want it to be as generally useful for other gamers as I can.

In addition to roleplaying game uses, it could also quite easily be used in other contexts where dice (or similar random number generation) would be appropriate, such as a craps games. RPGs represent the most sophisticated use of dice as random number generators I have encountered, however, so as long as I focus on satisfying the needs of roleplaying gamers I think I should be able to serve pretty much any needs of other, related users.


As of July 2012, I published my second Ruby gem, called "charset_move". It has a nominal library providing a CharsetMove class, but it's mostly useful just for the cmv command line utility interface that is installed with it.

The cmv utility "moves" a file, translating its name from one specified encoding to another. In short, it is a filename transcoder. It was inspired by a friend's search for a simple way to transcode filenames.


As of September 2012, I published my third Ruby gem, called "redrug". It is a simplified interface to some of the functionality of Redcarpet (a Markdown parser based on Sundown, which was based on upskirt), for common use cases.

I created it because it took me a grand total of one use of Redcarpet to decide I was tired of the overly verbose syntax required to get Redcarpet to do the stuff I wanted it to do. I understand why Redcarpet works the way it does; it is, relative to RedRug, a low-level library providing significant flexibility and power. For my purposes, I generally do not need all of that, so I wrote a wrapper library to simplify the interface.

Within a day after being published, this library had already become my most popular Ruby gem, as measured by the "downloads" numbers on In fact, it had more downloads within one day than the other two gems combined. It is published under the terms of the Open Works License, though this fact is not at present documented on either the homepage or the RubyGems page.


As of October 2012, I published my fourth Ruby gem, called "versionize". It is just a dead-simple way to manage version numbers in Ruby software, which I created because I wanted more than just a hardcoded string and accessor in my Ruby gems. There is not a whole lot to it, but it serves my needs, and after the first month of availability it seems like it might serve the needs of about 130 other people (the download numbers at as well.


As of April 2015, I published my fifth Ruby gem, called "creepcheck". It is an "April Fool's Project", in that (so far) each April Fool's Day sees me make updates to this joke-project, and I only update it on April Fool's Day.


As of December 2016, I published my sixth Ruby gem, called "fossgit". It is a command line utility that makes the process of mirroring Fossil SCM repositories as Git repositories more convenient. This includes pushing updates to the Git mirror to GitHub, if you have a GitHub repository for your Git mirror. It wraps the command line interfaces of both Fossil and Git to achieve these ends. I have plans to extract a library from the command line tool, which the utility will then wrap to create its command line interface, and to later merge that library into a larger project providing a Fossil API in Ruby, with FossGit itself becoming a consumer of that API.

Software Contributions

These are cases where I contribute my time to working on software projects run by other people.

FreeBSD Port Maintainer

At present, I only maintain one port for FreeBSD, xsel-conrad. From the port description:

XSel is a command-line program for getting and setting the contents of the X selection. Normally this is only accessible by manually highlighting information and pasting it with the middle mouse button.

This port is similar to x11/xsel, but with different CLI syntax and a bit more functionality. It is a lot more popular, too.


I picked up support for the port because I use the heck out of this utility, it was previously unmaintained, and the port needed a minor Makefile fix-up or two. All things considered, it's a pretty minor project, given how slowly a tool like this needs to change. I didn't even have to do anything to get it to compile with Clang.