>>>I agree both the vendor and community support of MM.NET is quite weak,

I agree.

>>>>however I believe this can be fixed without Oakleaf becoming a bigger company.
There are numerous successful FOSS projects out there are that driven by a single developer, and while MM.NET is not FOSS there are a lot of similarities - not least that the users of the project are all developers and all have the MM.NET source code.

I'm wondering how this affects OakLeaf strategically, keep in mind they offer paid support on the product.

>>>>I do believe Universal Thread is holding the MM.NET community back, and Kevin is aware of this. Personally I would contribute more, example and tutorial wise, if there was a better forum, including some kind of wiki.
In particular, having activity on Universal Thread - a private forum - is doing no favours.

I couldn't agree more here.