public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Proposal: change to default policy of doing changes to packages that are maintained by other developers
Date: Mon, 21 Oct 2019 17:58:51 -0700	[thread overview]
Message-ID: <CAEdQ38GZ+jXtoxCUiV+ZAc-WPWXR=Rj4DyOhq+-YJh0zxvYLVA@mail.gmail.com> (raw)
In-Reply-To: <20191022133642.41590ee5@katipo2.lan>

On Mon, Oct 21, 2019 at 5:37 PM Kent Fredric <kentnl@gentoo.org> wrote:
>
> On Mon, 21 Oct 2019 19:37:28 +0200
> Piotr Karbowski <slashbeast@gentoo.org> wrote:
>
> > This is a bit unhealthy, especially when some developers that maintain
> > packages are out of reach, or the patches to update ebuild just rot on
> > the bugzilla and are not taken in by maintainers.
>
> IME this is far from the norm and should not be used as the
> justification here.

I think exceptional cases are the reason for many, many policies in
Gentoo. That probably doesn't surprise you.

> If you don't have the patience to even wait _one_ day for a response,
> maybe you shouldn't be doing opensource.

I'm not sure what this is in reference to so it seems to be a
non-sequitur, but I like the policy of at least waiting a day for
review of non-critical fixes. Phrased another way, let people in every
timezone have a chance.


  reply	other threads:[~2019-10-22  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 17:37 [gentoo-dev] Proposal: change to default policy of doing changes to packages that are maintained by other developers Piotr Karbowski
2019-10-21 18:06 ` Matthew Thode
2019-10-22  0:36 ` Kent Fredric
2019-10-22  0:58   ` Matt Turner [this message]
2019-10-22  4:07     ` Kent Fredric
2019-10-22  0:55 ` Matt Turner

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='CAEdQ38GZ+jXtoxCUiV+ZAc-WPWXR=Rj4DyOhq+-YJh0zxvYLVA@mail.gmail.com' \
    --to=mattst88@gentoo.org \
    --cc=gentoo-dev@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