3. Derived Works Allowed 4. Integrity of the Author’s Source Code 5. No Discrimination Against Persons or Groups 6. No Discrimination Against Fields of Endeavor 7. Distribution of License 8. License Must Not Be Specific to a Product 9. License Must Not Restrict Other Software 10. License Must Be Technology-Neutral
support • Vendor independence • Vendor risk mitigation • An improved negotiating position • Compliance with policy • Fast adoption (no purchase necessary!) • An ancillary social benefit And has a reputation for: • Low price • Security • Innovation • Transparency • Interoperability
in which we sell • Drive adoption of standards • Foster innovation by leveraging community contributions • Encourage 3rd party contributions that can benefit customers • Increase the difficulty of competitive followers in bootstrapping a business • Gain brand recognition and community marketing • Grow customer goodwill and loyalty • Be an on-ramp to paid offerings
source Revenue comes tangentially: support, hosting, training Source is available. Development is public. License is proprietary. Open Core Parts are open, parts are closed. Revenue comes from upsell to proprietary features.
Time based BSL: Business Source License (MariaDB) 2. All rights except . . . CCL: Confluent Community License (Confluent) SSPL: Server Side Public License (Mongo) 3. Mixed open and closed Elastic License
• Anyone can merge • Community consensus process Pros: • Broad adoption Cons: • Hard to achieve alignment • Susceptible to “tragedy of the commons” (lack of polish) • Single copyright holder (CLA) • Restricted merge rights • Corporate vision Pros: • Customer focus Cons: • Often narrows use cases • If you disagree, you have to fork