The Apache Way for Business
summary
Explains how Apache governance forces individual contributors matter not company control, so businesses must join projects, align roadmaps, and fund contributors rather than buy feature priority. Recommends keeping a separate product brand from the project (product ≠ project), upstreaming patches (examples: Jackrabbit fixes, Cassandra performance/security patches), or maintaining a minimal fork when needed. Covers trademark/branding rules, practical routes to monetize—support, consulting, niche added-value—and why marketing must avoid claiming project ownership.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:12Who are you
- 5:04What topics do you want to cover
- 5:56Linux Foundation vs Apache Software Foundation
- 10:19Software as Public Good
- 11:13Nicks Story
- 12:37Apache Constitution
- 17:09How can we help
- 20:34When this was my project
- 21:05You have no guarantee
- 23:36Drive an agile team
- 24:51Apache Jackrabbit
- 26:35Forking
- 26:52Why contribute
- 28:13Happy question
- 28:34Small wins
- 32:03Marketing
- 33:43Project Name
- 34:44Diversity
- 36:00What not to do
- 42:34Support consulting
- 43:33Digital transformation
related talks
41mA user's perspective on open source
01h 00mGrow and manage your open source project with a proven way - The Apache Way
45mRunning an Apache Project: 10 Traps and How to Avoid Them
44mThe History of the Apache Software Foundation
47mHow to Turn Your Open Source Project Into a Company
22mKeynote: The Apache Way
35mDecoding 'Community Over Code'
38mHow To Be a Responsible Open Source Citizen