Sorry for the delays in the updates.
As for forking of Plugins, In general, WordPress.org discourages it for a few reasons, the first one that comes to my mind is that those who are using the old plugin never get the notice about the newer forked version eventually leading to more problems for users.
If someone wants to make a diff/patch to the plugin, I do appreciate it, and if you send it along in an email (to firstname.lastname@example.org) I will take a look and do my best to get it in the plugin - Of course, if theres no time to review things, and test it properly personally before release, it just never happens.. Testing other peoples work is not exactly a fast process, and many times in the past has simply lead me to writing the fix myself, knowing that I could trust the way i've written it (Something I can't do of other peoples code!). But if you do provide a patch, and are interested in helping out on the plugin long term (ie. be a committer to the plugin), I can work that out - It'd just require someone who wants to stick around long enough, and is willing to take code criticism to make sure the end product was still something i'd be happy to have attributed to myself in some way.
Finally, 2.1 has a few bugs still, none of them new, I'll get to it over the next fortnight though.