Cool ideas: one of the things we've been talking about doing forever is the idea of multiple levels of authorship on blogs, where some people can create posts, but not publish them, some can publish and edit their own, but not others, and some have full admin access. It seems like you could do what you want by granting some people the ability to create posts on a specific blog, but not publish them and then let a blog administrator come through and schedule each post for publishing, letting each post sit for a week. Would something like that work?
I think this would work as long the approver had an interface to sift through the posts "efficiently"...with possibly some "aging" auto-purge configurations...the biggest thing is that not all posts will get published....so some feature to help with the management of that would be needed. Also, to reiterate...authorship should be preserved during this process.
Thanks for the ideas....I'm pretty sure it would work.
From a community marketing perspective, this is a great idea. Sun Microsystems does a great job of this. They ask community members to contribute ideas for their community spotlight section (http://community.java.net/projects/publicize.csp). Then, they keep track of all the spotlights in a blog (http://today.java.net/today/projects_communities.csp). This would be really helpful to easily update the blog.