Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor text edits

...

  • Attract contributors from outside the founding company,

  • Deliver consistent ASF-compliant releases, and

  • Embed transparency and consensus in their processes.

...

Case Study 2: Apache Wave — Stalled Podling and Retirement

...

  • A strong technical foundation,

  • Widespread industry adoption, and

  • Corporate backing,

a project cannot thrive at Apache without multi-organization contributor diversity, mailing-list–based consensus, and shared governance.

...

  • Rotating release managers,

  • Strong mailing list culture, and

  • Early outreach beyond the founding org.

...

Case Study 9: Apache Zipkin — Withdrawing from the Incubator

...

  • Community context: An established ecosystem already existed under the OpenZipkin GitHub organisationorganization.

  • Challenges: Development and issue tracking remained primarily in the external GitHub organisationorganization; ASF mailing lists were underutilisedunderutilized.

  • Releases: No incubating ASF releases were produced.

  • Mentorship: Concerns were raised about lack of ASF alignment (releases, infra, governance).

...

  • Complete IP clearance at ASF standards,

  • Transition governance to the ASF lists, and

  • Prove they can make ASF-compliant releases.

...

Case Study 12: Apache ECharts — Global & Multilingual Community

...