Structuring the FLOW of Responsibility

Last modified by Stefano Maffulli on 2023/02/17 01:53

Structuring the FLOW of Responsibility

Learning Outcomes: Participants will advance their understanding of conceptual and operational perspectives on a diversity of agreement types associated with the distribution of intellectual resources. Operational methods such as licensing, contributor agreements, employment contract clauses and compliance verification solutions are framed in relation to the new ISO 19600 Guidelines on Compliance Management Systems.  All of this is first grounded in a bedrock theory of responsibility.

Conceptual Foundations of Responsibility

Theory of Responsibility

Management of Responsibility

A Documentation Specification: Software Package Data Exchange (SPDX)

A Compliance Management Process: ISO 19600

Note: An adaptation of ISO 19600 to FLOW development methodology remains to be described. References in this section are, at present, only based on the generic compliance management system guideline.

Management of Intellectual Provenance (IP) Responsibilities

  • Discussion: A company, foundation or project community benefits in several ways when it puts in place an Intellectual Provenance (IP) compliance management process aligned with the ISO 19600 Guidelines:
    • The effort demonstrates tangible "due diligence" in any potential litigation process;
    • This makes it much easier, faster (and thus less expensive) for your lawyers to help you in the event of litigation;
    • Multiple parties can more easily adopt a shared compliance management process:
      • Different organizations involved in commons-based peer production;
      • Different sections/departments within an organization.
    • Sustainable innovation is enhanced with responsible risk management, since team-members know what is in and what is out of bounds.

Licensing: The Delegation Responsibility

The Main Currents of FLOW Licensing

"Similarities; Differences; Choices; Trends; Linkages to Other Types of Agreements"

Dual/Multi Licensing Options (for individual commits and for whole projects)

The FLOW Subscription Model

License Compliance Verification

Policies and Approaches for License Compliance Verification

Technical Analysis of FLOW License Compliance Verification

All of the solutions listed below are themselves provided under FLOW licenses. 

Binary Analysis Tool: The Binary Analysis Tool (BAT) is a modular framework that uses the same approach applied by gpl-violations.org to discover issues in consumer electronics. It can open many types of firmware, detect Linux and BusyBox issues, and report outcomes in XML format. It also features knowledge-base support to allow high fidelity customization for advanced users. BAT is available for free under the Apache license so that everyone can use, study, share and improve it. The project frequently adds new features.
Website: http://www.binaryanalysis.org

Code Janitor Tool: The Code Janitor is a tool released by the Linux Foundation that helps to search source code to make sure that developers did not leave comments that might reveal future products, product code names or discuss competitors and their products. It maintains a database of keywords to scan for, and can be customized as necessary. It is available without charge. Website: http://www.linuxfoundation.org/programs/legal/compliance/tools

Dependency Checker Tool: The Dependency Checker is a tool released by the Linux Foundation that helps identify source code combinations that will lead to dynamic and static linking, and in the context of a license policy framework can create a list of items that need to be flagged before products are released. Website: http://www.linuxfoundation.org/programs/legal/compliance/tools

FOSSology: FOSSology started as an internal project at HP to support governance processes. It is a tool that analyses all the files in a project and reports on the licenses used, basing its results on license declarations and tell-tale phrases. It also has the ability to scan for copyright notices, email addresses and URLs, allowing users to create custom reports. The project is hosted by the Linux Foundation, is available as Free Software, and is maintained in both English and German by developers from HP and other organizations. Website: http://fossology.org

Ninka: Ninka is a lightweight license identification tool for source code. It is sentence-based, and provides a simple way to identify open source licenses in a source code file. It is capable of identifying several dozen different licenses (and their variations). It has been designed to be lightweight, fast and to avoid making errors. It is available under a Free Software license. Website: http://ninka.turingmachine.org

CORAS: Model-Driven Risk Analysis (CORAS Integration Platform, licensed LGPLv2)
http://heim.ifi.uio.no/~ketils/kst/Others/021008.platform-poster.pdf

FLOW Contributor Agreements

FLOW in Employment Contracts

Tags:
    

Submit feedback regarding this wiki to webmaster@opensource.org

This wiki is licensed under a Creative Commons 2.0 license
XWiki 14.10.13 - Documentation