Check out the first meeting of one of the most active groups in the world: tooling :) This is where you want to be to learn about how user companies are addressing automation around open

On this call we had a significant discussion around OpenChain ISO/IEC 5230 in the security domain. https://www.openchainproject.org/featured/2022/02/04/bi-weekly-2022-01-31 See what we have

Our usual partner call. We will be holding these every month of the 4th Thursday throughout 2022 to ensure everyone is

This meeting was held in Japanese: https://www.openchainproject.org/news/2022/02/04/japan-wg-22-2 (Good to share with your teams in the country :) )

Good morning! Being a global project we always have something at a crazy time. :) The good news is that Jimmy will be running regular telco meetings, and each time there will be one morning Europe

Thanks Gary. I will get the fix underway :)

I added an issue in the questionnaire repo to track this: https://github.com/OpenChain-Project/conformance-questionnaire/issues/70 Gary

Hi Jari, Thanks for the additional information. I don’t believe anyone is working on this issue. The PDF is generated from the data in the conformance-questionnaire github repo. All of

Gary et al So, in the Conformance in Questions (https://openchain-project.github.io/conformance-questionnaire/questionnaire.pdf), there is Spec Ref column and in that column, the references are

Hi Jari, Can you provide more specifics on where the inconsistency is? I just looked at the PDF in the link below it has the following text in the header: This document contains a series of

Good morning Shane I am sorry that I missed the 2AM meeting. Guess I was sleeping while it snowed Regards Chris

Hi All, I just noticed that the printable version of self-certification document (https://openchain-project.github.io/conformance-questionnaire/questionnaire.pdf) has Spec Refs to the OpenChain Spec

Telco meeting underway right now: https://zoom.us/j/4377592799

You have been invited to the following event. OpenChain Telco Work Group Meeting When Monthly from 17:00 to 18:00 on the first Thursday from Thu Feb 3 to Thu Mar 3 Japan Standard

Jan’s description is consistent with my interpretation. If there is general confusion over the meaning of “Open Source compliance inquiry” – I would recommend someone file an issue here:

Hi Gergely, my understanding is that it addresses the handling of the inbound questions concerning the open source parts of the Supplied Software. Assume you are using some GPLv2 licensed code and

Hi, I’m trying to interpret the requirements of 2.1.1 and I have problems finding out the meaning of “Open Source compliance inquiry”. It is not defined in the document. Can someone please

Hello. The other day, JAPAN WG FAQ-SG published "Common misunderstandings related to OSS license V7", and we received a request to add a link to each QA slide from the index. Therefore, we have

As discussed on our last call, some changes reflecting our conceptual approach (up for

As we enter the year of the Tiger I want to wish everyone fortune and happiness. 新年好, 恭喜发财 and 새해 복 많이 받으세요!