Okay so here's the deal.
First, I've been kinda quiet this past week because I've been busy. I had to rebuild a machine at work that died and there's been lots of little things that have taken my time and attention. But I'm hoping this coming week will see some new builds. I have merged thekraven's source tree into mine (we were going to use this for our team) and I'll try to use that to push out the next release. I hope and expect that will be beta1.
I have three phones to make ROMs for. thekraven gave me a green light to step in and make builds for the LS670 (OS). I also have at least two VS660 (Vortex) users that are interested. I tossed out a VS660 build to one of them. The phone didn't work, but that's probably easily fixable.
I also have three flavors/projects to build: AOSP, CM9, AOKP.
That makes 9 ROMs and, since thekraven has bowed out (at least for now), only one dev. It's a lot to maintain.
I'm not sure exactly what I'm going to do. The two most attractive options off the top of my head are: (1) use the IHO repo. I have commit access already. But blarf may not want aosp and aokp in his repo. Or (2) use the team account I setup (github.com/thunderc) to do another iho-like project. Except I'd be making at least some of the binaries myself.
Any devs out there that have some experience and want to step up to maintain a ROM, please let me know. I will require some experience, as I have no interest in walking people through how to build a ROM and maintain repos. I will probably also contact the IHO devs to see if any of them are interested, and give them priority if they choose.