From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bradleyb@fuzziesquirrel.com>
Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized)
 smtp.mailfrom=fuzziesquirrel.com (client-ip=173.167.31.197;
 helo=bajor.fuzziesquirrel.com; envelope-from=bradleyb@fuzziesquirrel.com;
 receiver=<UNKNOWN>)
Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none)
 header.from=fuzziesquirrel.com
Received: from bajor.fuzziesquirrel.com (mail.fuzziesquirrel.com
 [173.167.31.197])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.ozlabs.org (Postfix) with ESMTPS id 4BrZZ00fVTzDqTk
 for <openbmc@lists.ozlabs.org>; Wed, 16 Sep 2020 06:28:38 +1000 (AEST)
X-Virus-Scanned: amavisd-new at fuzziesquirrel.com
Date: Tue, 15 Sep 2020 16:28:32 -0400
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: openbmc@lists.ozlabs.org
Subject: interest in a minimal image recipe
Message-ID: <20200915202832.rq3os62pdj7mzaco@thinkpad.fuzziesquirrel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
X-BeenThere: openbmc@lists.ozlabs.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Development list for OpenBMC <openbmc.lists.ozlabs.org>
List-Unsubscribe: <https://lists.ozlabs.org/options/openbmc>,
 <mailto:openbmc-request@lists.ozlabs.org?subject=unsubscribe>
List-Archive: <http://lists.ozlabs.org/pipermail/openbmc/>
List-Post: <mailto:openbmc@lists.ozlabs.org>
List-Help: <mailto:openbmc-request@lists.ozlabs.org?subject=help>
List-Subscribe: <https://lists.ozlabs.org/listinfo/openbmc>,
 <mailto:openbmc-request@lists.ozlabs.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2020 20:28:40 -0000

I've heard a handful of times that meta-phosphor users often have to 
remove the latest feature added by default to obmc-phosphor-image.

I have an RFC for an empty image that these users could bbappend and 
opt-in to specific image features instead of having to repeatedly 
opt-out.

If you like the opt-in approach, please drop a +1 and/or review my patch:

https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/36516

I bring this up now because I, and others have been adding new image 
features to obmc-phosphor-image (e.g. turned on by default), and I would 
like to start a discussion about what it means for an application to be 
in the OpenBMC github organization.  I would propose that it means it is 
enabled and turned on by default in obmc-phosphor-image.

Looking forward to your thoughts.

-brad