Today’s applications are arguably the equivalent of a mashup in code. They are made up of code that comes from a variety of sources. For instance, they may use one or more frameworks and libraries, each of which may also may rely on hundreds of modules (e.g., npm or Ruby gems). Even portions the “original” code in a project may have originally been copy-pasted from documentation, a tutorial, or—gasp—Stack Overflow.
We developers have become so comfortable with open source that we often make the mistake of not paying attention to the licenses of the software we are using. But not paying attention to licensing can open you and your company up to potential liabilities. Brian Rinaldi offers an overview of the various types of licenses typically associated with the software and code you may use in a given project, helping you stay aware and navigate the complexities.
Brian Rinaldi is a developer advocate at Progress. Brian has been a developer for nearly 20 years, working with frontend and backend technologies mostly focused on the web. Brian is the coeditor of Mobile Web Weekly, authored a report on static site generators for O’Reilly, and coauthored Working with Static Sites, also from O’Reilly.
For exhibition and sponsorship opportunities, email firstname.lastname@example.org
For information on trade opportunities with O'Reilly conferences, email email@example.com
View a complete list of Fluent contacts
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org