| 1 |
On Sun, 19 Jan 2014 12:18:49 -0800 |
| 2 |
""Paweł Hajdan, Jr."" <phajdan.jr@g.o> wrote: |
| 3 |
|
| 4 |
> On 1/19/14, 10:29 AM, William Hubbs wrote: |
| 5 |
> |
| 6 |
> > +* Should a situation arise where a developer causes breakage to the |
| 7 |
> > point that it cannot be ascribed to an honest mistake, either the QA |
| 8 |
> > lead or two members of the QA team can require the Infra team to |
| 9 |
> > temporarily suspend commit access for the developer, pending |
| 10 |
> > analysis of the causes and resolution to be provided by the QA team |
| 11 |
> > within 14 days of said suspension. Resolution for these kinds of |
| 12 |
> > issues is completely in the hands of the QA team, and only the |
| 13 |
> > Gentoo Council can revisit the case. |
| 14 |
> |
| 15 |
> 14 days sounds like pretty long. I recommend replacing that with |
| 16 |
> requiring that decision to be validated within 7 days by the QA team |
| 17 |
> lead. If he concurs, the next steps are outlined above, just as if he |
| 18 |
> himself started the process. If he decides to reverse their decision, |
| 19 |
> he can just ask infra and handle the rest of the matter within QA |
| 20 |
> team. |
| 21 |
|
| 22 |
Yes, 7 instead of 14 days sounds good. |
| 23 |
|
| 24 |
For the rest: Note that this is the QA team, as well as "QA lead or two |
| 25 |
members"; hence the paragraph deals with the persons whom requested the |
| 26 |
suspend to provide it. It doesn't involve validating / reversing it. |
| 27 |
|
| 28 |
Given that this has been typed years ago; we probably might just want |
| 29 |
to rewrite it from scratch, discussing first what we actually want and |
| 30 |
then write a proper patch that deals with all the cases rather than |
| 31 |
some rules that leave open a lot of questions. |
| 32 |
|
| 33 |
How long is temporary? What happens after that? Provide to who? ...? |
| 34 |
|
| 35 |
> It's also suspicious to me why not just go to Comrel also in the |
| 36 |
> second case, but the draft directly mentions the Council. |
| 37 |
|
| 38 |
It could be perceived as outside ComRel's scope, as a technical matter. |
| 39 |
|
| 40 |
-- |
| 41 |
With kind regards, |
| 42 |
|
| 43 |
Tom Wijsman (TomWij) |
| 44 |
Gentoo Developer |
| 45 |
|
| 46 |
E-mail address : TomWij@g.o |
| 47 |
GPG Public Key : 6D34E57D |
| 48 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives