Content-type: text/plain; charset=us-ascii
Precedence: list
MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [alpine-devel] How to improve quality control for patch reviews
From: Chris Ely <tcely@icloud.com>
In-reply-to: <20180726141558.2d451763@ncopa-desktop.copa.dup.pw>
Date: Thu, 26 Jul 2018 16:27:31 -0400
Cc: Alpine Development <alpine-devel@lists.alpinelinux.org>
Content-transfer-encoding: quoted-printable
Message-id: <67E3C4D9-0183-45E7-8381-662CD7F54C4B@icloud.com>
References: <20180726141558.2d451763@ncopa-desktop.copa.dup.pw>
To: Natanael Copa <ncopa@alpinelinux.org>

> On Jul 26, 2018, at 8:15 AM, Natanael Copa <ncopa@alpinelinux.org> =
wrote:
>=20
> Any other ideas or thoughts?

I'd like to see more use of collaborators feature of GitHub for aports =
specifically. I sent my ideas for this in an earlier email. With a bit =
of automation we can turn GitHub into a sort of staging area where =
people can take a more active role before being given push access. As of =
right now, there's very little contributors can do with PRs as they =
aren't part of the alpinelinux organization.

I personally find having stale labels / reviews and no feedback very =
frustrating. So I'm very much in favor of expanding the pool of people =
who can provide feedback and adjust labels / review statuses.=


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---