Just to clarify: do you mean you entered the room on January 18th at 14:00 UTC (15:00 CET)? The tooling work group was scheduled for this time. Checking because your mail arrived on January

Hi all Yesterday me and some people arrived on time at 15:00 CET, and 5 minutes later, most of us dropped, as we had no agenda whatsoever or meeting plan. And this is becoming recurrent. And maybe

Hi I and Alberto have ourselves set up a BBB machine -- and in case we can offer to host the next meeting. On the one hand I have attended many meetings on the FSFE's instance without a hiccup. On the

Hi Nathan! I won’t be there in person (02:00 my time), but I wanted to flag that the website had substantial updates recently, so it might be worth a look. Everyone, dial in

Hi all - Just a reminder that the Education Work Group has a working session coming up. We're working on updating the key documents that help promote our projects, among other things our FAQ. We also

If the work group is ok, we can always use the main OpenChain room on Zoom. No setup or passcode necessary, just enter the link and it automatically records the

FWIW, I’vealways struggled with BBB. Previously, the audio has always sounded like it’s underwater, and (I think) people weren’t able to make out what I was saying – but the recordings showed

Hello It seems like the Bluebutton app doesn’t work too well. I couldn’t get it to establish audio connection and it seemed that others had the same issue. Regards Chris

A reminder that the automotive work group has its regular meeting later today ☺️ OpenChain Reference Tooling Work Group - Third Wednesday Meeting Scheduled: Jan 18, 2023 14:00 to 15:00,

Oskar and Jon will be visiting Japan with other people from the newly independent FOSSID to help provide a market overview. The meeting takes place on the 2nd of February between 10:00 and 14:00 in

Our community colleagues in Finland are holding an OSPO-related event in late January that will cover OpenChain. Learn more and register

Our regular monthly call for North America / Asia saw some discussion around two key topics for the next generations of our specifications for license compliance and for security. One related to

Philippe Ombredanne from nexB will lead a technical deep dive into VulnTotal on the 7th of February at 09:00 CET (08:00 UTC). Join us in our usual room here: • https://zoom.us/j/4377592799 This

OpenChain Automation Case Study #7 – VulnerableCode technical deep dive into VulnTotal Philippe Ombredanne from nexB will lead a technical deep dive into VulnTotal on the 7th of February at 09:00

Issue under discussion here: https://github.com/OpenChain-Project/License-Compliance-Specification/issues/62 == Here is what we currently have: == 3.5.1 - Contributions If an organization considers

Further discussion was contained here: OpenChain-Project/License-Compliance-Specification#63 Consolidating to this issue (and closing License Compliance Spec Issue 63) because it seems we will

During the North America / Asia monthly call January 2023 we had a solid discussion on this issue: https://github.com/OpenChain-Project/License-Compliance-Specification/issues/63 Context: == Current

Please find attached. Main focus will be on editing the specs. All welcome. We have some meaty stuff to discuss, including continuing our discussion on the definition of open

Dear all Our regular USA / Asia monthly community call will take place in just over one hour (09:00 CST / 10:00 KST + JST). For those in the USA, it is at 17:00 Pacific / 19:00 Central on

Hi Chris The call will be at 17:00 Pacific / 19:00 Central on January 16th (Monday) for the US :) https://zoom.us/j/4377592799 Shane