From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC] Undertakers: appeal policy
Date: Sat, 28 Sep 2019 13:26:41 +0200 [thread overview]
Message-ID: <443f0e87f4fe579891d23809d46acbd6caf14bb8.camel@gentoo.org> (raw)
In-Reply-To: <H6PGQQD7.4MS5L7HR.PS6TA2RI@LBUFA6JC.KUWNTPGM.YD7PCIIT>
[-- Attachment #1: Type: text/plain, Size: 3074 bytes --]
On Sat, 2019-09-28 at 10:53 +0100, Roy Bamford wrote:
> On 2019.09.21 08:01, Michał Górny wrote:
> > Hi, everyone.
> >
> > Since we currently don't explicitly indicate the appeal procedure
> > for Undertaker actions, I'd like to propose adding the following to
> > our
> > wiki page.
> >
> > TL;DR: Potential retirements can be appealed <1 mo before execution
> > (or
> > post execution), with ComRel being the first appeal instance,
> > and Council being the second.
> >
> >
> > Full proposed policy, with rationale:
> >
> > 1. Both pending and past retirements can be appealed to ComRel.
> > The ComRel decision can be further appealed to the Council.
> >
> > R: ComRel is a parent project for Undertakers, so it seems reasonable
> > to
> > make it the first appeal instance.
> >
> >
> > 2. Pending retirements can be appealed no earlier than one month
> > before
> > planned execution date (i.e. no earlier than after receiving third-
> > mail).
> >
> > R: This is meant to prevent premature appeals while Undertakers would
> > not retire the developer anyway (e.g. due to new activity).
> > Undertakers
> > recheck activity while sending third mail, so that's a good point to
> > confirm that someone's retirement is still pending.
> >
> >
> > 3. Throughout the appeal process, the pending retirement is suspended.
> >
> > If the appeal occurs post retirement, the developer remains retired
> > throughout the appeal process. The appeal process is finished if
> > either:
> >
> > a. the Council issues final decision,
> >
> > b. the ComRel decision is not appealed further within 7 days,
> >
> > c. both sides agree not to appeal further.
> >
> > R: We obviously want to avoid ping-pong of retiring, then unretiring
> > (then maybe retiring again).
> >
> >
> > 4. The appeal process is meant to resolve disagreements between
> > Undertakers and developers. It is not a replacement for communicating
> > with Undertakers.
> >
> > R: We don't want people to appeal everything without even trying to
> > resolve it between us. For example, if we missed something, then you
> > should tell us rather than calling for appeal. However, if we do
> > disagree on whether something counts as sufficient activity, this is
> > something you can appeal.
> >
> >
> > 5. The appeal process resolves each case individually based on
> > existing
> > policies. While it may influence future policies, those need to be
> > carried out via appropriate policy making channels.
> >
> > R: In other words, appeals don't change policies silently. If a
> > policy
> > needs to be changed, it must follow proper channel with ml review.
> >
> >
> > WDYT?
> >
> > --
> > Best regards,
> > Michał Górny
> >
> >
>
> Michał,
>
> Looks good. It also looks like the standard process so does it
> need to be documented explicitly on the Undertakers page?
>
Given that one person already asked about it, I supposed it does.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2019-09-28 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 7:01 [gentoo-project] [RFC] Undertakers: appeal policy Michał Górny
2019-09-21 9:55 ` [gentoo-project] " James Le Cuirot
2019-09-21 13:54 ` Richard Yao
2019-09-21 18:36 ` Rich Freeman
2019-09-21 18:48 ` Michał Górny
2019-09-21 19:43 ` James Le Cuirot
2019-09-21 22:22 ` Aaron Bauman
2019-09-28 9:53 ` [gentoo-project] " Roy Bamford
2019-09-28 11:26 ` Michał Górny [this message]
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=443f0e87f4fe579891d23809d46acbd6caf14bb8.camel@gentoo.org \
--to=mgorny@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