Yeah, it's too bad that we don't have the resources right now to keep
up the prior momentum on Quark updates.
I've seen various forks made of the Open Quark code base in github, so
maybe we'll see some further community contribution.
Nevertheless, as soon as we get can spare some cycles amongst the
general start-up craziness (who'd have thought customers can keep you
busy!) then we'll take some time out to get things organised again on
the Open Quark side. Also, all of our current change set over and
above the public code base is bug fixes rather than any new juicy
features. Per my original post, I'm hoping to change that with a new
hire... we'll see.