Date   

Re: DC-SCM 2.0 pinout rev 0.95 available on the wiki

Wang, Qian
 

One use case for 2nd NCSI is redundancy.  We are working on the spec, goal is to have an update in October.

Thanks,

Qian

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Chris Scott via groups.io
Sent: Thursday, September 16, 2021 3:03 PM
To: OCP-HWMgt-Module@OCP-All.groups.io
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

Thanks, Qian. I noticed two NCSI interfaces are called out in the pinout while one is called out in the latest draft of the v2.0 spec. What is the target use case?

 

Regards,

Chris

 


From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Wang, Qian via groups.io <qian.wang@...>
Sent: Wednesday, September 15, 2021 4:57 PM
To: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io>
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

Yes, the 2nd eSPI0* instance with P1 designation could be used for the 2nd node.  We will look into removing the ‘0’ in the name, same for QSPI0*.

Thanks,

Qian

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Chris Scott via groups.io
Sent: Wednesday, September 15, 2021 4:39 PM
To: OCP-HWMgt-Module@OCP-All.groups.io
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

In the dual-mode configuration, is eSPI_0 offered in two places on the connector, or is the 2nd instance (with the "P1" designation) supposed to be a 2nd eSPI interface? Please explain.

 

Thanks,

Chris

 


From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Qian Wang via groups.io <qian.wang@...>
Sent: Monday, September 13, 2021 10:31 AM
To: OCP-HWMgt-Module@ocp-all.groups.io <OCP-HWMgt-Module@ocp-all.groups.io>
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

 

On Mon, Sep 13, 2021 at 8:55 AM Qian Wang via groups.io <qian.wang=ocproject.net@groups.io> wrote:

Hello All,

 

This is the link for DC-SCM 2.0_pinout_rev0.95:

It is also posted on the wiki.  If you have any comments or questions, please let us know.

 

thanks,

Qian


Re: DC-SCM 2.0 pinout rev 0.95 available on the wiki

Chris Scott
 

Thanks, Qian. I noticed two NCSI interfaces are called out in the pinout while one is called out in the latest draft of the v2.0 spec. What is the target use case?

Regards,
Chris


From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Wang, Qian via groups.io <qian.wang@...>
Sent: Wednesday, September 15, 2021 4:57 PM
To: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io>
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki
 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Yes, the 2nd eSPI0* instance with P1 designation could be used for the 2nd node.  We will look into removing the ‘0’ in the name, same for QSPI0*.

Thanks,

Qian

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Chris Scott via groups.io
Sent: Wednesday, September 15, 2021 4:39 PM
To: OCP-HWMgt-Module@OCP-All.groups.io
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

In the dual-mode configuration, is eSPI_0 offered in two places on the connector, or is the 2nd instance (with the "P1" designation) supposed to be a 2nd eSPI interface? Please explain.

 

Thanks,

Chris

 


From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Qian Wang via groups.io <qian.wang@...>
Sent: Monday, September 13, 2021 10:31 AM
To: OCP-HWMgt-Module@ocp-all.groups.io <OCP-HWMgt-Module@ocp-all.groups.io>
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

 

On Mon, Sep 13, 2021 at 8:55 AM Qian Wang via groups.io <qian.wang=ocproject.net@groups.io> wrote:

Hello All,

 

This is the link for DC-SCM 2.0_pinout_rev0.95:

It is also posted on the wiki.  If you have any comments or questions, please let us know.

 

thanks,

Qian


Re: DC-SCM 2.0 pinout rev 0.95 available on the wiki

Wang, Qian
 

Yes, the 2nd eSPI0* instance with P1 designation could be used for the 2nd node.  We will look into removing the ‘0’ in the name, same for QSPI0*.

Thanks,

Qian

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Chris Scott via groups.io
Sent: Wednesday, September 15, 2021 4:39 PM
To: OCP-HWMgt-Module@OCP-All.groups.io
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

In the dual-mode configuration, is eSPI_0 offered in two places on the connector, or is the 2nd instance (with the "P1" designation) supposed to be a 2nd eSPI interface? Please explain.

 

