A good start would be to just put it on GitHub and have somebody who can, occasionally, review and merge pull requests. Since you no longer have in-house technical staff, I don't think its reasonable to expect you to do any more than that. You may even want to give a trusted community member commit access to do the review/merging since paying a contractor may not make economic sense.
Going by my experience with the original Midifighter source code, you're likely not going to have very many people play with the code and fewer still will contribute changes. As far as I remember, from speaking with Robin and Michael, myself and my brother were one of the only (possibly the only) people who actually made any significant changes to the original Midifighter firmware (changes are available here, btw). However, having the code available will give people who care some level of comfort and hopefully will mean that a few bugs get fixed here and there. It also may help get back some of the tinkerer/maker vibe that Midifighter had back in the early days (which is what got me interested in the first place -- I am not a DJ).
As I said in my previous post, I'm willing to help where I can, although actually implementing changes/fixes, testing them and rolling them out is.. probably not realistic as I don't own a Twister and can't currently rationalise buying one just to tinker with (as I said above, I'm not a DJ), but that doesn't mean I can't help, especially as I've had past experience with the MF codebase so may be able to provide some guidance to others.
Will you be open sourcing the firmware for the entire Midifighter range or just the Twister? (I suspect they're all quite similar anyway -- the 3D code was surprisingly similar to the Pro for example)
Bookmarks