On Tue, 01 Apr 2014 18:55:40 +0300 Samuli Suominen <[email protected]> wrote:
> On 01/04/14 18:28, Tom Wijsman wrote: > > On Tue, 01 Apr 2014 12:23:43 +0000 > > hasufell <[email protected]> wrote: > > > >> And this is going to get worse if people don't trust them. > >> Currently it looks more like a loose club, instead of a team with > >> strong hierarchical structure, which is the only thing that > >> enables a quick line of action if needed. And that is one of its > >> purposes, afaiu. > > There is a strong structure present; for policy enforcement and > > breakage prevention, we have the ability to 1) act until there is > > And let's be perfectly clear here, nothing was, or is broken. Or would be; for instance, the PDEPEND. It is usually done in prevention; see it more as a "what if" and less of a "spank for breakage", in this case his decision might have been taken too fast. > Futher, no policy was violated, none, whatsoever. The "appeal to ..." policy was, but it was a first time event; this can serve as a reminder how people can respond to such a QA action, that is to talk to the 1) QA person, 2) QA team and then 3) Council. > This is an individual, albeit a QA member, disagreeing with a design > model. How can we disagree with a design model we didn't know about yet? > If joining QA team means you get to dictate, alone, how others do > their work, even when they are not breaking anything while doing so, That is also a part of quality assurance. > without the rest of the team, we'd be setting a bad precedence. Per the GLEP; when there is disagreement, the rest can vote on it; beyond that, there's also the Council. > The QA membership is not a large trout you get to bash others with > when you feel like it. Of course; but this isn't what is happening, is it? > Otherwise everyone would be lining up the QA team membership just to > protect their work from others. Projects like the Council, ComRel and QA are there to protect Gentoo; and yes, people are (or should be) lining up to protect Gentoo. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : [email protected] GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