Thanks,

Chris

 


From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Qian Wang via groups.io <qian.wang@...>
Sent: Monday, September 13, 2021 10:31 AM
To: OCP-HWMgt-Module@ocp-all.groups.io <OCP-HWMgt-Module@ocp-all.groups.io>
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 

 

On Mon, Sep 13, 2021 at 8:55 AM Qian Wang via groups.io <qian.wang=ocproject.net@groups.io> wrote:

Hello All,

 

This is the link for DC-SCM 2.0_pinout_rev0.95:

It is also posted on the wiki.  If you have any comments or questions, please let us know.

 

thanks,

Qian


Re: DC-SCM 2.0 pinout rev 0.95 available on the wiki

Chris Scott
 

In the dual-mode configuration, is eSPI_0 offered in two places on the connector, or is the 2nd instance (with the "P1" designation) supposed to be a 2nd eSPI interface? Please explain.

Thanks,
Chris


From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Qian Wang via groups.io <qian.wang@...>
Sent: Monday, September 13, 2021 10:31 AM
To: OCP-HWMgt-Module@ocp-all.groups.io <OCP-HWMgt-Module@ocp-all.groups.io>
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki
 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


On Mon, Sep 13, 2021 at 8:55 AM Qian Wang via groups.io <qian.wang=ocproject.net@groups.io> wrote:
Hello All,

This is the link for DC-SCM 2.0_pinout_rev0.95:
It is also posted on the wiki.  If you have any comments or questions, please let us know.

thanks,
Qian


Re: DC-SCM 2.0 pinout rev 0.95 available on the wiki

Chris Scott
 

Thanks for posting this, Qian. Are the definitions of the power states given anywhere? In particular, PRE-STBY vs. STBY vs. S5? I don't see them defined in this .xlsx or in the DC-SCM v2.0 (or v1.0) specs.

Regards,
Chris


From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Qian Wang via groups.io <qian.wang@...>
Sent: Monday, September 13, 2021 10:31 AM
To: OCP-HWMgt-Module@ocp-all.groups.io <OCP-HWMgt-Module@ocp-all.groups.io>
Subject: Re: [OCP-HWMgt-Module] DC-SCM 2.0 pinout rev 0.95 available on the wiki
 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


On Mon, Sep 13, 2021 at 8:55 AM Qian Wang via groups.io <qian.wang=ocproject.net@groups.io> wrote:
Hello All,

This is the link for DC-SCM 2.0_pinout_rev0.95:
It is also posted on the wiki.  If you have any comments or questions, please let us know.

thanks,
Qian


Re: DC-SCM 2.0 pinout rev 0.95 available on the wiki

Qian Wang
 

On Mon, Sep 13, 2021 at 8:55 AM Qian Wang via groups.io <qian.wang=ocproject.net@groups.io> wrote:
Hello All,

This is the link for DC-SCM 2.0_pinout_rev0.95:
It is also posted on the wiki.  If you have any comments or questions, please let us know.

thanks,
Qian


DC-SCM 2.0 pinout rev 0.95 available on the wiki

Qian Wang
 

Hello All,

This is the link for DC-SCM 2.0_pinout_rev0.95:
It is also posted on the wiki.  If you have any comments or questions, please let us know.

thanks,
Qian


Re: OCP 2021 Global summit Experience Center demo

Marshall Goldberg
 

Lattice would like to demonstrate a working, specification-compliant DC-SCM signal aggregation solution over LVDS.

 

We expect to be ready for a November demonstration.

 

Thank you,

Marshall Goldberg

Lattice Semiconductor, Inc.

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> on behalf of Qian Wang via groups.io <qian.wang@...>
Date: Monday, July 12, 2021 at 4:08 PM
To: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io>, Eric Shobe <eric.shobe@...>
Subject: [OCP-HWMgt-Module] OCP 2021 Global summit Experience Center demo

ATTENTION:: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

 


Hello all,

This is a call for HWMM demo participation at the Global summit this year in November.  We plan to have a HWMM booth in the Experience Center, anyone who has a RunBMC or DC-SCM module to demo is welcome to join us at the booth to showcase your design.

 

