|
Invitation: OpenChain UK Work Group Meeting @ Thu Oct 13, 2022 12:00 - 14:00 (CEST) (main@lists.openchainproject.org)
|
||||||||||
|
|
||||||||||
|
Invitation: OpenChain German Work Group Meeting @ Wed Nov 16, 2022 11:00 - 17:00 (CET) (main@lists.openchainproject.org)
|
||||||||||
|
|
||||||||||
|
OpenChain Germany Work Group – 2022-11-16 in Cologne
OpenChain and PwC will host the next OpenChain Germany Work Group meeting on the 16th of November 2022 in Cologne. All welcome. Learn more here:
https://www.openchainproject.org/featured/2022/09/29/germany-wg-2022-11-16
|
||||||||||
|
|
||||||||||
|
OpenChain UK Work Group Meeting – 2022-10-13 in London
OpenChain, Moorcrofts and Orcro will host the next OpenChain UK Work Group meeting on the 13th of October 2022 in London. All welcome. Learn more here:
https://www.openchainproject.org/news/2022/09/29/uk-work-2022-10-13
|
||||||||||
|
|
||||||||||
|
REMINDER: SPECIAL CALL: ISO/IEC WG suggestions for Security Specification today at 08:00 UTC (2022-09-27)
tl;dr: we have an important specification call in just under an hour.
ISO/IEC WG/SC27 (security) has provided some feedback on the OpenChain Security Assurance Specification 1.0 for our review. Our review cycle runs from now until October 4th and you can get started on checking their comments via our issue tracker here: https://github.com/OpenChain-Project/Security-Assurance-Specification/issues We will hold a special call to discuss their comments on Tuesday the 27th of September 2022 at 08:00 UTC to review their comments. We are providing some guidance on the review of these comments and suggestions. (1) Our specification was completed after a multi-month process in March 2022, and it was ratified by our board for ISO/IEC JTC-1 PAS submission on the 14th of September 2022 (2) Therefore OpenChain Security Assurance Specification 1.0 is functionally complete (3) We should review the ISO/IEC WG comments with this perspective (4) We are looking for editorial adjusts for clarity and errors (5) We are not looking to change the scope or function of OpenChain Security Assurance Specification 1.0 or any immediate clarity / error adjusted successor (6) This is because we want to proceed with our JTC-1 PAS submission as approved by the OpenChain Governing Board (7) But we can place any comments for scope and function adjustment into a deferred status (8) And we will return to them for discussion around inclusion in OpenChain Security Assurance Specification 2.0 This meeting is held in the OpenChain Project Zoom room: https://zoom.us/j/4377592799 Check your timezone: PDT United States Pacific UTC-07:00 UTC Coordinated Universal Time UTC CET Central European Time UTC+01:00 IST India Standard Time UTC+05:30 CST China Standard Time UTC+08:00 KST Korea Standard Time UTC+09:00 JST Japan Standard Time UTC+09:00 Compare timezones: https://www.worldtimebuddy.com Join via one tap mobile: +86 10 8783 3177,,4377592799# Mainland China +33 1 8699 5831,,4377592799# France +49 69 7104 9922,,4377592799# Germany +81 524 564 439,,4377592799# Japan +82 2 3143 9612,,4377592799# Korea +91 80 71 279 440,,4377592799# India +886 (2) 7741 7473,,4377592799# Taiwan +44 330 088 5830,,4377592799# UK +13017158592,,4377592799# USA Find your local country number: https://zoom.us/u/awFnORNiA Meeting ID: 437 759 2799 Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://meetings.hubspot.com/scoughlan
|
||||||||||
|
|
||||||||||
|
October's Ospology.live - OSPO Workshop:Stockholm, Sweden
Sean McIlroy (LF, PM)
Dear all October's Ospology.live will be hosted by OSPO at Ericsson (Stockholm, Sweden) and co-organized with TODO, OpenChain, SPDX, CHAOSS and OpenSSF projects. Join the first in-person Workshop to help organizations effectively implement Open Source Program Offices (OSPOs) based on specific region needs in Europe.
If you have any questions, please contact the event Organizer - Ana Jimenez (asantamaria@...)
|
||||||||||
|
|
||||||||||
|
Reminder: Call tomorrow to discuss ISO/IEC WG suggestions for OpenChain Security Assurance Specification 1.0
ISO/IEC WG/SC27 (security) has provided some feedback on the new OpenChain Security Assurance Specification 1.0 for our review. Our review cycle runs from now until October 4th. Get started via our issue tracker here:
https://github.com/OpenChain-Project/Security-Assurance-Specification/issues Our call to address the comments takes place tomorrow (Tuesday 27th September) at 08:00 UTC. Calendar invite attached. Regards Shane
|
||||||||||
|
|
||||||||||
|
Invitation: SPECIAL CALL TO ACTION: ISO/IEC WG suggestions for OpenCh... @ Tue Sep 27, 2022 09:00 - 10:00 (WEST) (main@lists.openchainproject.org)
|
||||||||||
|
|
||||||||||
|
SPECIAL CALL TO ACTION: ISO/IEC WG suggestions for OpenChain Security Assurance Specification 1.0 - CALL ON TUESDAY AT 08:00 UTC
Dear all
ISO/IEC WG/SC27 (security) has provided some feedback on the OpenChain Security Assurance Specification 1.0 for our review. Our review cycle runs from now until October 4th and you can get started on checking their comments via our issue tracker here: https://github.com/OpenChain-Project/Security-Assurance-Specification/issues We will hold a special call to discuss their comments on Tuesday the 27th of September 2022 at 08:00 UTC to review their comments. I want to provide some guidance on the review of these comments and suggestions. (1) Our specification was completed after a multi-month process in March 2022, and it was ratified by our board for ISO/IEC JTC-1 PAS submission on the 14th of September 2022 (2) Therefore OpenChain Security Assurance Specification 1.0 is functionally complete (3) We should review the ISO/IEC WG comments with this perspective (4) We are looking for editorial adjusts for clarity and errors (5) We are not looking to change the scope or function of OpenChain Security Assurance Specification 1.0 or any immediate clarity / error adjusted successor (6) This is because we want to proceed with our JTC-1 PAS submission as approved by the OpenChain Governing Board (7) But we can place any comments for scope and function adjustment into a deferred status (8) And we will return to them for discussion around inclusion in OpenChain Security Assurance Specification 2.0 Regards Shane
|
||||||||||
|
|
||||||||||
|
Invitation: OpenChain Monthly Community Call - 09:00 CST (01:00 UTC) ... @ Monthly from 02:00 to 03:00 on the third Tuesday (WEST) (main@lists.openchainproject.org)
|
||||||||||
|
|
||||||||||
|
Invitation: OpenChain Monthly Community Call - 09:00 PST (16:00 UTC) ... @ Monthly from 17:00 to 18:00 on the first Tuesday (WEST) (main@lists.openchainproject.org)
|
||||||||||
|
|
||||||||||
|
IMPORTANT: New OpenChain Monthly Community Call - 09:00 PST (16:00 UTC) on 1st Tuesday / 09:00 CST (01:00 UTC) on 3rd Tuesday
Dear all
We have been experimenting with various structures for our calls for a couple of months (time and topic defined calls to action etc.). After collecting community feedback, I would like to announce a new Monthly Community Call Schedule where: (1) Once per month for primary timezones we will hold a structured one hour meeting (2) This meeting will have a repeating core agenda so you always know what you are getting (3) We will be giving plenty of space for our work groups to ensure they share core news with you in a timely manner (4) You can provide direct feedback on aspects of community work, management and future planning This new structure is important to help us bring together the various things the OpenChain community is doing around the world, from building our family of standard (licensing compliance and now security compliance), assisting with tooling, SBOMs and OSPOs, and facilitating industry specific discussions in areas like telco and automotive. The calendar invitations for our new meeting schedule will go out shortly. We will start in October and continue on this schedule to end-2023 before any further adjustments, allowing plenty of predictability in your calendars. Regards Shane — Shane Coughlan General Manager, OpenChain e: scoughlan@... p: +81 (0) 80 4035 8083 w: www.linuxfoundation.org Schedule a call: https://meetings.hubspot.com/scoughlan
|
||||||||||
|
|
||||||||||
|
Re: Implementing Section 3.3.2 of OC Standard on common license use cases
I am adding Japan and Korea work groups to this thread as some of the companies there have been doing case studies. :)
toggle quoted messageShow quoted text
On Sep 23, 2022, at 12:50, Mattran, Mary <mary.mattran@...> wrote:
|
||||||||||
|
|
||||||||||
|
OpenChain Summit 2022 – Full Recording
The OpenChain Project held its annual an all-day summit adjacent to Open Source Summit Europe (OSS EU) on the 14th of September. This event featured news from our latest board meeting (including the decision to launch our new security specification), a deep dive into a significant new automation landscape to assist with license, security and export control compliance, SBOM discussions and more.
Check out the full recording at the link below alongside copies of our excellent keynote presentation from Andrew Katz of Orcro and the automation landscape capability map presentation delivered by Jan Thielscher of EACG on behalf of the OpenChain Reference Tooling Work Group. Here are the key takeaways: • The OpenChain Project now maintains a family of specifications to build trust in the supply chain. We started with license compliance and now we have a sister standard for security. • Open source automation for open source license, security and export control compliance is getting a clear capability map to guide investment of resources and save time. • Software Bill of Materials (SBOM) has seen great progress in the last year or two, and the OpenChain Telco Work Group is working on very practical items related to market adoption. • Open source licensing discussions have become somewhat stale and there is scope for considering the future of open source licensing approaches. https://www.openchainproject.org/news/2022/09/23/openchain-summit-2022-full-recording
|
||||||||||
|
|
||||||||||
|
Implementing Section 3.3.2 of OC Standard on common license use cases
I am interested to know how other companies are implementing section 3.3.2 of the standard which discusses how the program should be capable of handling "common open source license use cases". Do you have a written process for each use case? Do you have people who check for license incompatibilities? Do you have a list of the common licenses and the obligations for various use cases?
|
||||||||||
|
|
||||||||||
|
Be part of the OpenChain Partner Webinar Series - An easy way to learn about services supporting ISO/IEC 5230, the International Standard for open source
Sean McIlroy (LF, PM)
As you may be aware, the OpenChain Project has launched a series of webinars that explains the services available from our partners around the world. Our goal is to help you understand your options if you seek third party assistance for adoption, refinement or certification. Currently we have two slots open, after which we will discuss scheduling further webinars with you, and the best timing for their release. Here is where you can lock down your slot: https://docs.google.com/spreadsheets/d/1-c9iQDuDb5oYQqA7q2RgIQMOpblZSTlKsRGOR9xHXYg/edit?usp=sharing The format is pretty simple: you pre-record a webinar that we play at the appropriate data and time, and we encourage questions to happen on the main mailing list to maximize community engagement. Ideally we would like you to provide the recording in 1080p mp4 format. Webinars so far:
If you have any questions, please don't hesitate to contact me
|
||||||||||
|
|
||||||||||
|
Re: List of open chain calendar events for partners
Indeed!
toggle quoted messageShow quoted text
We were doing a short experiment with call to action (time limited) and holding off on mini-summits pending the large summit last week. A revised schedule will be announced in less than 24 hours 🙂 Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://meetings.hubspot.com/scoughlan
On Sep 21, 2022, at 19:33, Christopher Wood <cvw01@...> wrote:
|
||||||||||
|
|
||||||||||
|
OpenChain Security Assurance Specification 1.0 now available
Dear all
The OpenChain Security Assurance Specification 1.0 is now available: https://github.com/OpenChain-Project/Security-Assurance-Specification/blob/main/Security-Assurance-Specification/1.0/en/openchain-security-specification-1.0.md This specification is built from the Security Assurance Reference Guide 2.0 (Release Candidate 1) published on 2022-03-28. That completed reference specification document went through a final approval process via editing on our specification list and calls, before graduating to a governing board vote to transform into this published security specification on 2022-09-14. We will now proceed to ISO/IEC JTC-1 PAS submission with an estimated completion date of circa mid-2023. In the meantime, our security assurance specification is ready for market adoption as a de facto standard. Over the next couple of weeks we have some time for sanity-checks and minor adjustments. I would like to begin that process today. There are two tasks for the community: (1) Check our Security Assurance Specification 1.0 against the Security Assurance Reference Guide 2.0 (Release Candidate 1) to ensure Sections 1, 2 and 3 match. You can find the Security Assurance Reference Guide 2.0 (Release Candidate 1) here: https://github.com/OpenChain-Project/Security-Assurance-Specification/tree/main/Security-Assurance-Guide-Depreciated/2.0 (2) Check the OpenChain Security Assurance Specification 1.0 for any typographical errors that have snuck through our existing editing process. You can find the document linked at the start of this email or here: https://github.com/OpenChain-Project/Security-Assurance-Specification/blob/main/Security-Assurance-Specification/1.0/en/openchain-security-specification-1.0.md This email constitutes a soft launch for this specification. Over the next few days we will start broader distribution of this news, including on social media and via blog posts. However, you can begin sharing it immediately with your teams and peers. Please note: the scope of this reference specification may expand over time based on community feedback. However, comments and notes should be confined to the existing scope at this juncture. Our specification is complete barring minor adjustments for readability, editing and clarity. Regards Shane — Shane Coughlan General Manager, OpenChain e: scoughlan@... p: +81 (0) 80 4035 8083 w: www.linuxfoundation.org Schedule a call: https://meetings.hubspot.com/scoughlan
|
||||||||||
|
|
||||||||||
|
Re: List of open chain calendar events for partners
Christopher Wood
Hi Steve and Shane It’s not just you Steve. I thought the same thing when I looked at the schedule this morning. Best Chris
On Sep 21, 2022, at 9:55 AM, Steve Kilbane <stephen.kilbane@...> wrote:
|
||||||||||
|
|
||||||||||
|
Re: List of open chain calendar events for partners
Yes, the calendar is about to get a ton of new entries, but currently is looking quiet 🙂
toggle quoted messageShow quoted text
Shane Coughlan OpenChain General Manager +818040358083 Book a meeting: https://meetings.hubspot.com/scoughlan
On Sep 21, 2022, at 16:55, Steve Kilbane <stephen.kilbane@...> wrote:
|
||||||||||
|
|