public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Herb Miller Jr. <herb@hlmjr.com>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Begin a dev-libs/nodejs category?
Date: Wed, 21 Mar 2018 12:22:15 +0000	[thread overview]
Message-ID: <BLUPR17MB0273E901337C31401217A44BD9AA0@BLUPR17MB0273.namprd17.prod.outlook.com> (raw)
In-Reply-To: <20180321203335.17c9a2f5@katipo2.lan>

On 03/21/2018 03:33 AM, Kent Fredric wrote:
> On Wed, 21 Mar 2018 01:44:11 +0000
> Herb Miller Jr. <herb@hlmjr.com> wrote:
>
>> If I am, then yes, some kind of automation
>> would be the only sane way to keep up
> In my experience you can't *really* rely on automation 100% for this
> sort of thing. Not while achieving quality results.
>
> Its viable for an overlay where there's no expectations of quality, but
> for the main tree, I find you want to have a human san-check everything
> and manually vet each upstream version for "anomalous things".
>
> Automation is good at handling the "known predictable" cases, humans
> are better at detecting "huh, that's weird, why did they do that?"
>
> Because you absolutely want to know if upstream added some stupid
> change that is harmful to Gentoo users before you blindly replicate it.

And I agree with you 100%. I would never rely on automation exclusively.
I would use it to write boilerplate sections, check for updates, check
for breakage, etc. I'd never open a PR for something I hadn't polished
myself.



  reply	other threads:[~2018-03-21 12:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 11:50 [gentoo-dev] [RFC] Begin a dev-libs/nodejs category? Herb Miller Jr.
2018-03-20 18:34 ` Michał Górny
2018-03-20 19:43   ` Herb Miller Jr.
2018-03-20 18:48 ` Michael Orlitzky
2018-03-20 20:14   ` Herb Miller Jr.
2018-03-20 20:44     ` Michael Orlitzky
2018-03-21  1:27   ` Kent Fredric
2018-03-21  1:36     ` M. J. Everitt
2018-03-20 23:50 ` Benda Xu
2018-03-21  1:44   ` Herb Miller Jr.
2018-03-21  7:33     ` Kent Fredric
2018-03-21 12:22       ` Herb Miller Jr. [this message]
2018-03-21 10:07     ` X dej
2018-03-21 12:15       ` [gentoo-dev] Pypi generator (Was: [RFC] Begin a dev-libs/nodejs category?) Benda Xu

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=BLUPR17MB0273E901337C31401217A44BD9AA0@BLUPR17MB0273.namprd17.prod.outlook.com \
    --to=herb@hlmjr.com \
    --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