Regards,

Qian


OCP 2021 Global summit Experience Center demo

Qian Wang
 

Hello all,
This is a call for HWMM demo participation at the Global summit this year in November.  We plan to have a HWMM booth in the Experience Center, anyone who has a RunBMC or DC-SCM module to demo is welcome to join us at the booth to showcase your design.

Regards,
Qian


7/5 DC-SCM 2.0 workstream meeting canceled

Qian Wang
 

Hello all,
Friendly reminder that the HWMM DC-SCM 2.0 workstream meeting is cancelled due to US holiday.

Regards,
Qian


Cancelled Event: Hardware Management Modules Sub-Project meeting #cal-cancelled

OCP-HWMgt-Module@OCP-All.groups.io Calendar <noreply@...>
 

Cancelled: Hardware Management Modules Sub-Project meeting

This event has been cancelled.

When:
Monday, June 7, 2021
12:30pm to 1:30pm
(UTC-04:00) America/New York
Repeats: Monthly on the first Monday, 30 times

Organizer: OCP Hardware Management Project opencompute.org_0bjgh9s81nj0ph2utsr61j0lbg@...

Description:
Please join my meeting from your computer, tablet or smartphone.&nbsp;<br><a href="https://global.gotomeeting.com/join/454746381">https://global.gotomeeting.com/join/454746381</a>&nbsp;<br><br>You can also dial in using your phone.&nbsp;<br>United States: +1 (646) 749-3112&nbsp;<br><br>Access Code: 454-746-381&nbsp;<br><br>Joining from a video-conferencing room or system?&nbsp;<br>Dial: 67.217.95.2##454746381&nbsp;<br>Cisco devices: <a href="mailto:454746381@...">454746381@...</a>&nbsp;<br><br>First GoToMeeting? Let's do a quick system check: <a href="https://link.gotomeeting.com/system-check">https://link.gotomeeting.com/system-check</a>&nbsp;

-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
Please do not edit this section of the description.

View your event at https://calendar.google.com/calendar/event?action=VIEW&eid=ZjRvOHA3NmZuMnZ2cnZ2dHVkZDBqZzNxOHIgb2NwLWh3bWd0LW1vZHVsZUBvY3AtYWxsLmdyb3Vwcy5pbw&tok=Njgjb3BlbmNvbXB1dGUub3JnXzBiamdoOXM4MW5qMHBoMnV0c3I2MWowbGJnQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb205ZDEwNWU2Y2I5NDg5YWZjODVjOTU1NjlmY2E1OTE5MTI1MjQ5ZGNj&ctz=America%2FChicago&hl=en&es=1.
-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-


Re: DC-SCM FSI Proposal

Steve Roberts
 

I do not see the ESPI and FSI in the same systems.  So if the implication is to head the, its it ok for discussion.

However, the other observation is the number of dedicated pins for both ESPI and QSPI.  If these are not used concurrently, there are enough pins there to put on a 2nd NCSI as an alternative function.



On Mon, Jun 21, 2021, 12:25 PM Dube, Shawn <shawn.dube@...> wrote:

 

Steven,

 

Do you see FSI as a replacement for eSPI for different CPUs, or as a compliment to eSPI with both being used concurrently?

 

-Shawn

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Steve Roberts
Sent: Monday, June 21, 2021 9:56 AM
To: OCP-HWMgt-Module@ocp-all.groups.io
Subject: [OCP-HWMgt-Module] DC-SCM FSI Proposal

 

[EXTERNAL EMAIL]

 

With the CLA signatures coming in and the new DC-SCM v2 pin count, I wanted to jump back to the FSI discussion so we can see that in the PIN list.

 

Per the proposal, I'm looking for the FSI signals to be listed as alternates on I3C buses 3&4 (A49,A50,A51,A52)

   --- ideally, we'd like that to also list 1.2V with that alternate mapping since ASPEED and FPGAs easily support this

 

Steven

 

 

Internal Use - Confidential


Re: DC-SCM FSI Proposal

Dube, Shawn
 

 

Steven,

 

