Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=linux.intel.com (client-ip=134.134.136.126; helo=mga18.intel.com; envelope-from=james.feist@linux.intel.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.intel.com Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (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 47JKG01Kd8zDqpL for ; Thu, 21 Nov 2019 10:51:02 +1100 (AEDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Nov 2019 15:50:58 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,223,1571727600"; d="scan'208";a="237953991" Received: from skyhawk.jf.intel.com (HELO [10.54.51.81]) ([10.54.51.81]) by fmsmga002.fm.intel.com with ESMTP; 20 Nov 2019 15:50:57 -0800 Subject: Re: Redfish OpenBMC OEM To: Gunnar Mills , Joseph Reynolds , "openbmc@lists.ozlabs.org" Cc: jason.m.bills@linux.intel.com, apparao.puli@linux.intel.com References: <0967abf5-7eb4-8b72-2fe7-d8d4a95ca856@linux.intel.com> <5e21e041-aa40-f1a1-e4eb-9aed63db368a@linux.ibm.com> From: James Feist Message-ID: Date: Wed, 20 Nov 2019 15:50:57 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2019 23:51:05 -0000 On 11/20/19 2:45 PM, Gunnar Mills wrote: > > On 11/20/2019 11:47 AM, James Feist wrote: >> On 11/20/19 7:57 AM, Joseph Reynolds wrote: >>> On 11/19/19 1:04 PM, James Feist wrote: >>>> On 11/19/19 10:03 AM, Joseph Reynolds wrote: >>>>> On 11/19/19 10:23 AM, Gunnar Mills wrote: >>>>>> >>>>>> The process seems a little light for adding OpenBMC OEM Redfish >>>>>> properties and schemas. Can we establish a little more stringent >>>>>> process for adding these? >>>>>> >>> >>> Gunnar, does that begin to address your concern? > > I am most concerned with us adding these OpenBMC OEM schemas and > properties without first engaging the Redfish Group. > > James, Joseph, and others would you support having a guideline, stating > before adding an OEM schema or property, please first engage the Redfish > Group? Things Redfish is not interested in taking are an obvious > exception. I am also fine with things that are in the process of being > up-streamed, being added as OEM temporarily. What redfish group are you mentioning? > > > Thanks, > Gunnar >