"The fact that other communities haven't moved into their sections en masse is not their fault. It's YOUR (ie. everyone else) FAULT."
The first sentence is fine. The second not so much. "Fault" assumes that moving to SO/contributing etc is unambigously a good thing. I would not be suprised if at least some developers thought their existing communication channels are just fine.
"For example, I tried to get the Grails community to use StackOverFlow when the site first started and their attitude was that they would rather just use the mailing list and sift through Nabble.
"The problem isn't with StackOverFlow, it's with the other communities refusing to adopt something new."
They may have good reasons to do so. Just because you are enthusiastic about SO doesn't mean everyone has to be.
(Due Disclosure : I don't use SO at all. I once saw an algorithm question on SO I could answer and when I tried, I found out I had to use OpenID to log in. Couldn't be bothered.)
StackOverFlow provides structure and organization to the information. I've dug through enough email threads that ended at a dead-end to be able to say that the structure is welcome.
People tag their questions, while others vote on the questions and answers. Question titles are matched against the database when people enter new questions. Admins "close" duplicates, and stop trolling. The reputation "economy" provides a way to get an answer.
StackOverflow isn't perfect but it is a big step forward in organizing the information so that that the data can be searched more effectively.
The first sentence is fine. The second not so much. "Fault" assumes that moving to SO/contributing etc is unambigously a good thing. I would not be suprised if at least some developers thought their existing communication channels are just fine.
"For example, I tried to get the Grails community to use StackOverFlow when the site first started and their attitude was that they would rather just use the mailing list and sift through Nabble.
http://archive.codehaus.org/lists/org.codehaus.grails.user/m.... "
This sounds like a valid choice to me.
"The problem isn't with StackOverFlow, it's with the other communities refusing to adopt something new."
They may have good reasons to do so. Just because you are enthusiastic about SO doesn't mean everyone has to be.
(Due Disclosure : I don't use SO at all. I once saw an algorithm question on SO I could answer and when I tried, I found out I had to use OpenID to log in. Couldn't be bothered.)