Navigating the Incubator Trenches
summary
Apache incubation focuses on turning vendor or single‑org code into a meritocratic community: require a software grant (SGA) or IP clearance, prohibit LGPL/strong copyleft in donated source, and insist releases are source‑only with “incubating” in the distribution name (Gradle wrapper jars/binaries are disallowed). Projects can use GitHub as primary via teams and a mirror tool gitbox (95% repo automation). Emphasize frequent releases, strict license headers, and mailing-list-first archived decision making to prove governance and earn graduation.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:30What is the Incubator?
- 4:35Why Incubate?
- 6:56How to Incubate
- 10:46Discuss & Vote
- 14:08Acceptance
- 17:49Migrating Development Over
- 27:37Keeping Your Source Code Clean
- 35:03Grants & IP Clearance
- 38:02Build a Community
- 41:05Dependencies
- 43:41Getting a Release Out the Door
- 45:46Release Contents
- 46:40Naming Your Release
related talks
46mHow to Slide Your Release Pass the Incubator
28mReleasing binaries in the Incubator
29mNavigating Podling Releases: Achieving Success in the Apache Incubator
41mHatching The Clutch - A Guide to the Apache Incubator
38mAdvice to Incubator Mentors
19mAnt Group’s Open Source Incubator: Aligning With CNCF Maturity Framework
35mDecoding 'Community Over Code'
22mKeynote: The Apache Way