This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Patch review by coworkers
- From: Florian Weimer <fweimer at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 27 Sep 2017 13:15:59 +0200
- Subject: Patch review by coworkers
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=fweimer at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 04C8185540
Hi,
Red Hat now has several people who regularly work on upstream glibc.
This raises questions regarding patch review.
Does the community expect that we Red Hatters deal with patches from
posting to commit, having colleagues doing the review etc.? The
argument in favor of that is that if something interests Red Hat, Red
Hat should throw resources at it, and not rely on the community to do
the work.
-or-
Does the community expect that we avoid patch review by coworkers? The
argument for that is that it avoids any incentive to game the review
system, and it puts community interests first.
Note that I'm talking about the ordinary day-to-day work here, not
patches we know or have reason to suspect to be controversial. And if
we err, we can still revert patches, of course.
Thanks,
Florian