Amazing. In a disturbing journalistic way.
The Salem Statesman Journal has editorialized in favor of proceeding with a $600-800 million Third Bridge across the Willamette River. It has published several news stories about this unwanted, unneeded, and unpaid-for debacle.
Yet... the newpaper has never, not once, not ever, talked with leaders of the No Third Bridge citizen group. Read all about it in today's No Third Bridge Facebook post.
SALEM BLOGGER CALLS THE THE EDITOR OF THE STATESMAN JOURNAL TO TASK FOR POOR COVERAGE OF THE 3RD BRIDGE
Salem blogger and Salem Weekly columnist Brian Hines is right in his open letter to S-J editor Michael Davis. Our "newspaper of record's" coverage of the 3rd bridge issue has been poor. There have been just a handful of articles about it. The leaders of the opposition have never been interviewed. Not once.
Maybe Hines' post will get some attention and we will get some investigative coverage between now and the City Council meeting on June 24th. But don't hold your breath.
I'm not. There's a good chance the supposed "paper of record" for our area will stay silent on reasons to oppose what seems to be the most expensive public works project in Salem history.
If this bothers you, tell the SJ executive editor, Michael Davis, how you feel:
This is one reason why traditional newspapers are dying: they aren't practicing genuine journalism any more.
Thanks for the shout-out, No Third Bridge guys. I just wish the Statesman Journal would get off its butt and start covering this story like it should be. Like I said in a comment on the Facebook post:
Glancing at the front page of the Statesman Journal today, I saw the banner headline was "College-funding budgets headed for vote."
OK, that's a rather important statewide issue.
But come on, S-J dudes... isn't it even more important to inform Salem residents about an upcoming (June 24) vote on a $600-800 million Third Bridge?
Especially since you have never, not once, talked with the lead opponents of this unneeded, unwanted, and unpaid-for boondoggle?