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 F177313877A for ; Fri, 1 Aug 2014 18:27:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F3AA5E094E; Fri, 1 Aug 2014 18:27:24 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6804AE0935 for ; Fri, 1 Aug 2014 18:27:24 +0000 (UTC) Received: from [192.168.1.100] (mobile-internet-5d6aa8-209.dhcp.inet.fi [93.106.168.209]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ssuominen) by smtp.gentoo.org (Postfix) with ESMTPSA id CBC6B33FABB for ; Fri, 1 Aug 2014 18:27:22 +0000 (UTC) Message-ID: <53DBDBF8.5060007@gentoo.org> Date: Fri, 01 Aug 2014 21:27:04 +0300 From: Samuli Suominen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 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 MIME-Version: 1.0 To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Re: Call for agenda items - Council meeting 2014-08-12 References: <21463.26330.847055.224071@a1i15.kph.uni-mainz.de> <20140731211239.0eb282cb@pomiot.lan> <53DBC854.9000607@gentoo.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 7693378e-aa6d-4568-81c7-42d6320447b0 X-Archives-Hash: 81f3b0ea04fc51b795e6547e22b8208f On 01/08/14 20:23, Michael Palimaka wrote: > On 08/02/2014 03:03 AM, hasufell wrote: >> Michael Palimaka: >>> but we need something [...] to avoid unnecessary rebuilds. >>> >> People are already working on it. Join them if you find that it's an >> important issue instead of forcing council votes that rather discourage >> further efforts. >> >> > Where are they working on it? We wouldn't have half this issue in the > first place if things were happening out in the open instead of behind > closed doors. > > The workflow seems to have been... 1. Declare dynamic deps a /bug/ 2. Tell people it will be disabled by force, without getting council involved, and be quite rude about it... 3. Work on some replacement for the feature, development done mostly silently, in a way most people didn't even know about it When it should have been... 1. Work on some replacement for the feature, announce some design specifics of it in the ML, and explain it will be the replacement for the dynamic deps which will be disabled as redudant. Get people involved with good spirits. (The above message is written as approx. and is not to be taken literally or as an offense of anykind. Just saying there was no need to get people up in arms if the plan was to provide replacing feature all along.) - Samuli