Managing Android and the Complexity Inside: Understanding the Open Source License and Compliance Issues
- 1,897 views
Slides presented by Peter Vescuso, Black Duck Software's EVP of Marketing & Business Development, at the Linux Foundation's Android Builder’s Summit. ...
Slides presented by Peter Vescuso, Black Duck Software's EVP of Marketing & Business Development, at the Linux Foundation's Android Builder’s Summit.
As Android devices grow in popularity and the market expands, developers are eager to tap into its potential, but must be able to manage what is a relatively complex code base and be able to react quickly to rapidly changing feature sets. They also must do so in a way that complies with license obligations, or put themselves and their innovations at risk. While Android is well documented, easily accessible and being rapidly adopted, there are some misperceptions regarding its complexity and licensing. With 165 sub components, Android is fairly complex. Depending on how its many components are integrated and licensed with a device manufacturers own code is not trivial and may create risk and exposure. The Android has declared its license as Apache 2.0, but much of Android uses non-Apache licensed code licensed with the GPL, LGPL and many other licenses, including licenses not approved by the OSI. Attendees will learn about the composition of Android, its structure and components, and the many open source licenses it uses, and the issues a typical device manufacturer needs to address. Finally we will present best practices for managing the complexity of Android, especially as a participant in the mobile supply chain, and ensure compliance with its many licenses.
- Total Views
- Views on SlideShare
- Embed Views