On Tue, Jan 21, 2014 at 10:47:50AM -0500, Rich Freeman wrote: > If Comrel really objects to this I'm not entirely opposed to letting > QA have the reins (certainly we can't just let policy go unenforced > entirely). However, I would encourage the teams to give some thought > as to whether it makes sense to work together to separate the human vs > technical factors here.
Well, I guess that's the big question isn't it -- what is personal vs technical? I think we can all agree that if qa changes an ebuild and a dev comes back with "You stupid *** leave my *** ebuild alone." and reverts qa's change, that is personal and goes straight to Comrel because it is now a CoC violation as well. What about the scenario where qa makes a change, then the dev, in a civil manor, explains to qa why he prefers his original method and reverts QA's change without the agreement of QA and without presenting his case to the council? Now you have another qa violation since GLEP 48 states that QA's changes must stand until the council says otherwise. However, assuming the exchanges between qa and the dev are still respectful, I'm not sure there is a personal issue. wrt the commit rights issue: QA is asking for the ability to *suspend* not *revoke* commit rights. This was explained well by Tom; it is a temporary measure to get a dev's attention if nothing else works. I agree that it is strong. However, if qa gets out of hand with it, the council can always step in and take care of the matter. Thoughts? William
signature.asc
Description: Digital signature
