The community has generated a wide range of wonderful tools and additions to expand the utility of Islandora. Some of these contributions make it into the core set of modules that constitute an Islandora release, while others are shared more informally for use by the community as needed. In order to recognize these contributions and officially adopt them into future releases, we require that contributors complete a Contributor License Agreement or Corporate Contributor Licencse Agreement. This license is for your protection as a contributor as well as the protection of the Foundation and its users; it does not change your rights to use your own contributions for any other purpose. List of current Islandora iCLA/cCLAs.
To contribute your code, please follow the steps outlined in our Licensed Software Acceptance Procedure. If you would prefer not to contribute your code to the Foundation, or you have developed a tool that you don't believe will fit into general use, please contact us to have it listed on our Modules page so that it can be more readily discovered by the community.
List of Contributed Software
Other Ways to Contribute
To make a financial contribution to Islandora and to take a more active hand in guiding the future of the project, please consider joining the Islandora Foundation as a Member ($2000), Collaborator ($4000), or Partner ($10,000). For more information about the benefits of membership, please visit the Islandora Foundation pages or contact us.
The Islandora community has contributed to the success of the project from the very beginning. These contributions go far beyond volunteer coding - from participation in the user lists and camps, to pointing out bugs and requesting features, to simply demonstrating the wide range of what Islandora can do in your repos. We would like to offer our thanks and recognition for this support and have highlighted several opportunities to formally credit this effort in the form of defined volunteer roles:
Duties: Review pull requests over a release cycle - flag items that may constitute architectural changes to the code base, or which may require more substantial code review. The Release Manager will also attend Committers Calls every two weeks and participate actively in the reassignment/management of JIRA tickets, and attend Roadmap meetings over a release cycle to guide the release schedule. The Release Manager also packages code to be released.
Duties: Component Managers take responsibility for a single module or collection of modules, assigning individual review tasks to Reviewers and referring the results to the Release Manager for final disposition of the pull request.
Duties: Installing and running the latest Islandora release candidate code and testing for bugs. No programming experience required! We are looking for people with a general familiarity with islandora to try out the latest releases and put them through their paces to look for bugs and make suggestions.
Duties: Checking modules readme files and updating the Islandora Documentation Wiki to reflect new releases.
Each release we audit our README and LICENSE files. Auditors will be responsible for auditing a given component by verifying that these document are current and fit into their proper templates..