This Islandora project, including Islandora Labs, operates under the Islandora code of conduct. By participating in this project, you agree to abide by its terms. Please report inappropriate behaviour to [email protected].
Islandora, and Islandora Labs, invites community discussion on the following channels. If you are not sure you want to create an issue or pull request yet, feel free to discuss this project with us here:
- the IRC channel, #islandora, on freenode.net
- our Google Group/mailing list,
- our bi-weekly committers' calls, on Skype and open to everybody (contact [email protected] to join)
- our various Interest Groups
All contributions to Islandora Oral Histories Solution Pack are welcome: use-cases, documentation, code, bug reports, feature requests, etc. You do not need to be a programmer to contribute!
Regardless of how you want to contribute to Islandora Oral Histories Solution Pack, start by opening a Github issue. Someone (probably one of the maintainers) will respond and keep the discussion going.
As with all projects in Islandora Labs, all contributors to a pull request must have an Islandora CLA ([Contributor License Agreement]) on file before it can be merged. Here, a contributor is defined as the author of a git commit.
In Islandora Labs, the policies for merging may be different from the standard [Islandora Committer's Workflow]. These worfflow policies are set at the discretion of the Current Maintainer, as defined below in the sections below:
If you use Islandora Oral Histories Solution Pack and you have documented a task for yourself, consider sharing it with other users. We'd be happy to put it on the Islandora Oral Histories Solution Pack wiki or link to it if you'd rather maintain it somewhere else.
We love hear about how you want to use Islandora Oral Histories Solution Pack! In order to help us understand a new feature request, we ask you to provide us with a structured use case following this template:
| Title (Goal) | The title or goal of your use case |
|---|---|
| Primary Actor | Repository architect, metadata specialist, repository admin |
| Scope | The scope of the feature. Example: usability, performance |
| Level | The priority the use case should be given; High, Medium, Low |
| Story | A paragraph of text describing how this feature should work a what it should accomplish |
Additional examples:
- One per list bullet
Additional Remarks:
- One per list bullet
To report a bug you should open an issue that summarizes the bug. Set the Issue Type to "Bug".
In order to help us understand and fix the bug it would be useful if you could provide us with:
- The steps to reproduce the bug. This includes information about e.g. the Islandora version you were using along with version of stack components.
- If applicable, some sample data that triggers the bug.
- The expected behavior.
- The current, incorrect behavior.
Feel free to search the issue queue for existing issues that already describe the problem; if there is such a ticket please add your information as a comment.
If you want to provide a pull along with your bug report:
In this case please send us a pull request as described in section Create a pull request below.
Contributions to the Islandora codebase should be sent as GitHub pull requests. See section Create a pull request below for details. If there is any problem with the pull request we can work through it using the commenting features of GitHub.
-
For all code contributions, please use the following process in order to to prevent any wasted work and catch design issues early on.
- Open an issue and assign it the label of "enhancement" or "feature request", if a similar issue does not exist already. If a similar issue does exist, then you should consider participating in the work on the existing issue.
- Comment on the issue with your plan for implementing the issue. Explain what pieces of the codebase you are going to touch and how everything is going to fit together.
- The Islandora Oral Histories Solution Pack maintainers will work with you on the design to make sure you are on the right track.
- Implement your issue, create a pull request (see below), and iterate from there.
All issues should be worked on in separate git branches. The branch name should be the same as the Github issue number, e.g., issue-243.
Take a look at Creating a pull request. In a nutshell you need to:
- Fork the Islandora Oral Histories Solution Pack repository to your personal GitHub account. See Fork a repo for detailed instructions.
- Commit any changes to the issue/topic branch in your fork. Comments can be as terse as "Work on #243.", etc. but you can be more descriptive if you want. However, please refer to the issue you are working on somewhere in the commit comment using Github's '#' shortcut, as in the example.
- Send a pull request to the Islandora Oral Histories Solution Pack GitHub repository that you forked in step 1 (in other words, https://github.com/digitalutsc/islandora_solution_pack_oralhistories).
You may want to read Syncing a fork for instructions on how to keep your fork up to date with the latest changes of the upstream (official) Islandora Oral Histories Solution Pack repository.
Islandora Oral Histories Solution Pack is licensed under GPL version 3 or higher. By opening a pull request or otherwise contributing code to the Islandora Oral Histories Solution Pack codebase, you transfer non-exclusive ownership of that code (you retain ownership of your code for other purposes) to the Islandora Oral Histories Solution Pack maintainers for the sole purpose of redistributing your contribution within the Islandora Oral Histories Solution Pack codebase under the conditions of the GPLv3 license or higher and subject to the Islandora CLA ([Contributor License Agreement]). You also warrant that you have the legal authority to make such a transfer.
This CONTRIBUTING.md file is based heavily on the CONTRIBUTING.md file included with Islandora Foundation modules and the Move to Islandora Kit, as well as Rosemary Le Faive's [Islandora Labs CONTRIBUTING.md template] (https://github.com/rosiel/Contributing-Templates/blob/master/CONTRIBUTING.md).