ASFRepository

ASF Software Repository

Road Map

• 1. Agree on Repository goals

• 2. Agree on Repository requirements

• 3. Agree on URI syntax

• 4. Recommend best practices for

  • 1. Client Tools

  • 2. Publishing Tools

  • 3. Management Tools

Mailing List: subscribe | unsubscribe | Archive

Apache Software Repository Goals

A repository architecture/implmentation for software artifacts for streamlining distribution.

• Open (language independent, publisher/reader/maintainer independent)

• Scalable (can be mirrored, distributed, etc.)

• Programmatic (tools driven)yet also manually maintainable when needed

• Secure (both for publishing and downloading)

• Extensible (Apache teams can annotate with their own metadata)

Non-Goals:

• Artifact installation/site indexing (ala Perl Package Manager, PPM)

---

ASF Software Repository Requirements

• ASF Repository shall:

  • only host artifacts approved by a PMC

  • be accessible to the public via http

  • be mirrorable.

  • allow browsing and downloding of artifacts by humans via normal web browser

  • Provide tools for the management of the artifacts

• ASF Repository should (optionally)

  • provide metadata about a project,

    • its components

    • its dependencies

    • its artifacts

    • list of version available

    • url's to find specific versions of an artifact.

  • Provide tools for the management of the artifacts/project metadata

  • Allow for low cost maintance by hand without tool support.

• ASF Repository shall not

  • Host any artifact in violation of a license, or IPR.

---

• /ToDo -- requires decisions

• /Decisions

• /Terminology

• /Proposals

• /Metadata

• /Components

• /Issues

• /Participants

---

Interested Parties

• Gump]

• Maven

• Ruper & Ruper2

• Greebo

• CJAN

Reference Information

• Apache Mirroring Information

• http://www.ibiblio.org/maven/

• http://gump.dotnot.org/repository/

  • JSR 56 - JNLP

  • Java Web Start (JNLP RI)