Do you see FSI as a replacement for eSPI for different CPUs, or as a compliment to eSPI with both being used concurrently?

 

-Shawn

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Steve Roberts
Sent: Monday, June 21, 2021 9:56 AM
To: OCP-HWMgt-Module@ocp-all.groups.io
Subject: [OCP-HWMgt-Module] DC-SCM FSI Proposal

 

[EXTERNAL EMAIL]

 

With the CLA signatures coming in and the new DC-SCM v2 pin count, I wanted to jump back to the FSI discussion so we can see that in the PIN list.

 

Per the proposal, I'm looking for the FSI signals to be listed as alternates on I3C buses 3&4 (A49,A50,A51,A52)

   --- ideally, we'd like that to also list 1.2V with that alternate mapping since ASPEED and FPGAs easily support this

 

Steven

 

 

Internal Use - Confidential


DC-SCM FSI Proposal

Steve Roberts
 


With the CLA signatures coming in and the new DC-SCM v2 pin count, I wanted to jump back to the FSI discussion so we can see that in the PIN list.

Per the proposal, I'm looking for the FSI signals to be listed as alternates on I3C buses 3&4 (A49,A50,A51,A52)
   --- ideally, we'd like that to also list 1.2V with that alternate mapping since ASPEED and FPGAs easily support this

Steven


Today's HWMM meeting

Qian Wang
 

Hello all,
Please us this link for today's meeting, this is also on the calendar:

WhenMon, June 7, 9:30am – 10:30am
DescriptionThis call is open to the public and will be recorded and shared publicly. 

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/594376349

You can also dial in using your phone.
United States (Toll Free): 1 877 309 2073
United States: +1 (646) 749-3129

Access Code: 594-376-349

More phone numbers:
Argentina (Toll Free): 0 800 444 3375
Australia (Toll Free): 1 800 193 385
Austria (Toll Free): 0 800 202148
Bahrain (Toll Free): 800 81 111
Belarus (Toll Free): 8 820 0011 0400
Belgium (Toll Free): 0 800 78884
Brazil (Toll Free): 0 800 047 4906
Bulgaria (Toll Free): 00800 120 4417
Canada (Toll Free): 1 888 455 1389
Chile (Toll Free): 800 395 150
China (Toll Free): 4000 762962
Colombia (Toll Free): 01 800 518 4483
Costa Rica (Toll Free): 0800 542 5405
Czech Republic (Toll Free): 800 500448
Denmark (Toll Free): 8025 3126
Finland (Toll Free): 0 800 917656
France (Toll Free): 0 805 541 047
Germany (Toll Free): 0 800 184 4222
Greece (Toll Free): 00 800 4414 3838
Hong Kong (Toll Free): 30713169
Hungary (Toll Free): (06) 80 986 255
Iceland (Toll Free): 800 7204
India (Toll Free): 18002126633
Indonesia (Toll Free): 007 803 020 5375
Ireland (Toll Free): 1 800 901 610
Israel (Toll Free): 1 809 454 830
Italy (Toll Free): 800 793887
Japan (Toll Free): 0 120 663 800
Korea, Republic of (Toll Free): 00798 14 207 4914
Luxembourg (Toll Free): 800 29519
Malaysia (Toll Free): 1 800 81 6854
Mexico (Toll Free): 800 522 11 33
Netherlands (Toll Free): 0 800 020 0182
New Zealand (Toll Free): 0 800 44 5550
Norway (Toll Free): 800 69 046
Panama (Toll Free): 00 800 226 7928
Peru (Toll Free): 0 800 76913
Philippines (Toll Free): 1 800 1110 1661
Poland (Toll Free): 00 800 1124759
Portugal (Toll Free): 800 819 575
Romania (Toll Free): 0 800 400 819
Russian Federation (Toll Free): 8 800 100 6203
Saudi Arabia (Toll Free): 800 844 3633
Singapore (Toll Free): 18007231323
Slovakia (Toll Free): 0 800 105 748
.
Dial in or type: 67.217.95.2 or inroomlink.goto.com
Meeting ID: 594 376 349
Or dial directly: 594376349@... or 67.217.95.2##594376349

