[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] rfc: [QA] Ban policy introduction
From:       Dirkjan Ochtman <djc () gentoo ! org>
Date:       2018-07-30 9:03:35
Message-ID: CAKmKYaDL7s9yCmHypBrHHZ_btE+9zpChtrwbjijFcghKp43PXQ () mail ! gmail ! com
[Download RAW message or body]

On Mon, Jul 30, 2018 at 8:52 AM Guilherme Amadio <amadio@gentoo.org> wrote:

> If you introduce penalties for breaking prefix as well, I'm afraid many
> people will be unnecessarily penalized. I think that such penalties are
> counter productive in most cases. If someone is really being careless it
> might make sense to get some warning and lose commit access temporarily.
> If someone made a simple mistake that can be easily fixed, like version
> bumping a package that starts to fail in some corner case, then
> punishment doesn't make much sense.
>

The proposed policy already mentions that people will only be punished
after two warnings. This seems enough for me -- if people keep breaking
stuff despite warnings, a little penalty is probably a good thing.

The proposed policy already goes out of its way to require two warnings for
"independent" breakage, but it's not entirely clear what independent means
here. If you commit three breakages that are technically unrelated on the
same day, then you probably shouldn't be banned immediately. So I would
suggest also making clear that the warnings should be sent at least a few
days apart and that an initial penalty cannot happen until a few days apart
the second warning.

That said, I agree with those who are saying that breaking things should be
obvious, things like ignoring repoman and/or other CI messaging. If the
breakage is non-obvious and hard to spot locally, then we should instead
invest in tooling to make it more obvious. By "ignoring" here I do mean
that there needs to be a reasonable timeout -- sometimes if I commit a
change and get a CI alert after a few hours, it might be tricky due to
work/family/whatever concerns to fix it within, say, 24 hours.

Regards,

Dirkjan

[Attachment #3 (text/html)]

<div dir="ltr">On Mon, Jul 30, 2018 at 8:52 AM Guilherme Amadio &lt;<a \
href="mailto:amadio@gentoo.org">amadio@gentoo.org</a>&gt; wrote:<br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> If you introduce penalties for \
breaking prefix as well, I&#39;m afraid many<br> people will be unnecessarily \
penalized. I think that such penalties are<br> counter productive in most cases. If \
someone is really being careless it<br> might make sense to get some warning and lose \
commit access temporarily.<br> If someone made a simple mistake that can be easily \
fixed, like version<br> bumping a package that starts to fail in some corner case, \
then<br> punishment doesn&#39;t make much \
sense.<br></blockquote><div><br></div><div>The proposed policy already mentions that \
people will only be punished after two warnings. This seems enough for me -- if \
people keep breaking stuff despite warnings, a little penalty is probably a good \
thing.</div><div><br></div><div>The proposed policy already goes out of its way to \
require two warnings for &quot;independent&quot; breakage, but it&#39;s not entirely \
clear what independent means here. If you commit three breakages that are technically \
unrelated on the same day, then you probably shouldn&#39;t be banned immediately. So \
I would suggest also making clear that the warnings should be sent at least a few \
days apart and that an initial penalty cannot happen until a few days apart the \
second warning.<br></div><div><br></div><div>That said, I agree with those who are \
saying that breaking things should be obvious, things like ignoring repoman and/or \
other CI messaging. If the breakage is non-obvious and hard to spot locally, then we \
should instead invest in tooling to make it more obvious. By &quot;ignoring&quot; \
here I do mean that there needs to be a reasonable timeout -- sometimes if I commit a \
change and get a CI alert after a few hours, it might be tricky due to \
work/family/whatever concerns to fix it within, say, 24 \
hours.</div><div><br></div><div>Regards,</div><div><br></div><div>Dirkjan<br></div></div></div>




[prev in list] [next in list] [prev in thread] [next in thread]