From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C359A138334 for ; Tue, 16 Oct 2018 18:26:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 638B6E08A5; Tue, 16 Oct 2018 18:26:03 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0676FE088B for ; Tue, 16 Oct 2018 18:26:02 +0000 (UTC) Received: from localhost (unknown [107.159.36.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: vdupras) by smtp.gentoo.org (Postfix) with ESMTPSA id 7F990335C39; Tue, 16 Oct 2018 18:26:00 +0000 (UTC) Date: Tue, 16 Oct 2018 14:25:55 -0400 From: Virgil Dupras To: gentoo-dev@lists.gentoo.org Cc: Ralph Seichter Subject: Re: [gentoo-dev] Is there any way I can help with pull requests? Message-Id: <20181016142555.b7fccaa65e445d462bdc52ac@gentoo.org> In-Reply-To: <9dd3a2f3-d6d3-caec-c166-9cae1bb3de0f@seichter.de> References: <1539453637.16746.5.camel@gentoo.org> <9dd3a2f3-d6d3-caec-c166-9cae1bb3de0f@seichter.de> Organization: Gentoo X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA256"; boundary="Signature=_Tue__16_Oct_2018_14_25_55_-0400_Dzy8hTc_k_p+9iqm" X-Archives-Salt: 558a924c-7346-4058-9eef-e5668f28222d X-Archives-Hash: e63b7e366f9061149ec9bd02847e7ec0 --Signature=_Tue__16_Oct_2018_14_25_55_-0400_Dzy8hTc_k_p+9iqm Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 13 Oct 2018 20:18:06 +0200 Ralph Seichter wrote: > Glancing at my own open pull requests, it looks different (opened 15 and > 25 days ago, respectively). That is not meant as criticism; it just seems > to me that the team members who process PRs have a lot on their plates. Maybe I can try to explain why your 3 PRs [1] are still opened. The "skel.ebuild" one is easy: global changes have to be discussed on gentoo-dev. That the mailing list was recently whitelisted makes this harder than it should for non-devs. I believe such PRs take us by surprise and we don't have an efficient process for them. Areas for enhancement. The milter-regex one is, I think, a result of miscommunicating intent. zlogene does a great job on PRs by going over nearly all of them to catch obvious style problems. That you corrected them is good, but it doesn't mean that it's going to be merged anytime soon because this package is a net-mail package. Someone from that project [2] is going to have merge it, not zlogene. This is a tricky problem because it's completely understandable that you expect a timely response to your correction, but ultimately, you'll have to nudge someone from the net-mail project. But to know why you don't get a timely response, you need to intimately understand Gentoo's inner dynamics, which you can't. So, you think we rudely ignore you. But we don't, you're just lost in a Kafkaesque maze! Then, we're left with your nginx-unit PR, which is part of the proxy-maint program. Normally, those are well handled. In this case, we have mgorny who doesn't seem to like your PR. Devs tend to trust mgorny's judgement. It doesn't mean that he's right in this instance, but it adds a level of difficulty to the PR. The next dev to review this PR will have to be extra thorough with it if it's going to infirm mgorny's judgement. This places it in the "tricky PRs" mental bucket for, I guess, many proxy-maint members and it means that easier PRs will be processed before it. Sorry, it seems that you picked a tough package to be proxied-maintainer for. As I hope to have demonstrated, there is no ill intent or even negligence in the result that you observe. It's just that our processes are complex and far from perfect, and the workload, significant. In the end, I think, the best thing to do in most cases is to ping a dev after a reasonable timeout. We're mostly well intended and will take steps to minimize frustrations when we're made aware of them. Regards, Virgil [1]: https://github.com/gentoo/gentoo/pulls/rseichter [2]: https://wiki.gentoo.org/wiki/Project:Net-Mail --Signature=_Tue__16_Oct_2018_14_25_55_-0400_Dzy8hTc_k_p+9iqm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEzxAa2B+saKTW8nfCbgMDJWya24wFAlvGLTMACgkQbgMDJWya 24w8jAgAsKFs7fgM+VWyGRcEdL0fA/JTJsYfbTNxGFuyViKaZBcWPQPbcu+QzU+j 4xY9IkcqVwnig1PWwLWlbTkHFY9wNUk07aLgQn0nWtwFgEn6ho/eY6rvgxqjsZD0 VUInZE/x34T2rdceN4ZnnhCOqAoylGRy3WIFlvL3dDufao5zuE4u3ZEeiQygtk4Y I86pOa5RXTr/vIrcLzznlN6+hrMsIt4qIUmskHr/6lwLT1v0SsGO076zasrVVhGc g2cpnnshLqM8x9Ti1puzuvik9kfNoTK9plpFw7n1aOwYhMiuMQcPn7BFb8kuqIKH +BxNLAoOpKEGmKkJoW3sl9h0Y15N1A== =4vdT -----END PGP SIGNATURE----- --Signature=_Tue__16_Oct_2018_14_25_55_-0400_Dzy8hTc_k_p+9iqm--