On Thu, Sep 10, 2015 at 11:41 AM, Alec Warner <anta...@gentoo.org> wrote: > > On Thu, Sep 10, 2015 at 8:35 AM, hasufell <hasuf...@gentoo.org> wrote: >> >> >> If this affects tree consistency and usability, then it is not just up >> to the maintainers. > > There are lots of topics where I concede that QA has a point and can utilize > its influence; but 'consistency and usability' are not topics I would > normally expect them to impose on developers. >
Well, consistency as far as it involves compliance with standards (PMS, tree policies, etc) certainly is fair game. I don't think they always need to be the ones creating the rules, though. In any case, the whole versioned toolkit (gtk/qt/etc) flag issue is on the council agenda. I think this is an area that would benefit from a policy, whether or not I end up agreeing with whatever the policy ends up being. Even if we end up deciding to push to not use versioned flags, we may still end up having them for one-offs, and we'll still need policy on how to properly control whether the gui gets built or not, and so on. If we at least have a standard practice things will be easier on everybody, and this is bigger than any one Gentoo team. Of course once a policy is established QA should by all means enforce it. Also, I know that QA tends to get some knee-jerk reactions, but when QA announces a policy it isn't like this is the end of the conversation. If you think they're making a mistake, you can always talk to the QA lead, and appeal to the council. For the most part I think most of us try to be practical, even if we sometimes create a mess before we realize what we're getting into. -- Rich
