BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//program.foss-backstage.de//fossback23//talk//9MF8TW
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:STANDARD
DTSTART:20220314T000000
TZNAME:CET
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20220327T030000
RDATE:20230326T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20221030T030000
RDATE:20231029T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Build license management into your pipelines - Floor Drees
DTSTART;TZID=Europe/Berlin:20230314T120000
DTEND;TZID=Europe/Berlin:20230314T121000
DTSTAMP:20260816T165222Z
UID:pretalx-fossback23-9MF8TW@program.foss-backstage.de
DESCRIPTION:We’re all moving fast and in order to do so we’re relying 
 on a lot of dependencies to give us that commercial edge. In doing so we
 ’re trusting the work of strangers on the internet\, and also that of ve
 ndors who may change their mind on who can benefit from their software. \n
 \nThe 2022 OSSRA (Open Source Security and Risk) report\, examines the res
 ults of more than 2\,400 audits of commercial codebases\, of which 97% con
 tained open source. Four of the 17 industry sectors represented in the rep
 ort—Computer Hardware and Semiconductors\, Cybersecurity\, Energy and Cl
 ean Tech\, and IoT—contained open source in 100% of their audited codeba
 ses. \n\nIf you install Electron and have to add 87 packages — that mean
 s 87 license dependencies. Every single package is likely to have its own 
 dependencies\, and therefore\, another license you need to comply with. As
  you can imagine license management can’t be done manually and when done
  incorrectly can create a technical debt. \n\nLicense litigation may end u
 p forcing you to release your code under the same license as the package d
 ependency you used. Other potential problems include being sued for financ
 ial liability by the creator of the component\, and/or losing reputation a
 nd getting negative press coverage.\n\nFind out how to do a software compo
 sition analysis to create an SBOM (Software Bill of Materials)\, and how t
 o monitor changes in your components’ licenses every time you deploy.
LOCATION:Stage 2
URL:https://program.foss-backstage.de/fossback23/talk/9MF8TW/
END:VEVENT
END:VCALENDAR