New to GoToMeeting? Get the app now and be ready when your first meeting starts: https://global.gotomeeting.com/install/594376349


Invitation: Monthly DC-SCM 2.0 Workstream - Public Update @ Monthly from 11:30am to 12:30pm on the first Monday (CDT) (ocp-hwmgt-module@ocp-all.groups.io)

Michael Schill
 

You have been invited to the following event.

Monthly DC-SCM 2.0 Workstream - Public Update

When
Monthly from 11:30am to 12:30pm on the first Monday Central Time - Chicago
Calendar
ocp-hwmgt-module@ocp-all.groups.io
Who
Michael Schill - creator
ocp-hwmgt-module@ocp-all.groups.io
This call is open to the public and will be recorded and shared publicly. 

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/594376349

You can also dial in using your phone.
United States (Toll Free): 1 877 309 2073
United States: +1 (646) 749-3129

Access Code: 594-376-349

More phone numbers:
Argentina (Toll Free): 0 800 444 3375
Australia (Toll Free): 1 800 193 385
Austria (Toll Free): 0 800 202148
Bahrain (Toll Free): 800 81 111
Belarus (Toll Free): 8 820 0011 0400
Belgium (Toll Free): 0 800 78884
Brazil (Toll Free): 0 800 047 4906
Bulgaria (Toll Free): 00800 120 4417
Canada (Toll Free): 1 888 455 1389
Chile (Toll Free): 800 395 150
China (Toll Free): 4000 762962
Colombia (Toll Free): 01 800 518 4483
Costa Rica (Toll Free): 0800 542 5405
Czech Republic (Toll Free): 800 500448
Denmark (Toll Free): 8025 3126
Finland (Toll Free): 0 800 917656
France (Toll Free): 0 805 541 047
Germany (Toll Free): 0 800 184 4222
Greece (Toll Free): 00 800 4414 3838
Hong Kong (Toll Free): 30713169
Hungary (Toll Free): (06) 80 986 255
Iceland (Toll Free): 800 7204
India (Toll Free): 18002126633
Indonesia (Toll Free): 007 803 020 5375
Ireland (Toll Free): 1 800 901 610
Israel (Toll Free): 1 809 454 830
Italy (Toll Free): 800 793887
Japan (Toll Free): 0 120 663 800
Korea, Republic of (Toll Free): 00798 14 207 4914
Luxembourg (Toll Free): 800 29519
Malaysia (Toll Free): 1 800 81 6854
Mexico (Toll Free): 800 522 11 33
Netherlands (Toll Free): 0 800 020 0182
New Zealand (Toll Free): 0 800 44 5550
Norway (Toll Free): 800 69 046
Panama (Toll Free): 00 800 226 7928
Peru (Toll Free): 0 800 76913
Philippines (Toll Free): 1 800 1110 1661
Poland (Toll Free): 00 800 1124759
Portugal (Toll Free): 800 819 575
Romania (Toll Free): 0 800 400 819
Russian Federation (Toll Free): 8 800 100 6203
Saudi Arabia (Toll Free): 800 844 3633
Singapore (Toll Free): 18007231323
Slovakia (Toll Free): 0 800 105 748
.
Dial in or type: 67.217.95.2 or inroomlink.goto.com
Meeting ID: 594 376 349
Or dial directly: 594376349@... or 67.217.95.2##594376349

New to GoToMeeting? Get the app now and be ready when your first meeting starts: https://global.gotomeeting.com/install/594376349

Going (ocp-hwmgt-module@ocp-all.groups.io)?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account ocp-hwmgt-module@ocp-all.groups.io because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More.


Re: DC-SCM2.0 CLA process change

Qian Wang
 

Hello all,

Thank you all for your patience as we refine this process.

 

In the May 17th HW Mgmt Module meeting, the process described was that prospective signers could assess their level of contribution and sign the CLA.


However, the OCP process for collaboration requires approval of a candidate for signature before sending the CLA to be signed.

 

