Skip to content

incubating.md

Latest commit

 

History

History
63 lines (44 loc) · 3 KB

incubating.md

File metadata and controls

63 lines (44 loc) · 3 KB

Incubating PerlOnJava under the Apache Software Foundation (ASF) or aligning it with The Perl Foundation (TPF) could offer distinct advantages:

Apache Software Foundation (ASF)

  1. Governance & Neutrality

    • Apache’s meritocratic governance model ensures decisions are community-driven, reducing reliance on a single maintainer.
    • Neutrality attracts contributors/companies wary of vendor lock-in.

  2. Collaboration & Ecosystem

    • Integration with Apache’s JVM-centric projects (e.g., Groovy, Apache Commons) could foster interoperability.
    • Access to Apache’s infrastructure (CI/CD, legal, mailing lists) and mentorship via the Apache Incubator.

  3. Enterprise Adoption
    Apache projects are widely trusted in enterprise environments, which could boost adoption for Java-centric Perl use cases.

  4. Longevity
    ASF’s emphasis on sustainability reduces the risk of abandonment if the original maintainer steps back.

Drawbacks:

  • Bureaucratic processes (voting, releases) might slow rapid iteration.
  • The Perl-JVM niche may not align tightly with Apache’s existing ecosystem.

The Perl Foundation (TPF)

  1. Perl Ecosystem Synergy

    • Direct alignment with Perl’s core community and goals (e.g., Perl 5/6 interoperability, toolchain modernization).
    • Potential funding via TPF grants or collaboration with Perl Core development.

  2. Simpler Governance
    Less overhead than ASF, allowing faster iteration while still gaining community oversight.

  3. Advocacy
    TPF could promote PerlOnJava as part of Perl’s multi-runtime future (JVM, GraalVM, etc.).

Drawbacks:

  • Limited JVM-specific expertise/resources compared to Apache.
  • Less visibility in enterprise Java circles.

Other Options

  • Eclipse Foundation: Focused on JVM/Java tools (e.g., Eclipse IDE). Could align with Java-centric developers but lacks Perl-specific ties.
  • Software Freedom Conservancy: Provides administrative support (legal, fiscal) without imposing governance models.
  • Independent + Open Collective: Retain autonomy while using platforms like Open Collective for funding/transparency.

Why Consider Incubation?

  • Sustainability: Foundations mitigate "bus factor" risks.
  • Credibility: Institutional backing attracts contributors and enterprise users.
  • Resources: Legal, infrastructure, and community-building support.

Key Questions for PerlOnJava

  • Is the goal to integrate deeply with Java ecosystems (favoring ASF) or expand Perl’s reach (favoring TPF)?
  • Does the project need enterprise adoption (ASF) or Perl community alignment (TPF)?

Recommendation

If PerlOnJava aims to bridge Perl and Java ecosystems for enterprise use, Apache Incubator is a strong fit. If the focus is Perl-first innovation, TPF or independence may be better. Hybrid models (e.g., TPF governance + collaboration with Apache JVM projects) could also work.