Page History

...

Note this is accurate as of October 2025.

...

...

Synthesis: Patterns Across Case Studies

...

1. Early alignment matters
Projects that thrive (e.g.for example, Flink, Iceberg, and Airflow) had mentors who clarified ASF expectations early — , especially around releases, mailing-list use, and decision-making.
Early reinforcement prevents years of off-list or GitHub-only habits that are hard to undo later.

2. Balance guidance with independence
Over-involvement can mask weak community ownership.
Mentors succeed when they teach why ASF practices exist, then step back and let the PPMC lead, intervening only when culture or process drifts.

3. Watch for silent warning signs
Long gaps between releases, single-company commit patterns, or mailing lists that go quiet are all early indicators of risk.
Mentors should surface these gently before they become structural problems.

4. Coordinate among mentors
Consistent messaging avoids confusion.
Podlings that received mixed advice (e.g., on release timing or voting scope) often stalled until mentors and the IPMC clarified expectations together. 5. Model transparent communication
When mentors consistently reply on-list, summarize outcomes, and reference policy links, podlings mirror that behavior.
Mentor silence or private side-chats often lead to slower culture adoption.

65. Recognize when withdrawal or retirement is healthy
As seen with Zipkin or Mesos, not every project needs to remain at Apache forever.
Helping a community make that decision transparently can be as valuable as guiding one to graduation.

76. Keep mentorship time-bounded
Effective mentors plan their exit — ensuring . Ensuring the PPMC can self-govern before graduation and remains functional without external promptingwithout external prompting.

7. Time in incubation is a signal, not a goal
Incubation length varies from months to years. Fast graduation can show strong existing maturity (as with Flink) but may hide dependence if mentors push too soon. Longer incubation can simply reflect complex IP clearance (NetBeans) or gradual culture-building (Superset). Mentors should judge progress by ASF maturity, including steady releases, independent decisions, and visible community growth, not by time alone.

8. Mentorship style should adapt to the podling’s phase
Early phases need hands-on clarification of ASF basics such as releases, voting, and mailing lists. Later stages benefit more from coaching and accountability than instruction. Mentors who shift from directing to advising help the PPMC gain true independence before graduation.

9. Maintain context after graduation
Graduation isn't the end of learning. A short transition period where mentors remain subscribed or available helps the new TLP stabilize and handle first-year governance and reporting challenges confidently.

10. Reflect and share lessons back to the IPMC
Each incubation reveals new edge cases in culture, licensing, or governance. Mentors strengthen the whole Incubator when they share anonymized insights that inform future guidance and policy updates.

...

Case Study 1: Apache Pinot

...

- Strong Community Growth and Graduation

Entry

• Created at LinkedIn in 2013 and open-sourced in 2015.
• Entered the Apache Incubator in October 2018.

...

• Attract contributors from outside the founding company
• Deliver consistent ASF-compliant releases
• Embed transparency and consensus in their processes

...

Case Study 2: Apache Wave

...

- Stalled Podling and Retirement

Entry

• Originated at Google as “Wave in a Box.”
• Entered the Apache Incubator in December 2010.

...

After seven years without progress, Wave was retired in April 2018.
Current Status: Retired Podling

Takeaway

Even a high-profile donation can fail if a podling does not establish a sustainable, diverse community and adopt an ASF-style transparency approach.

...

Case Study 3: Apache Superset

...

- Struggles and Recovery

Entry

• Created at Airbnb.
• Entered the Apache Incubator in July 2017.

...

Superset shows that a podling can recover from early challenges if mentors persist, the community adopts ASF release discipline, and decision-making shifts to transparent forums.

...

Case Study 4: Apache Flink

...

- Rapid Graduation

Entry

• Originated as the Stratosphere research project at TU Berlin.
• Entered the Apache Incubator in April 2014.

...

Flink demonstrates that incubation can be very short when a project enters with an existing, well-organized, and diverse community that quickly adopts ASF practices.

...

Case Study 5: Apache Iceberg

...

- Building a New Standard

Entry

• Created at Netflix and donated to the ASF.
• Entered the Apache Incubator in November 2018.

...

Iceberg shows that projects with strong corporate origins can graduate healthily when they diversify, deliver ASF-compliant releases, and maintain vendor neutrality.

