Relicensing: When Your Open Source Tool Turns to the Dark Side
Formal Metadata
| Title | Relicensing: When Your Open Source Tool Turns to the Dark Side |
|
| Title of Series | |
| Number of Parts | 39 |
| Author | |
| Contributors | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Imagine waking up one morning to find out that your beloved open source database, which lies at the heart of your system, is being relicensed. What does that mean? Can you still use it as before? Could the new license be infectious and require you to open source your own business logic?
This doom’s day nightmare scenario isn’t hypothetical. It is, in fact, very real, for databases and other OSS, with several examples over the past year alone.
On this talk Dotan will review some of the less known risks of open source, and share his lessons learned from Elasticsearch’s recent relicensing move. If you’re using OSS, you’ll learn to identify smells that will help you determine if it’s at risk of being relicensed so you can take proactive measures to protect your business. If you’re in the process of evaluating a new OSS, you’ll learn to look beyond the license and consider additional criteria. |
|