c++ I'm not sure about this one - as I'm going away for a few days, please keep an eye open here for comments to clarify the scope of the review: Prepare a cross-platform QT C-wrapper class for unit testing and mocking - devjb‎ - 2018-12-07 13:59:35Z

@MartinR You might propose your changes as pull requests a the GitHub repo for now (currently I am the only one working at it). Once our FAQ is stable and self contained (no more SO related links). We will discuss need for further changes in room meeting events.

@MartinR Ty for engaging BTW.

@πάνταῥεῖ I was thinking of general feedback, not of concrete changes. As an example, #11 says “Moderation requests (e.g. cv-pls, del-pls, etc.) should not be a habit for users.” – As I understand it, off-topic questions should be closed quickly on Code Review.

@MartinR Ah, I probably misunderstood you. Of course requests are about off-topic questions and not about particular users.

@MartinR Largely, the criteria in place for SOCVR are there because it's just physically impossible for the participants in the room to handle all of the bad questions which everyone comes across in a normal day (i.e. there are too many bad questions per participating user). If the ratio of requests to participating users remains where the people participating can actually service all of the requests, then it's reasonable to have criteria that are looser than SOCVR uses.

The important thing is to not have so many the cv-pls requests in the room such that the requests can't be handled by the user's participating here. You don't want the room to become just a replacement for the Close Vote Queue. If everyone kept to the ratio of posting no more than 1 request per 4+ requests on from other people on which they have voted, then there would not be a problem with getting too many cv-pls requests.