I am not sure if it's a mistake to make this post community wiki as opposed to simply closing it as not constructive: Project management blogs
In The Future of Community Wiki. Here is a quote from a user on another Stack Exchange site talking about the detriments of community wiki:
... the examples of ‘community wiki’ that I’ve seen so far seem to be actively detrimental to the web site. For example, the ‘What Lion bugs irritate you the most?’ thread takes lots of good questions and answers that could (should?) be individually placed on the main page and effectively hides them in a single thread.
For just about any other question where someone asks "can't we just make it community wiki", we should stop and ask ourselves if there aren't possibly more great questions we can harvest:
Many things which “need” to be community wiki simply don’t. Sometimes it’s just a matter of understanding the root of a question: “Software to record video games” can be turned into a great question (How Can I Record Demos of My Gameplay?) without needing the crutch of community wiki. Or, you may need to break the original question into smaller parts...
(emphasis is mine)
In conclusion, will this post listing blogs be good for our site? Will it just be used as an excuse to make more community wiki posts, losing the message altogether about how it's not a quick fix for problem questions and how they may prevent other great questions from being asked? Will it just bring in spam? If the message gets lost or if it just promotes spam, should this be removed? What value does this bring to our community?
My hope is that it could help stifle the growth of the types of questions we don't want here. My hope is that next time someone asks for a list of blogs, or a link to a resource that discusses Agile, or some other not constructive question, we point them to this post instead.
Let me know what you think.