...

...

Case Study 6: Apache Blur

...

- Long Stagnation, Retired

Entry

• Search engine built on Lucene.
• Entered the Apache Incubator in July 2012.

...

Blur shows that inactivity and failure to build a community often lead to retirement, no matter how promising the technology.

...

Case Study 7: Apache MXNet

...

- Vendor Dominance and Retirement

Entry

• Originally developed at the University of Washington, later heavily backed by AWS.
• Entered the Apache Incubator in September 2017.

...

• Contributor diversity did not improve significantly.
• As activity declined, the ASF Board approved retirement.
• Retired to the Apache Attic in September 2023.

Current Status: Retired TLP

Takeaway

MXNet illustrates the risks of concentrated corporate influence. Even with a strong technical foundation and corporate backing, a project cannot thrive at Apache without multi-organization contributor diversity, mailing-list-based consensus, and shared governance.

...

Case Study 8: Apache Airflow

...

- From Company Project to Global Community

Entry

• Created at Airbnb in 2014 as a workflow orchestration system.
• Entered the Apache Incubator in March 2016.

...

• Releases: Began producing incubating releases in 2016; later established a steady cadence.
• Community growth: Quickly broadened participation beyond Airbnb — - contributors from Google, Polidea, and independents became committers.
• Governance: Shifted all decision-making onto dev@ mailing lists.
• Ecosystem impact: Widely adopted in data-engineering ecosystems; integrations accelerated growth.
• Mentorship: Mentors emphasized neutrality and rotating release managers.

...

• Rotating release managers
• Strong mailing-list culture
• Early outreach beyond the founding organization

...

Case Study 9: Apache Zipkin

...

- Withdrawing from the Incubator

Entry

• Distributed tracing system, originally created at Twitter in 2012.
• Entered the Apache Incubator in July 2018.

...

• Community context: An established ecosystem already existed under the OpenZipkin GitHub organization.
• Challenges: Development and issue tracking remained primarily in the external GitHub organization; ASF mailing lists were under-utilized.
• Releases: No incubating ASF releases were produced.
• Mentorship: Concerns were raised about lack of ASF alignment (releases, infrastructure, governance).

...

Zipkin illustrates that incubation can be a trial of fit. Sometimes even a popular project determines that continuing outside the ASF model better serves its goals; in such cases, withdrawal can be an appropriate outcome.

...

Case Study 10: Apache Trafodion

...

- Graduation Followed by Retirement

Entry

• Donated by HP as a transactional SQL-on-HBase database.
• Entered the Apache Incubator in May 2015.

...

• Contributor diversity remained limited; community activity slowed.
• The project was retired to the Attic in March 2021.

Current Status: Retired TLP

Takeaway

Graduation is not sufficient for survival. Without long-term diversity and a steady inflow of contributors, even graduated TLPs may be retired.

...

Case Study 11: Apache NetBeans

...

- Migrating a Mature Codebase

Entry

• Long-standing IDE originally developed by Sun Microsystems and later maintained by Oracle.
• Donated by Oracle and entered the Apache Incubator in October 2016.

...

NetBeans shows that incubation isn’t just for new projects — - even mature, widely used codebases must:

• Complete IP clearance at ASF standards
• Transition governance to ASF lists
• Demonstrate the ability to make ASF-compliant releases

...

Case Study 12: Apache ECharts

...

- Global and Multilingual Community

Entry

• JavaScript-based data-visualization library created at Baidu.
• Entered the Apache Incubator in August 2018.

...

ECharts demonstrates that ASF incubation is effective for globally popular projects, even when most contributors start in a non-English environment. Inclusivity and multilingual practices are vital for sustaining global diversity.

...

Case Study 13: Apache Hadoop

...

- Ecosystem Catalyst

Entry

• Originated as part of Yahoo!’s search infrastructure and donated to the ASF.
• Entered the Apache Incubator in January 2006.

...

Hadoop showed that transparent, collaborative governance at ASF scale can catalyze entire technology ecosystems.

...

Case Study 14: Apache Cassandra

...

- From Corporate to Community

Entry

• Initially developed at Facebook and open-sourced in 2008.
• Entered the Apache Incubator in March 2009.

...

