QA, a �popular� task? Really?

“Back on topic. As I said, I think the QA team should be the one
deciding whether a developer is a technical liability to the
project. This is crucial for the quality to be kept in check:
having a “motivated” developer that makes a mess around the tree is
not something we’re very happy about; while we strive to motivate
people to help out, doing so recklessly is not good. But nobody
expects the QA team to be good at judging the interpersonal skills
of developers, which is why I said that devrel should do that. On
the other hand, it seems like the Developers Relations team wants
to take care of that as well. It would be all fine and dandy if the
members of that team were to be chosen for their technical skills
but … well, that’s not the case for most of them I’m sorry to
say, and I don’t think that they’ll be saying otherwise here. The
rebuttal we read about that has been that “some of you can join
devrel” but the whole point is to keep separated and different the
HR team from the technical QA team. They both have their different
jobs to attend to.”

Complete
Story