How Islandora Code gets Made

Contributing to Islandora

Islandora is committed to being a great open source project and to help improve that we are introducing new policies to improve our transparency. Communication is key to any successful project and we want to make sure the community is able to contribute in all discussions.

All new features should be discussed openly on the development forum giving the full community the opportunity to make recommendations and contribute to the development. The feature will then be broken down into tasks that will be managed by jira tickets. Bugs will simply be represented as a bug ticket in the jira system.

Code Repository

Github supports repositories for the Islandora and the DGI code repositories. Islandora is considered to be the master repository and is co-maintained by UPEI/DGI, and the DGI repository is a downstream repository that is maintained by DGI. We are moving to a new system of governance with the Islandora Foundation.

For code to be accepted into the master Islandora repository, a developer must publish the code in a forked repository and make a pull request. After the code has been reviewed and signed off then the code will be merged into the project. We use Travis for unittesting and Jenkins for integration testing/docs. Tests do not supply 100% coverage and Jenkins is currently unreliable so smoke testing of all pulls by reviewers is advisable. It is also advisable to run the tests and style checks on a module that is being altered before submitting a pull request. The command Travis runs for style checking in Drupal 7:

• drush coder-review --reviews=production,security,style,i18n,potx,sniffer module_name

Questions about participating in the Islandora project can be directed to islandora-dev@googlegroups.com.