> I'll contact the council separately, and ask that they look at two > things: > > a) What the QA team is and isn't empowered to do > b) The approval process that the QA team must follow before imposing > tree-wide changes on other developers.
According to prior council meeting logs: 15:14 <@vapier> QA works off of agreed policy. policy was put forth by developers and validated by council. 15:14 <@seemant> the fact is, QA can scream all they want -- but if there's no *authority* behind them, devs might be inclined to feel free to ignore QA 15:14 <@Azarah> and if they do, they get sorted by devrel in theory 15:15 <@vapier> so they have authority now. listen to the QA team because they're working of valid policy. if you dont, devrel will take action. So the only question in my mind is what does it take for something to become 'vaild policy'. I believe the QA team is working on a writeup to present to the council to address that issue. --Dan -- gentoo-dev@gentoo.org mailing list
