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 380301381F3 for ; Sun, 21 Apr 2013 15:07:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CFDEAE0BBB; Sun, 21 Apr 2013 15:07:40 +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 DCF1BE091F for ; Sun, 21 Apr 2013 15:07:39 +0000 (UTC) Received: from [192.168.1.4] (f055014176.adsl.alicedsl.de [78.55.14.176]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: chithanh) by smtp.gentoo.org (Postfix) with ESMTPSA id A743233DE43 for ; Sun, 21 Apr 2013 15:07:38 +0000 (UTC) Message-ID: <517400BD.3060809@gentoo.org> Date: Sun, 21 Apr 2013 17:07:41 +0200 From: =?UTF-8?B?Q2jDrS1UaGFuaCBDaHJpc3RvcGhlciBOZ3V54buFbg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in profiles: ChangeLog package.mask References: <20130419091632.D01152171D@flycatcher.gentoo.org> <20130419153043.30ffc50c@portable> <5173F9F7.6050100@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 7e031e33-a70d-4a00-8cad-fa5ab12df90c X-Archives-Hash: 207202c3b7672fc0aa9c027232b5e81e Denis Dupeyron schrieb: >> When someone asks about changing a package which someone else maintains, I >> always suggest reporting a bug about it. Do you think that is generally ok, >> or not the proper way to communicate? > > Exactly. Bugzilla is not a communication tool, > Communication is (in order of > effectivity) in-person meeting, phone, irc, email. But all comments in bugs are sent to the maintainer via email, at least in default settings. So in my opinion, the communication aspect of email is also included in bugzilla. > If you're not using > any of these tools you're not communicating effectively and you can't > expect things to go smoothly. I think that over direct email, bugzilla has the advantage of being visible in the public record. And in contrast to mailing lists, only interested parties will receive the messages. But if you think that is not the case, we can ask council to clarify whether a change announced in bugzilla counts as proper communication with the maintainer. Best regards, Chí-Thanh Christopher Nguyễn