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 need to 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 enters the Islandora Project in one of three ways:

Idea for Plugin

Send a message to the [http://groups.google.com/group/islandora-dev Development Mailing List] outlining the idea. This allows us to solicit feedback from the wider community. "I would like to develop this. For these reasons. To meet these requirements."

The idea is brought up in the weekly developer meeting (NOTE: LINK) by the person who proposed it and either:

A consensus is reached in the weekly developer meeting and a committer will create a [https://jira.duraspace.org/secure/Dashboard.jspa JIRA Ticket] outlining the idea. This should be the beginnings of a project plan. TODO: LINK HERE TO PROJECT PLAN PAGE.

Or the issue is elevated to the road-map team for a decision.

A project plan (LINK) is developed to guide the development going forward.

The new module is created in the developers own github

Discussion continues as the project moves forward.

When the module is ready for its first release it is reviewed and forked into the Islandora Github.

Bug

Bug report is submitted to JIRA

If necessary this is discussed in the committers meeting.