Facebook Partners with Stack Overflow
I don't see the stack overflow model as being a great fit for what facebook api developers need.  The main problem I saw with facebook api was that the right way to do things kept changing, and the docs and forum didn't keep up well.  You basically needed to begin facebook API work by reading the entire blog in chronological order and then keep on scanning the dev blog daily, which may work ok if you're a fulltime facebook API developer but it is not a good fit for contract or part-time or hobby development.<p>I think changing APIs is begging for a wiki much more than a Q&A site.  Facebook used to have a wiki for their api, but they went and deleted it, which I considered basically unforgiveable and proceeded to do my best to avoid having to touch the API after that.<p>In short, bringing back <a href="http://wiki.developers.facebook.com/" rel="nofollow">http://wiki.developers.facebook.com/</a> and focusing on keeping it current would be a much better start than a Q&A site, even a really good Q&A site.  You'd still have the need-to-keep-with-changes problem, but at least you'd have somewhere to start from, and wouldn't keep getting referred to out of date information when googling answers.<p>Yes I know Stack Overflow has community editable wiki question styles, but then you just compound the problem and now need to update 100 different 'how do I [x]' questions every time the API changes.