Hi Everyone, There are two calls scheduled on Monday, 7/18. 9am PST – Specification - Close on public comments - https://wiki.linuxfoundation.org/openchain/spec-2016-h1-public-comments 5pm

-----Original Appointment----- From: Kate Stewart [mailto:kstewart@...] Sent: Tuesday, July 12, 2016 12:44 AM To: Kate Stewart; Williams, Kelly; Mark.Gisi@...; Marr, David Subject: Invitation:

Hi Everyone, please find attached a revised version of the certification document. I am looking forward to discussing it with you during our upcoming call.

We will continue to review the public comments. We discussed 9 of 20 comments last meeting. You can review all the public comments received at the following link:

Hi Everyone, Reminder the focus on the upcoming call on Mon, 7/11 at 9am PST/ 4pm GMT will be on the Specification and Certification. Specification public comments

Dear all This is a reminder that the OpenChain curriculum slides are ready for editing online as referenced below. Slides chapters have been assigned to all volunteers who stepped forward to assist.

Hi Shane, Thanks for the clarification. I've updated the meeting minutes on the wiki - https://wiki.linuxfoundation.org/openchain/minutes. Regards, Kelly

Dear OpenChain Curriculum volunteers As discussed on our recent meeting we have around 175 slides that need to be refined into about 100 slides for circa 3 hour delivery. The slides are currently

Hi Kelly Thank you for your hard work as always! I have a few adjustments to the Curriculum minutes. The decided outcomes as I understand it were: (1) Refine existing 175 slides into 100 slides for

The presentation and minutes are posted on the wikihttps://wiki.linuxfoundation.org/openchain/minutes. Let me know if I missed anything or if you have any questions. Thanks! Kelly From:

I think we decided on the call today to use "conformance" and "conforms to" in the spec so the FAQs will need to also be updated to reflect that change. Sent from my phone, please excuse my brevity.

Reviewing the FAQ, I think it all looks even more confusing with the double meaning of the term compliance. For example: "Does all software in an organization need to be covered by an OpenChain

+1 to all of Karen's comments. I've been finding the double usage of compliance in this context confusing, both for people I'm talking to, and for me -- I'm not confident they get it. Conformance

You can find the OpenChain Frequently Asked Questions (FAQs) link here: https://wiki.linuxfoundation.org/openchain/spec-faq - Mark Mark Gisi | Wind River | Director, IP & Open Source Tel

You can review all the public comments received at the following link: https://wiki.linuxfoundation.org/openchain/spec-2016-h1-public-comments - Mark Mark Gisi | Wind River | Director,

Hi Everyone, Reminder the focus on the upcoming call on Monday, 6/20 at 5pm PST will be on the Specification and Curriculum. Agenda: https://wiki.linuxfoundation.org/openchain/minutes Join

Dear all In advance of our call next Monday please find the latest version of our draft slides here: https://1drv.ms/p/s!AsXJVqby5kpnhh_DyKoOkwZUnBVC Please note this is a “living document” and

Hi Jilayne Happy to explore the creation of a template test after we complete our training slides. Regards Shane

This is an important issue where I work for example, we often have to separate software created on dependencies from upstream versus work created in-house. Each can have a different license strategy

Hi OpenChain participants, attached to this email you will find a first draft of a certification document. As discussed during our last call, I created this document using the “Verification