From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id ECFF81381F3 for ; Sat, 22 Jun 2013 10:11:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4CB13E0A9D; Sat, 22 Jun 2013 10:11:19 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5500BE0A8C for ; Sat, 22 Jun 2013 10:11:18 +0000 (UTC) Received: from [192.168.1.204] (39.164.16.95.dynamic.jazztel.es [95.16.164.39]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 987D333DF72 for ; Sat, 22 Jun 2013 10:11:16 +0000 (UTC) Message-ID: <1371895873.30388.10.camel@localhost> Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Sat, 22 Jun 2013 12:11:13 +0200 In-Reply-To: References: <201306211940.03851.vapier@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.3 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-Transfer-Encoding: 8bit X-Archives-Salt: 3c326180-c76c-4c55-b0a1-30f8acb4ba0a X-Archives-Hash: e7f2d73bfc9bebf2914eb744b4010ad4 El sáb, 22-06-2013 a las 00:06 +0000, Robin H. Johnson escribió: [...] > I'm not going into review systems here at all, I'm simply trying to have > a policy of what changes are welcomed/blocked WITHOUT interaction from > the listed maintainer(s) of a given package/herd. [...] In my case I would like to be always notified a change has been committed (even forwarding gentoo-commits message to me), that will help me to keep track of the committed changes, and learn more if they corrected a bug caused by me ;) Regarding what other can commit or not... I think a general good policy would be to: 1. If package is not hardly broken -> report a bug to maintainer with a 1 week timeout. If he/she doesn't reply, go ahead. 2. If package is nonfunctional -> go ahead and fix it as soon as possible!