ASF Software Repository
2006-02 Summary
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: ![[WWW]](/wiki/modern/img/moin-www.png){kind=small}
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.
Host any development snapshots (they should be at
http://cvs.apache.org/repository/).
ToDo -- requires decisions
Interested Parties
Reference Information