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 8EBF41387FD for ; Sat, 29 Mar 2014 14:06:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 555D8E0A7D; Sat, 29 Mar 2014 14:06:22 +0000 (UTC) Received: from virtual.dyc.edu (mail.virtual.dyc.edu [67.222.116.22]) by pigeon.gentoo.org (Postfix) with ESMTP id B9B9CE0A60 for ; Sat, 29 Mar 2014 14:06:21 +0000 (UTC) Received: from [192.168.3.7] (cpe-74-77-145-97.buffalo.res.rr.com [74.77.145.97]) by virtual.dyc.edu (Postfix) with ESMTPSA id 40D857E000B for ; Sat, 29 Mar 2014 10:06:21 -0400 (EDT) Message-ID: <5336D386.6080609@opensource.dyc.edu> Date: Sat, 29 Mar 2014 10:07:02 -0400 From: "Anthony G. Basile" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.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] Call for agenda items - Council meeting 2014-04-08 References: <53342A5F.70903@gentoo.org> <20140329143051.791839e6@gentoo.org> In-Reply-To: <20140329143051.791839e6@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: f5cfa22b-d9bf-4784-aaa2-0fde0bcb70d6 X-Archives-Hash: d30b36eeac93fb47556f8cca92e0f7da On 03/29/2014 09:30 AM, Tom Wijsman wrote: > On Sat, 29 Mar 2014 08:50:36 -0400 > "Anthony G. Basile" wrote: > >> Okay I'd like to add an agenda item. A policy inspired by bug >> #506034. > > (PS: Bug #506114 could be relevant to your item) > > Same here, let's take this a step further and extend this to profiles. > A policy inspired by bug #435094 and bug #506142. > >> Motion: "Significant changes to virtuals are to be discussed (via >> mailing list or bugzilla) with all the maintainers and/or herds which >> maintain packages those virtuals depend on." > > Motion: "Significant changes to profiles are to be discussed (via > mailing list or bugzilla) with all the maintainers and/or herds that > rely on what gets changed in the profiles." > >> Discussion: "Like eclasses, changes to virtuals can affect all the >> packages which depend on them. Changing existing virtuals, removing >> virtuals or adding new ones affect the packages they depend on. When >> such a change is proposed, all maintainers affected need to be >> included in the discussion." > > Discussion: "Like eclasses and virtuals, changes to the profiles affect > a set of packages at once. For instance, adding or removing a mask or > force can result in something becoming forced or optional. If something > is assumed to be forced, or optional; it can result in breakage, we > would like to prevent huge breakage. When such change is proposed, all > maintainers affected need to be included in the discussion." > > Concern: "Unawareness, possible breakage and a lack of cooperation." > Tom, I agree. This does seem like a good idea. An example here are some of the ABI variables that were introduced. I maintain some profiles which stack differently than default/linux/amd64/13.0 and getting a heads up about changes in the layers of the default profiles would have helped. -- Anthony G. Basile, Ph. D. Chair of Information Technology D'Youville College Buffalo, NY 14201 (716) 829-8197