The Android mobile operating system is an excellent example of the power of open source software. Android’s ascent is attributable not only to demand for feature-rich mobile devices but also to the flexibility, extensibility, and developer-friendly openness of the core Android project, which has brought similar and rich functionality to a wide variety of mobile devices, available from many carriers. In this white paper we describe the opportunity and challenge of developing for Android, look at its history, review licensing and IP issues and present a solution for managing its abundance and complexity.
Creating an open source policy is not a trivial matter. OSS management spans multiple areas of responsibility, and the requirements and points-of-view of each of these areas must be included and reconciled if the policy is to be successful. As such, Olliance has identified four specific steps to creating an effective open source policy:
- Identify key stakeholders
- Obtain an organizational commitment
- Draft the policy
- Review and approve the policy
Download this whitepaper to learn more about creating and implementing an open source policy.
In this white paper we address the IP risks that developers, development managers, compliance officers, legal, and C-level managers must take into account when developing and distributing software created with FOSS in today’s multi-source development processes. We also provide readers with a discussion of myths that surround IP exposure in FOSS and survey the real issues surrounding licensing obligations, IP exposure and good FOSS citizenship.
By 2011, 90% of the Global 2000 will include open-source technologies as business-critical elements of their IT portfolios. It’s therefore likely that your organization is knowingly or worse, unknowingly using free and open-source software (FOSS) in internal and customer-facing software. The challenge is creating the right balance between management controls and enabling your development teams to leverage the ever-increasing abundance of high quality, secure, free and open source code. The white paper contains tips that are designed to help you establish the best approach to manage the use of FOSS as part of your code strategy to drive innovation and lower costs.
This whitepaper draws on the experiences of the Black Duck Software team, our customers, and other industry experts to propose new approaches to managing intellectual property in this new world. It describes a set of seven best practices that companies can use to avoid the risks and gain the benefits of this promising new approach to software development.
This white paper is for IT development executives looking to accelerate developer use of open source software as part of a multi-source development process while gaining necessary control over its adoption. First, you are not alone. Many IT executives face similar challenges as open source software use has grown exponentially in the last few years. Secondly, and most important, these problems can be fixed. This white paper tells you how.
On Friday June 29th, 2007, the Free Software Foundation announced the release of GPL (General Public License), version 3. This much anticipated version is the sequel to the commonly used GPL v2. This paper offers a brief summary of the most significant terms of the GPLv3 license.
Software Compliance Management: Automating License Compliance in the New, Mixed-IP Development World
This whitepaper educates companies about the challenges and benefits of working in a mixed-IP World and how software compliance systems are helping to unlock the potential of modular, collaborative development to significantly enhance profitability, reliability and ROI.
This whitepaper explains the advantages of reusing open source components in projects implemented by agile development teams, discusses the issues and risks that must be managed and highlights the benefits organizations can receive by leveraging open source components. It concludes with a brief case study that demonstrates the productivity gains that can be swiftly realized by integrating agile development and open source software.
This paper describes how the “open source genome” concept can be useful in understanding the origin and history of your code. We explore the nature of open source, why and how software developers use it, how information from an open source genome can help identify open source in your code and establish its origins, and why that is important.
This paper reviews the business case for automating the management of open source and provides recommendations for how to make open source an integral part of your software development operation while addressing business risks and compliance issues.
The SPDX Working Group has a straightforward charter: Create a set of data exchange standards to enable companies and organizations to share license and component information (metadata) for software packages and related content with the aim of facilitating license and other policy compliance. The goal -- to create a common software package data exchange format to simplify the discovery, collection and sharing of information about software packages and related content -- promises to save time, improve the accuracy of license data collection, and simplify compliance with software licenses. Learn more from the The Software Package Data Exchange™ (SPDX™) Format whitepaper.
This whitepaper explains how using a standard format, everyone in the supply chain from engineering to business managers, can now speak the same language as regards the contents of your software. Negotiations will be easier and issues can be resolved between technical and non technical decision makers, paving the way for faster time to market.
Written by Market Intelligence firm IDC and sponsored by Black Duck, the purpose of this whitepaper is to lay out software development "supply chain" strategies, to nurture community culture, and to discuss techniques to improve code usage as software creation evolves toward greater complexity.
The software supply chain enables developers to leverage software from multiple sources - internal, external, and open source - and to coordinate them effectively. We present the benefits and challenges of a life-cycle approach that emphasizes visibility into and control of software assets. Improving software development and business adaptability to competitive pressures is ultimately enabled by effective software creation. The need to leverage code in dynamic competitive environments across the software supply chain pushes companies toward software management to leverage existing sources of supply and improve business adaptability.
The New Due Diligence Assessing and Protecting Your Software Asset Value in Mergers, Acquisitions and Financing Rounds
The goal of this whitepaper is to make all parties involved in technology Merger & Acquisition (M&A) or funding events aware of software compliance management solutions, and how they can help organizations achieve their business goals.
In this whitepaper we explain why you need to identify all of the encryption functions in your software – and the challenge that poses. Then we explain the need for an automated means to identify encryption functions and to guide you through the compliance process. Finally, we describe how the Black Duck Export system helps make your job easier.