[gentoo-dev] rfc: [QA] Ban policy introduction

2018-07-28 Thread Mikle Kolyada
Hello,

The Gentoo QA team would like to introduce the following policy that
would be applied to individuals breaking the state and quality of the
main gentoo.git tree

( as we do not have this strictly documented yet):



If recommended Gentoo workflow policies are not followed by an
individual developer
(e.g make major changes to the widely used eclasses without prior
discussion on the mailing list or
commit changes that lead to multiple CI checks failure), the standard QA
procedure is:

1.) Two warnings granted by QA team, after two independent breakages
2.) Revoking the commit access for 14 days

These violations will be evaluated individually by all QA team members.
Warnings can be revoked, if during 6 months period a developer makes at
least 20 non trivial changes not producing more breakages.








signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] rfc: [QA] Ban policy introduction

2018-07-28 Thread Sergei Trofimovich
On Sun, 29 Jul 2018 00:40:18 +0300
Mikle Kolyada  wrote:

> Hello,
> 
> The Gentoo QA team would like to introduce the following policy that
> would be applied to individuals breaking the state and quality of the
> main gentoo.git tree
> 
> ( as we do not have this strictly documented yet):
> 
> 
> 
> If recommended

It's not called "recommended" but "enforced".

> Gentoo workflow policies are not followed by an
> individual developer
> (e.g make major changes to the widely used eclasses without prior
> discussion on the mailing list or
> commit changes that lead to multiple CI checks failure)

Here should go exhaustive list of links to the policies to be enforced.

> the standard QA
> procedure is:
> 
> 1.) Two warnings granted by QA team, after two independent breakages
> 2.) Revoking the commit access for 14 days
> 
> These violations will be evaluated individually by all QA team members.
> Warnings can be revoked, if during 6 months period a developer makes at
> least 20 non trivial changes not producing more breakages.
> 
> 

-- 

  Sergei