Bearing in mind that, second only to the API docs, the KitchenSink is the most important and useful training resource to which developers have access, I am very disappointed that bugfixing and development of it seems to be almost non-existent.
As an example, several months ago, I submitted a git commit containing fixes for every single syntax error that the KS contains (about 300 errors!), and then posted a notification to the devs. Despite this, the fixes weren't merged. OK, I admit that syntax errors are a trivial issue, and probably don't cause any problems with the app's functionality but, on the other hand, there really is no need for them! The work was done - all you had to do was merge it.
However, the KitchenSink contains SO many bugs that do cause functionality not to work but which also could be easily fixed. If Appcel does not have the manpower to properly maintain the KS then, surely, should it not just hand it over to the community?
I also raised the subject with Appcel some time ago of utilising the community more effectively, but there seems to be little change. It's such a missed opportunity, IMHO. If there are any planned developments in this area going on behind the scenes, then I am sure I'm not the only one who would be interested to hear about them.
I put "Community Development" as my priority in the recent survey, and too have asked appcel about utilizing the community. I was told (quite helpfully) to take a pull from github :P
would appear then if you do nothing gets done about it
1) fix the Q&A
2) fix kitchenSink
3) sort out a team for the Q&A / docs (community based or otherwise)
 oh and answer tickets [/edit]
I also agree wholeheartedly, especially about the lack of utilization of the existing community. Because of this, I'm currently working on creating an independent Titanium Mobile resource and training site. The site will include guides and tutorials to help developers get started, and maybe most importantly, a proper forum so the community can flourish and grow.
If you're interested in helping, you can contact me directly at firstname.lastname@example.org or use our contact form: Contact Us
I'll be sure to update the community as the project progresses.
Can you post your source somewhere? I'd love to have a version without all of those warnings.