Redfish OpenBMC OEM

[James Feist]

On 11/21/19 7:39 AM, Gunnar Mills wrote:
> 
> On 11/20/2019 5:50 PM, James Feist wrote:
>> 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?
>>>>>>>>
>>>
>>> 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?
>>
> 
> DMTF’s Redfish
> 
> They have an open forum here,  to ask questions and request features: 
> https://redfishforum.com/
> 
> To get access to the Redfish code repository and meetings
> 1) Your company must be a Redfish Supporter or Promoter, a lot of 
> companies working on OpenBMC are
> 2) Join the DMTF, www.dmtf.org/join
> 3) Join the "Redfish Forum" working group, 
> https://members.dmtf.org/apps/org/workgroup/portal/
> 4) Send an email asking for access to the Redfish code repository
> 
> I was thinking either of these would establish "engaging Redfish".

I'd be fine with adding this to the docs/readme, however as your company 
has to be a supporter, it should probably be a weak requirement.

> 
> Thanks,
> Gunnar