The project lead(s) normally provides the approval.  Intel does not believe it should be the sole gatekeeper and a more open governance model should be used for approval.  However, I will manage the approval request process, please send the joining request to me.  To that end, a core group would approve additional members who could sign the CLA.

 

The original intent of moving the DC-SCM 2.0 work into OCP was that the original 4 companies wanted to add two more members. But wanted to do so within an IP framework. OCP provided that framework.  The proposal is to

·       Designate these 6 companies as the core group which are approved to sign the CLA.  These are: Microsoft, Google, Intel, DellEMC, HPE and IBM

The core group could be called the TSC - technical steering committee in open-source governance

·       That signed-CLAs from 3 companies is sufficient to establish the core group

·       That the core group approves additional companies to join the core group. The approval is by consensus, until other voting rules are established.

·       That the criteria include the understanding of a company's exact contribution to the DC-SCM 2.0 Spec (already available or planned).

 

Updates to the specification will be provided on the HWMM monthly calls and on the wiki.  The Tracker sheet will continue to be available for submitting opens.

 

Regards,

Qian


Re: DC-SCM2.0 CLA process change

Stuewe, John
 

Tony,

 

Archna Haylock <archna@...>   can send them to you.

 

John Stuewe

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Hsu.Tony ??? ISV
Sent: Monday, May 17, 2021 8:50 PM
To: OCP-HWMgt-Module@OCP-All.groups.io
Subject: Re: [OCP-HWMgt-Module] DC-SCM2.0 CLA process change

 

[EXTERNAL EMAIL]

All

 

Does anyone know where to get CLA/FSA or link to the CLA/FSA?

 

Thanks

tony

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Qian Wang
Sent: Tuesday, May 11, 2021 6:19 PM
To: OCP-HWMgt-Module@ocp-all.groups.io
Subject: [OCP-HWMgt-Module] DC-SCM2.0 CLA process change

 

Hello all,

 

This email is intended for the DC-SCM 2.0 specification development participants.

 

Archna clarified the use of the two agreements (the CLA and FSA) for the work of the HWMM sub-project. The CLAs (Contributor License) are required to protect those contributing to the specification and the FSA (Final Spec) protects the users of the specification.  The following is the proper usage of the CLA and FSA -  per the other projects.

 

  • Those wishing to contribute and discuss the Specification
    • Need to sign the CLA which Archna will provide – the CLA should be familiar to most of your legal departments
    • The companies who sign the CLA can meet and contribute to the Specification
      • To move quickly on the CLA, please let me know if you plan to sign it ASAP. 
    • Issue and resolution tracking will continue to be available on the wiki.  The specification update drafts will be posted on the wiki monthly
    • The CLA is also required for the workstreams, which will be rehosted as OCP meetings to give them the proper IP framework
  • The HWMM sub-project meetings will be rescheduled to once a month to report out updates (no CLAs needed for this)
    • The HWMM will also report out at the monthly HW Mgmt Project meeting, as it currently does
  • Upon completion of the specification, the CLA signers are encouraged to sign the FSA.

 

This process change will be the topic of the May 17th meeting. The intent is to restart the meetings when a definitive number of companies have signed the CLA.  The number will be decided on May 17 - my proposal is 3. 

 

Thanks,

Qian

 



Confidentiality Note

本郵件含有英業達股份有限公司機密資訊、或受法律保護之資料,唯有原發信人指定之收信人得閱讀或使用本郵件之內容。如您並非被指定之收信人,請立即將本郵件及所有附件予以刪除;請勿揭露、儲存或使用本郵件之任何資訊,並請您立即告知原發信人本郵件的傳遞錯誤。謝謝您的合作。
This e-mail transmission and any attachments contain information from Inventec Corporation. The information is confidential and/or privileged and intended to be solely for the use of the individuals or entities named in this e-mail transmission. If you are not the intended recipient, be aware that any disclosure, saving or use of the content of this e-mail transmission and attachments is strictly prohibited. If you have received this email transmission in error, please notify us immediately, and delete the e-mail and attachments. We greatly appreciate your cooperation.


Re: DC-SCM2.0 CLA process change

Hsu.Tony 許昭賢 ISV
 

All

 

