1. News
Oliver gave an overview about “what happened since last meeting”:
On 6th of Feb there was the kick off meeting of the OpenChain German Work Group. More than 35 persons attended the meeting. Main results were:
1. the work group agreed on working on a guideline and layout of an OSS disclosure document
2. the work group will work on translations of the existing material, there is already work in progress. Please see https://github.com/OCSpecGermanTranslation/OpenChain-SuppierLeaflet-GermanTranslation/tree/master/supplier-leaflet/de
3. the work group has a “rolling chair” model – i.e. the host of the particular meeting is automatically the chair of the work group
Oliver started working on a charter, contribution guideline, code of conduct and updated the README of our project. The current state of work can be analyzed, improved, commented etc. in the branch https://github.com/Open-Source-Compliance/Sharing-creates-value/tree/onboarding-new-persons
Please follow the link, read the documents and please provide comments and improvements. The branch is called onboarding-new-persons
Sami suggested to add a “code example” what we expect in the context of reuse conformant contributions. Further he suggested to add a phrase like “other licenses of already existing code.
Sami volunteered to let our logo to be checked whether our logo is fine from a trademark point of view
2. Summary of the Unconference about OSS tooling in Brussels
Michael gave an overview about the unconference on OSS compliance tooling which took place on 31st of January in Brussels. Material and photos are available in our repo, please check https://github.com/Open-Source-Compliance/Sharing-creates-value/tree/master/Tooling-Landscape/Meeting-Material/Meeting-20200131
2.1. Code matching
One result of the code matching session was that there need to be a definition what is exactly to be understood by code matching. Some see code matching as the task “I have a binary package and need to find the corresponding source”. Others see it “I want to check source code whether it contains source code originating for 3rd parties.
2.2. sw360
This session centered around using and installing sw360.
2.3. Container Scanning
All attendees agreed that license compliance is a problem. The attendees agreed to start working on guidelines and best practices for container handling and container license compliance.
2.4. Big Picture
Please have a look at the slides.
2.5. Glue Code
Please have a look at the slides.
2.6. Requirements
Please have a look at the slides.
3. What approaches are existing for license compliant containers
We were not able to discuss the topic “3. What approaches are existing for license compliant containers” and decided to dedicate the next meeting entirely to container compliance
4. Next Meeting
26th of Feb 2020
Agenda: What approaches are existing for license compliant containers
Keep Up-To-Date and Participate