Cassandra’s evolution shows that early establishment of transparent, multi-organization governance is essential to maintaining community neutrality and resilience against vendor concentration over time.

...

Case Study 15: Apache Kafka

...

- Vendor-Neutral Governance at Scale

Entry

• Created at LinkedIn as a distributed streaming platform.
• Entered the Apache Incubator in July 2011.

...

Kafka is often cited as a strong multi-company community; as its commercial ecosystem expanded, the community continued to discuss how to preserve vendor-neutral governance.

...

Case Study 16: Apache Pulsar

...

- Modern Distributed Messaging with Transparent Governance

Entry

• Originally developed at Yahoo! for cloud messaging.
• Entered the Apache Incubator in June 2017.

...

Pulsar’s steady releases and strong mentor collaboration show how consistent transparency accelerates maturity and trust.

...

Case Study 17: Apache APISIX

...

- Cloud-Native Global Growth

Entry

• Developed by Shenzhen-based API7.ai as an open-source API gateway.
• Entered the Apache Incubator in October 2019.

...

APISIX highlights ASF’s ability to host fast-moving, globally distributed, cloud-native projects that balance corporate and independent participation.

...

Case Study 18: Apache IoTDB

...

- Academic Research to Industrial Adoption

Entry

• Created at Tsinghua University as part of the TSFile research project.
• Entered the Apache Incubator in November 2018.

...

IoTDB shows that academic research can evolve into sustainable open-source communities when they adopt transparent governance and regular release practice.

...

Case Study 19: Apache Spark

...

- From Research to Broad Adoption

Entry

• Originated at UC Berkeley’s AMPLab and open-sourced in 2010.
• Entered the Apache Incubator in June 2013.

...

Spark demonstrates that academic innovation can scale to global enterprise adoption when guided by transparent governance and frequent ASF-compliant releases.

...

Case Study 20: Apache Storm

...

- Early Stream-Processing Success

Entry

• Created at BackType and later acquired by Twitter.
• Entered the Apache Incubator in September 2013.

...

Storm was early in real-time stream processing at Apache, showing that small teams can succeed when they fully embrace ASF release discipline and transparent development. Now in a stable maintenance phase, it continues to demonstrate the value of long-term stewardship within the ASF model.

...

Case Study 21: Apache Mesos

...

- Cluster Management at Scale

Entry

• Originated as a UC Berkeley research project.
• Entered the Apache Incubator in December 2010.

...

• Activity declined as industry focus shifted to Kubernetes.
• The project was retired to the Apache Attic in October 2021.

Current Status: Retired TLP

Takeaway

Mesos was once core infrastructure at scale; its retirement shows that sustaining relevance requires continuous community renewal and adaptation to industry change.

...

Case Study 22: Apache Druid

...

- High-Performance OLAP at ASF Scale

Entry

• Originally created at Metamarkets for real-time analytics.
• Entered the Apache Incubator in February 2018.

...

Druid demonstrated that ASF incubation can support enterprise-focused, cloud-native analytics software while maintaining neutral governance.

...

Case Study 23: Apache Parquet

...

- Shared Foundation for Analytics

Entry

• Originally developed by Twitter and Cloudera for columnar data storage.
• Entered the Apache Incubator in April 2014.

...

Parquet illustrates how incubation can steward a neutral, shared standard that supports the broader ASF analytics ecosystem.

...

Case Study 24: Apache Arrow

...

- Cross-Language Interoperability

Entry

• Founded as a collaboration among multiple ASF projects to create a shared in-memory columnar format.
• Entered the Apache Incubator in February 2016.

...

Arrow shows that ASF governance can successfully coordinate long-term, cross-language data standards serving a broad ecosystem.

...

Case Study 25: Apache NiFi

...

- From Government Research to Open Collaboration

Entry

• Originated within the U.S. National Security Agency (NSA) as “NiagaraFiles.”
• Donated to the ASF through a U.S. government release process.
• Entered the Apache Incubator in November 2014.

...

NiFi proved that government-developed software can thrive under ASF transparency and community-driven collaboration.

...

Case Study 26: Apache Kylin

...

- Early China-Initiated ASF TLP

Entry

• Developed at eBay China for OLAP on Hadoop.
• Entered the Apache Incubator in November 2014.

...