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 611BF138350 for ; Wed, 26 Feb 2020 20:30:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2B82BE09C2; Wed, 26 Feb 2020 20:30:54 +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 01334E09C1 for ; Wed, 26 Feb 2020 20:30:53 +0000 (UTC) Received: from pomiot (c142-245.icpnet.pl [85.221.142.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 39E6234F1CE; Wed, 26 Feb 2020 20:30:52 +0000 (UTC) Message-ID: <6483c3bf40908a2d41f8534f66a8352694c034bd.camel@gentoo.org> Subject: Re: [gentoo-project] rfc: comrel changes From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-project@lists.gentoo.org Date: Wed, 26 Feb 2020 21:30:47 +0100 In-Reply-To: <20200226202235.GA25065@whubbs1.dev.av1.gaikai.org> References: <1c28039f9bf22ee07a473b8bfde840727db848e5.camel@gentoo.org> <20200226165439.GA19499@whubbs1.dev.av1.gaikai.org> <463d0a68d01bb03e7792d63c823f8c9ae32431f1.camel@gentoo.org> <20200226201317.GA24993@whubbs1.dev.av1.gaikai.org> <20200226202235.GA25065@whubbs1.dev.av1.gaikai.org> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-OD/b/ybLHSS3PE4pMWdI" User-Agent: Evolution 3.32.5 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: eed5f80e-8eb9-438b-aee4-973109dfb6a8 X-Archives-Hash: d5a7e15685d9ccde67ce1d8dfa31fcd9 --=-OD/b/ybLHSS3PE4pMWdI Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2020-02-26 at 14:22 -0600, William Hubbs wrote: > On Wed, Feb 26, 2020 at 02:13:17PM -0600, William Hubbs wrote: > > As I've said earlier in the thread, I'm not talking about bugs that are > > in process. I'm talking about bugs where nothing has started to happen. >=20 > So, if we don't want hard timeouts, is there another option? >=20 > My concern is when a reporter opens a bug then the bug sits there for an > extended period of time with no one addressing it. I agree there. Paradoxically, ComRel seems to have communication problems. All it really takes is making sure the user gets *some* response in time, be it 'we are looking into this, this will take some time, we will notice you as things progress'. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-OD/b/ybLHSS3PE4pMWdI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAl5W1XhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM3 NkE4NDUwOTQwOThEMjhDQzhCMjZDNTYzOUFEQUUyMzI5RTI0MEUACgkQY5ra4jKe JA5HRAf+PnIBBNsuyNjNkgWPXCQPvVTcmcYtJZoH7xaRDrld5ygUyuxKMgiRLtFE 2YndgkxINqJhaAmwJg2Q/Oepke3OMTz43jqb5zRI7spTE/gc9vtmj2M40llgDYIx 4fHdU8wZ+eajhZgRHV7HlxnNpaIVsRec48H/swepA42k1706rQycli3y3KYVJy0/ tKipSGesbekjEGytQ84sH9d1e400WY59AbV6EUOQXRfONqeuV3r5yw/vL9zVIHDf YOPexR3hukZtvMkXtRpQcjj9ORpqWuO/OKAet/RLqwSpEHs4o/wYkj+vfinadJzO 878oRldz1SHwtTarCPO4gZ4prWQZPA== =4dO3 -----END PGP SIGNATURE----- --=-OD/b/ybLHSS3PE4pMWdI--