Wir Waren So Frei
thousands of personal photographs and full-length videos documenting the fall of the Berlin Wall.
Developers

CollectiveAccess is developed by a dedicated crew, some employed by Whirl-i-Gig and some by partner institutions. We welcome volunteers and code contributions. If you would like to get involved, send us an email at support@CollectiveAccess.org. We'd be happy to have you onboard!

To better coordinate collaboration amongst developers, the project maintains various tools and resources described below. You are welcome to use these tools to access CollectiveAccess code and communicate with the developers.

Source Code
SVN repository access

The CollectiveAccess development team uses Subversion (aka. SVN) version control software to manage project source code. SVN keeps track of all changes made to the code and facilitates simultaneous work by geographically dispersed developers.

Anonymous access to the CollectiveAccess SVN repository is available at http://collectiveaccess.svn.whirl-i-gig.com. The repository layout is thus:

PathDescription
/CollectiveAccess/trunkContains "trunk" source code. When checking out the source for use always use the trunk unless you know why you should do otherwise.
/CollectiveAccess/branchesContains development branches. Don't use this code unless you know why you should.
/CollectiveAccess/tagsContains snapshots of releases. Check out code from here if you want a specific release rather than the bleeding edge code in /CollectiveAccess/trunk
/CollectiveAccess/frontendsContains various presentation front-ends, including Pawtucket (web), Woonsocket (iPhone) and Pascoag (Flash-based kiosk).
/CollectiveAccess/distContains files used by the CollectiveAccess Debian package.
/CollectiveAccess/projectsContains files for various side projects. Not publicly accessible.

Web-based SVN browser
A web-based SVN repository browser is maintained at http://svn.CollectiveAccess.org.
Bug Tracking
JIRA
A JIRA bug tracker is available at http://bugs.CollectiveAccess.org:9000. Please file all bug reports and feature requests on JIRA. If you have any questions prior to filing a report feel free to email us at support@CollectiveAccess.org.
Developer Documentation
Wiki
A wiki is maintained for ongoing documentation and development notes at http://wiki.CollectiveAccess.org. The wiki is open to all. All users and developers are encouraged to create new pages and edit existing ones as needed. If you find that something needs more explanation please put it on the wiki!
Class documentation
Automatically generated class documentation for all CollectiveAccess library code is generated nightly and available at http://providence.whirl-i-gig.com/doc/libdocs.