Does anyone know where to get CLA/FSA or link to the CLA/FSA?

 

Thanks

tony

 

From: OCP-HWMgt-Module@OCP-All.groups.io <OCP-HWMgt-Module@OCP-All.groups.io> On Behalf Of Qian Wang
Sent: Tuesday, May 11, 2021 6:19 PM
To: OCP-HWMgt-Module@ocp-all.groups.io
Subject: [OCP-HWMgt-Module] DC-SCM2.0 CLA process change

 

Hello all,

 

This email is intended for the DC-SCM 2.0 specification development participants.

 

Archna clarified the use of the two agreements (the CLA and FSA) for the work of the HWMM sub-project. The CLAs (Contributor License) are required to protect those contributing to the specification and the FSA (Final Spec) protects the users of the specification.  The following is the proper usage of the CLA and FSA -  per the other projects.

 

  • Those wishing to contribute and discuss the Specification
    • Need to sign the CLA which Archna will provide – the CLA should be familiar to most of your legal departments
    • The companies who sign the CLA can meet and contribute to the Specification
      • To move quickly on the CLA, please let me know if you plan to sign it ASAP. 
    • Issue and resolution tracking will continue to be available on the wiki.  The specification update drafts will be posted on the wiki monthly
    • The CLA is also required for the workstreams, which will be rehosted as OCP meetings to give them the proper IP framework
  • The HWMM sub-project meetings will be rescheduled to once a month to report out updates (no CLAs needed for this)
    • The HWMM will also report out at the monthly HW Mgmt Project meeting, as it currently does
  • Upon completion of the specification, the CLA signers are encouraged to sign the FSA.

 

This process change will be the topic of the May 17th meeting. The intent is to restart the meetings when a definitive number of companies have signed the CLA.  The number will be decided on May 17 - my proposal is 3. 

 

Thanks,

Qian




Confidentiality Note

本郵件含有英業達股份有限公司機密資訊、或受法律保護之資料,唯有原發信人指定之收信人得閱讀或使用本郵件之內容。如您並非被指定之收信人,請立即將本郵件及所有附件予以刪除;請勿揭露、儲存或使用本郵件之任何資訊,並請您立即告知原發信人本郵件的傳遞錯誤。謝謝您的合作。
This e-mail transmission and any attachments contain information from Inventec Corporation. The information is confidential and/or privileged and intended to be solely for the use of the individuals or entities named in this e-mail transmission. If you are not the intended recipient, be aware that any disclosure, saving or use of the content of this e-mail transmission and attachments is strictly prohibited. If you have received this email transmission in error, please notify us immediately, and delete the e-mail and attachments. We greatly appreciate your cooperation.


DC-SCM2.0 CLA process change

Qian Wang
 

Hello all,


This email is intended for the DC-SCM 2.0 specification development participants.


Archna clarified the use of the two agreements (the CLA and FSA) for the work of the HWMM sub-project. The CLAs (Contributor License) are required to protect those contributing to the specification and the FSA (Final Spec) protects the users of the specification.  The following is the proper usage of the CLA and FSA -  per the other projects.

 

  • Those wishing to contribute and discuss the Specification
    • Need to sign the CLA which Archna will provide – the CLA should be familiar to most of your legal departments
    • The companies who sign the CLA can meet and contribute to the Specification
      • To move quickly on the CLA, please let me know if you plan to sign it ASAP. 
    • Issue and resolution tracking will continue to be available on the wiki.  The specification update drafts will be posted on the wiki monthly
    • The CLA is also required for the workstreams, which will be rehosted as OCP meetings to give them the proper IP framework
  • The HWMM sub-project meetings will be rescheduled to once a month to report out updates (no CLAs needed for this)
    • The HWMM will also report out at the monthly HW Mgmt Project meeting, as it currently does
  • Upon completion of the specification, the CLA signers are encouraged to sign the FSA.

 

This process change will be the topic of the May 17th meeting. The intent is to restart the meetings when a definitive number of companies have signed the CLA.  The number will be decided on May 17 - my proposal is 3. 


Thanks,

Qian

1 - 20 of 46