Unable to render {include} The included page could not be found.

This Version

This documentation relates to an earlier CollectionSpace version.

This documentation is for version 3.2.1. The current version is 5.0.
View this page in the current documentation or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

CollectionSpace manages its source code with the open-source Git version control system, in publicly-accessible repositories on the cloud-based GitHub application.

Icon

Prior to version 2.1, CollectionSpace managed its source code via the Subversion (SVN) version control system, on a a project-maintained SVN repository at source.collectionspace.org. That SVN repository is now a read-only, point-in-time archive. The project's current code is maintained in GitHub, as noted above.

CollectionSpace Repositories

CollectionSpace's source code repositories are accessible via:

https://github.com/collectionspace/

There are repositories for all three layers of the CollectionSpace system:

There is also a Tools repository for auxiliary tools and scripts. (One representative example is the mini-build, a tool to simplify configuration of a CollectionSpace instance.)

Access to the Repositories

Consistent with the public status of work on the CollectionSpace project, all of the repositories are open for read-only, anonymous access. Any changes to that status will be posted here.

Commits (writes) to the repositories require a user name and password. User accounts can be requested by writing to the Work Team Mailing List.

JIRA Integration

There is a degree of integration between the project's source code repository and its issue tracking system. For instance, any commits made to a repository whose comments begin with JIRA issue numbers will automatically be posted to the relevant JIRA issue(s). Examples:

To post details of a repository commit to JIRA Issue CSPACE-15:

To post details of a repository commit to two JIRA issues, Issue CSPACE-15 and Issue CSPACE-21:

To post details of a repository commit that doesn't involve a JIRA issue:

FishEye Instance

The CollectionSpace project also provides an instance of Atlassian FishEye, a web-based interface for exploring and tracking changes within the project's source code repositories, at:

http://fisheye.collectionspace.org

As noted by Jesse Martinez:

Fisheye [is ...] a tool for viewing committed code, keeping track of code changes, viewing code diffs, creating custom RSS feeds from committed code, viewing charts of repository activity, searching, and browsing all within a tidy web interface. Additionally, it integrates nicely within JIRA [...] when tacking on JIRA issue numbers to commit comments.

Licensing

CollectionSpace is licensed under the Educational Community License (ECL), Version 2.0. For details, see Licensing.

Javadoc Documentation for the Source Code

Javadoc documentation is currently available for the Services Layer source code at http://nightly.collectionspace.org/apidocs/services

See Also

How to check out CollectionSpace's source code

  • No labels