From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [PATCH v2] glep-0048: Provide clear rules for disciplinary actions
Date: Fri, 26 Apr 2019 16:38:54 +0200 [thread overview]
Message-ID: <20190426163854.37925e6e@gentoo.org> (raw)
In-Reply-To: <20190423173410.8531-1-mgorny@gentoo.org>
On Tue, 23 Apr 2019 19:34:10 +0200
Michał Górny <mgorny@gentoo.org> wrote:
[...]
> Secondly, it suggests that the only disciplinary action
> possible would be 're-evaluating commits rights' which sounds like
> an euphemism for removing commit access permanently.
:=)
politically correct!
[...]
> + negatively impact the behavior of Gentoo systems, work of other
> developers
> + or infrastructure facilities), the QA team may issue a temporary
> revocation
> + of developer's commit access (ban). In case of repeated offenses,
> the QA
> + team may request that ComRel re-evaluates the commit access. All
> + the evidence of the violation, as well as ban length will be
> evaluated
> + by the QA team for each case individually. The disciplinary
> decisions made
> + by the QA team are subject to appeal via the council.
I would add maximum amounts of time everywhere here: For the QA ban
because this effectively still leaves room for "age of the universe"
long bans and a slightly shorter one for the comrel response to ensure
no important ban is missed due to people being on vacations.
Depending on that maximum, council appeal may not be needed because
it'd take longer than the ban length anyway.
next prev parent reply other threads:[~2019-04-26 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 17:34 [gentoo-project] [PATCH v2] glep-0048: Provide clear rules for disciplinary actions Michał Górny
2019-04-26 14:38 ` Alexis Ballier [this message]
2019-04-27 1:21 ` Chí-Thanh Christopher Nguyễn
2019-04-27 1:47 ` Raymond Jennings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190426163854.37925e6e@gentoo.org \
--to=aballier@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox