Skip to main content
Category

News

OpenChain Featured in CIO Review India

By News

On Thursday, 13 February 2020, OpenChain was featured in an article in the CIO Review India. The primary focus of the article was related to welcoming Lyra Infosystems are an official partner.

“We are excited and delighted to be part of the OpenChain Ecosystem to offer OpenChain conformance services, Open Source Policy, Process, Compliance consultation, Legal Remediation, and Audit services to organizations around the globe. Lyra Infosystems is an Open Source promoter, user, provider and a services organization with more than 280+ customers across geographies, domains, industries and technology verticals,” says Naba Magrabi, Open Source Senior Consultant for Lyra Infosystems.

Read the Article

https://www.cioreviewindia.com/news/linux-foundation-s-openchain-project-welcomes-lyra-infosystems-as-new-partner-nid-5330-cid-130.html

Request for Comments: One Slide Summary of Where OpenChain Fits in Workflows

By News

Fukuchi San from Sony has provided us with a draft outlining where the various sections of the OpenChain Specification fit into company process workflows. This is building on a document that was previously available for OpenChain Specification 1.2. The goal is to provide a quick framing of our industry standard for organizations considering adoption, considering conformance, or managing these activities. 

We would like to collect feedback on this document as it is likely to disseminate widely throughout our community in various languages over time. Email our General Manager (scoughlan@linuxfoundation.org) or any of our mailing lists to provide comments and suggestions. 

OpenChain Supplier Education Leaflet – German Draft

By News

Stefan from Fiducia & GAD IT announced yesterday that work is well advanced on a German translation of our Supplier Education Leaflet. Originally created by a sub-group of the OpenChain Japan Work Group, the supplier education leaflet is available in Japanese, English, Simplified and Traditional Chinese, as well as in Vietnamese as a draft.

Stefan’s full announcement and call for support

As discussed yesterday in Nuremberg during our kick-off meeting of the German OpenChain Working Group, I would like to reach out for support regarding finalisation of a translation of the Open Chain Supplier Leaflet into German.

You can see the current state-of-work at
https://github.com/OCSpecGermanTranslation/OpenChain-SuppierLeaflet-GermanTranslation/blob/master/supplier-leaflet/de/OpenChain-GeneralGuideline-E-0608_DE.pdf

The layout is not yet as complete as in the original – I would like to finalise the design after having sorted out the final German text. Thus, in a first round, quality checking of the text would be a good point to start 🙂

My ‚request-for-contribution‘ to you, if you currently want to / can support: 
Could you please compare the current German translation draft to the English version at
https://github.com/OCSpecGermanTranslation/OpenChain-SuppierLeaflet-GermanTranslation/blob/master/supplier-leaflet/supplier-leaflet-1.0-en.pdf
and provide corrections and suggestions for improvement? Please feel free to direct any comments to my address Stefan.thanheiser@gmx.de.

(Should any of you want to go deeper: I ported the document from the proprietary Adobe format I found at Github (sorry, if there should have been any other format there -maybe I did not dig deep enough into the directory structure) to a format of the open source tool Scribus – why not use OSS tools when writing about OSS? ;-).
The “scribus source file” for the PDF can be found at
https://github.com/OCSpecGermanTranslation/OpenChain-SuppierLeaflet-GermanTranslation/blob/master/supplier-leaflet/de/OpenChain-GeneralGuideline-E-0608_DE.sla
and can be edited using Scribus v1.5.5.)

Thank you in advance for your support and best regards,
Stefan

Check Out The Other Translations

Get these guides and many more documents in the OpenChain Reference Library.

OpenChain Reference Tooling Work Group @ FOSDEM – February 2020

By News

The OpenChain Reference Tooling Work Group held a series of meetings adjacent to the FOSDEM conference in Brussels. Here are the outcomes and minutes as provided by Oliver Fendt.

Big Picture

It would be good to have information about “who is using which open source tool to do OSS compliance work” to create an overview that might help during internal discussions about appropriate tooling. We did not find an exact solution for this but there was consensus to work on enhancing a planned TODO Group survey with concrete questions about OSS based compliance tool usage. The survey is scheduled to be launched in June 2020.

It would help if we could create a detailed description of the functional building blocks (e.g. license & copyright scanner) available and which tool(s) implement the desired functionality or part thereof. A similar concept is also an outcome of the “requirements” session, see below.

Glue Code

To produce practical glue code a concrete use case is necessary. If you have a concrete use case and the tools intended to address this use case it is easy to identify the glue code required for implementation. This also provides the possibility to address whether the APIs of the tools support the implementation of the use case. When a tool does not support the needed API it is then practical and possible to file a targeted issue for that specific tool.

We intend to create a place where one can share information about different integration scenarios or proof of concepts different person are currently working on, in order to avoid duplicated efforts and to be able to connect to others addressing the same concerns. Two examples: Martin is willing to share the information about his company’s Yocto proof-of-concept and Arun will share information about work in his company.

 *   Oliver Fendt has taken an action item to create a place (directory) in our Github repo that this and other information can be shared and coordinated.

There is also the possibility that existing tools have integration scenarios with on their roadmap and that for these scenarios glue code is unnecessary. Coordination is key.

Requirements

There was consensus that documentation is needed to describe the progress from user stories (what do I want/need to do) to capabilities of the functional building blocks that make up the big picture (e.g. License & copyright scanner). It is important to provide concrete instances of tools which implement the necessary capabilities. This will also be a good base to identify needed glue code and/or APIs to be implemented in the concrete tools.

 *   Oliver Fendt has taken an action item to create an issue about this in our Github repo @ https://github.com/Open-Source-Compliance/Sharing-creates-value/issues/74

Finally

If you want to contribute to realize our targeted results you are highly welcome. Jump in and comment on the issues we will create based on these outcomes.

Let’s work together to make this happen

Get these guides and many more documents in the OpenChain Reference Library.