Good morning Shane Would it be possible to get recordings of these webinars? I can’t seem to be able to wake up here at 1:30 AM to attend a webinar at 2 AM Central Daylight time in the US and it

"Today, the Department of Commerce and NTIA are publishing a report on the minimum elements for an SBOM. The report builds on the work of NTIA’sSBOM multistakeholder process as well as the responses

We are going live now. ISO 5230 and security extensions is the topic: https://zoom.us/j/9990120120?pwd=NzVCaFE2L1RRRFZaSkk0dm8xdlplUT09

REMINDER: OpenChain Bi-Weekly Work Group Call - 2021-07-13 at 06:00 UTC / 07:00 BST / 08:00 CEST / 11:30 IST / 14:00 CST / 15:00 KST+JST In 30 minutes we are talking OpenChain ISO 5230 and security

REMINDER: OpenChain Bi-Weekly Work Group Call - 2021-07-06 at 06:00 UTC / 07:00 BST / 08:00 CEST / 11:30 IST / 14:00 CST / 15:00 KST+JST In 30 minutes we are talking OpenChain ISO 5230 and security

Webinar #26 – Open Hardware at CERN, FOSSLight Overview and Automating Yocto with SPDX This was a massive webinar covering just over an hour. Highly recommended to catch the latest in open hardware

Amazing news! Best regards, Gilles GravierDirector, Senior Strategy Advisor - Global Open Source PracticeWipro LimitedM: +41 79 472 8437in/gillesgravier @gravax

Spectacular news! Well done! Andrew Katz Partner [LinkedIn icon]<https://www.linkedin.com/company/moorcrofts-llp> [Twitter icon] <https://twitter.com/moorcroftsllp> [Logo] <https://moorcrofts.com/>

In one of our biggest announcements for 2021, Samsung Electronics announces adoption of OpenChain ISO 5230, the International Standard for open source compliance. They join a growing community of

OpenChain Bi-Weekly Webinar - 2021-07-06 at 06:00 UTC / 07:00 BST / 08:00 CEST / 11:30 IST / 14:00 CST / 15:00 KST+JST On today's webinar we are going to cover two major topics. First up we have

OpenChain Bi-Weekly Webinar - 2021-07-06 at 06:00 UTC / 07:00 BST / 08:00 CEST / 11:30 IST / 14:00 CST / 15:00 KST+JST On tomorrow’s webinar we are going to cover two major topics. First up we

Probably just to prevent some misunderstanding or unnecessary fears: The law, Dirk referred to, will be effective from 2023. Then it addresses companies with >3000 employees, from 2024 it will also

Dirk That is a brilliant question. I would add to this that consideration of open source projects in general have many contributors. Would that make a company contributing to the code-base “that

It is also my guess that you need an explicit supply contract to establish the supplier relationship formally. If you do it within a holding company (inner source) that formal relationship is

Hi, Germany has a new law about diligence in the supply chain, basically to watch out that no supplier violates human rights. We like to talk about open source projects being suppliers, but I'm not

You can find all the sections of the event carefully edited by Soim right here: https://openchain-project.github.io/OpenChain-KWG/en/meeting/10th/

Hi Steve, That’s a great question, and thinking about it, I’d be in a similar position if I was looking for formal compliance. I’d also add “designed/wrote the Company Open Source

Thanks, Martin. In that context, your comments make sense. I'm specifically looking for a starting point: assuming no-one in the org has any formal/external training yet, how does one show

Dear all, I may have misunderstood the original question, my comment was around “training the trainers” and/or keeping the “experts” up to date. I don’t think there is much formal