I believe his comment on "KDF trolls" is in regards to people who simply complain that KDF will never get fixed. You may have noticed, he answered several KDF-related questions, with some decent responses. But the real "meat and potatoes" of the answers, are as usual hidden behind the typical "We have plans, but we can't reveal them yet...". That may in large part be due to his previous behavior where he revealed big plans in great detail (the old "Engineering Report" posts), and as expected, many players were ultimately disappointed when said plans didn't pan out.
A more balanced approach is certainly the way to go, but I still would like to hear concrete answers to some of the many KDF-related questions people have been having. I noticed several in chat who quite simply said "Give it a rest already!". Problem with that is, KDF players have been waiting for 3 years. As Archer said to the Vulcans; "How much longer?"
They have a great resource, called 'The Foundry'. Add additional props appropriate for Klingon maps, and make the map design tools (click-and-place room layouts) as well as populating rooms with appropriate enemies and props, and you'll have a dynamite method for user generated KDF missions. Add 20 or so of the "best" KDF missions, adapted for the games storyline, and BOOM, there you have your level 1-20 content for KDF. The reason KDF isn't played as much as FED, is because players have to FIRST level to 20 (or is it 25?!?) on FED side, before being able to start a level 20 KDF character. If players could start a new KDF character at Level 1, with full PVE progression from 1 through 50, more players would play it. They need to take a "If you build it, they will come" approach to fixing the KDF. Rather than the current "If they come, we will build it."
I'll be going through the posted transcripts at the STO forums, and compile an extensive email with both suggestions and questions regarding STO. As Executive Producer, Mr Stahl is certainly the right person to post suggestions to, as he can both forward those suggestions to the related team members, and okay/nix the suggestion if deemed necessary.