An Organizational-Technical Concept to Deal with Open Source Software License Terms

Open source software (OSS) released under various license terms is widely used as third party libraries in today's software projects. To ensure open source compliance within an organization, a strategic approach to OSS management is needed. As basis for such an approach, we introduce an organiz...

Full description

Bibliographic Details
Main Authors: Sergius Dyck, Daniel Haferkorn, Jennifer Sander
Format: Article
Language:English
Published: International Institute of Informatics and Cybernetics 2016-06-01
Series:Journal of Systemics, Cybernetics and Informatics
Subjects:
Online Access:http://www.iiisci.org/Journal/CV$/sci/pdfs/SA725JZ16.pdf
id doaj-4d091ee088184d5ea018bd7762a68d6e
record_format Article
spelling doaj-4d091ee088184d5ea018bd7762a68d6e2020-11-24T23:56:33ZengInternational Institute of Informatics and CyberneticsJournal of Systemics, Cybernetics and Informatics1690-45242016-06-011436873An Organizational-Technical Concept to Deal with Open Source Software License TermsSergius DyckDaniel HaferkornJennifer SanderOpen source software (OSS) released under various license terms is widely used as third party libraries in today's software projects. To ensure open source compliance within an organization, a strategic approach to OSS management is needed. As basis for such an approach, we introduce an organizational-technical concept for dealing with the various OSS licenses by using procedural instructions and build automation software. The concept includes the careful consideration of OSS license conditions. The results obtained from this consideration and additional necessary commitments are documented in a so-called license playbook. We introduce procedure instructions enabling a consistent approach for software development using OSS libraries. The procedure instructions are described in a way such that they can be implemented for example for Java projects using the popular build automation tool Apache Maven and the software repository tool Nexus. We give guidance on how to realize such an implementation on basis of automation tools in practice.http://www.iiisci.org/Journal/CV$/sci/pdfs/SA725JZ16.pdf open source softwareopen source complianceprocedure instructionsorganizational-technical conceptbuild automation softwaresoftware engineering
collection DOAJ
language English
format Article
sources DOAJ
author Sergius Dyck
Daniel Haferkorn
Jennifer Sander
spellingShingle Sergius Dyck
Daniel Haferkorn
Jennifer Sander
An Organizational-Technical Concept to Deal with Open Source Software License Terms
Journal of Systemics, Cybernetics and Informatics
open source software
open source compliance
procedure instructions
organizational-technical concept
build automation software
software engineering
author_facet Sergius Dyck
Daniel Haferkorn
Jennifer Sander
author_sort Sergius Dyck
title An Organizational-Technical Concept to Deal with Open Source Software License Terms
title_short An Organizational-Technical Concept to Deal with Open Source Software License Terms
title_full An Organizational-Technical Concept to Deal with Open Source Software License Terms
title_fullStr An Organizational-Technical Concept to Deal with Open Source Software License Terms
title_full_unstemmed An Organizational-Technical Concept to Deal with Open Source Software License Terms
title_sort organizational-technical concept to deal with open source software license terms
publisher International Institute of Informatics and Cybernetics
series Journal of Systemics, Cybernetics and Informatics
issn 1690-4524
publishDate 2016-06-01
description Open source software (OSS) released under various license terms is widely used as third party libraries in today's software projects. To ensure open source compliance within an organization, a strategic approach to OSS management is needed. As basis for such an approach, we introduce an organizational-technical concept for dealing with the various OSS licenses by using procedural instructions and build automation software. The concept includes the careful consideration of OSS license conditions. The results obtained from this consideration and additional necessary commitments are documented in a so-called license playbook. We introduce procedure instructions enabling a consistent approach for software development using OSS libraries. The procedure instructions are described in a way such that they can be implemented for example for Java projects using the popular build automation tool Apache Maven and the software repository tool Nexus. We give guidance on how to realize such an implementation on basis of automation tools in practice.
topic open source software
open source compliance
procedure instructions
organizational-technical concept
build automation software
software engineering
url http://www.iiisci.org/Journal/CV$/sci/pdfs/SA725JZ16.pdf
work_keys_str_mv AT sergiusdyck anorganizationaltechnicalconcepttodealwithopensourcesoftwarelicenseterms
AT danielhaferkorn anorganizationaltechnicalconcepttodealwithopensourcesoftwarelicenseterms
AT jennifersander anorganizationaltechnicalconcepttodealwithopensourcesoftwarelicenseterms
AT sergiusdyck organizationaltechnicalconcepttodealwithopensourcesoftwarelicenseterms
AT danielhaferkorn organizationaltechnicalconcepttodealwithopensourcesoftwarelicenseterms
AT jennifersander organizationaltechnicalconcepttodealwithopensourcesoftwarelicenseterms
_version_ 1725457971991805952