Frankly, this seems like an editorial mistake not a journalists mistake. Unless he completely made up the information he received, or lied about the attribution in the internal slack chat, he should not have been fired for this. This was an editorial error. In fact, the exact information he passed along was factually correct by one interpretation. The S-300 rockets were "Russian" in the sense that they were Russian m…
That seems likely, but you still don't let the reporter off the hook. "Technically correct by one interpretation" isn't the standard for journalistic sourcing. He needed another source or more context (just an identification of these as AA missiles would have been enough to kill the story) and didn't get one. It was a messup on a few different axes, but it's started with bad journalism. Whether or not the guy was fir…
Did you read the slack chat?
The journalist 100% does not need another source to inform his internal team of the initial story or the sourcing.
Did the journalist make the decision to publish? NO! They said that decision was above their pay grade. When people asked for clarifying information, they said they didn't have any.
That's why it was an editorial mistake.
Frankly, I simply don't see how you can conclude the journalist needed another source, given that it clearly it wasn't their decision to publish the article. That was an...editorial decision! Which is why I think the blame for publishing without enough information should go to...the editorial team