How to Contribute Code or Documentation

How to get involved

Development for ArchivesSpace is conducted in sprints, during which new features are implemented, bugs are fixed, and chores, such as updating part of the application stack, are completed.  

Developers and others willing to update or create documentation are welcome to contribute in any given sprint. If you have experience with ArchivesSpace and are willing to take on work considered a priority by the community, you are welcome to join an ArchivesSpace scrum call and commit to take on open issues raised in sprint planning. Please contact us at if you are interested in getting involved.

If your institution has a specific issue or bug to which you would like to commit developer resources, you can indicate this to the ArchivesSpace team by logging an issue in JIRA and indicating you have a developer that will be taking on this work. For larger contributions, please review our evaluation process and contact ArchivesSpace Program Manager Christine Di Bella with any questions or to begin the process.

The ArchivesSpace release process presumes that the master branch in archivesspace/archivesspace is maintained as stable, deployable code, and that a separate branch or repository is used to commit changes prior to release.

Nuts and bolts of code contribution

The ArchivesSpace source code is available on Github. To contribute code, please see the instructions to check out the repository, make changes, commit the code,  and submit a pull-request .

All code contributions should include unit tests and will follow the best practices and standards.