Some of our developers use
from JetBrains and we display this logo in recognition of their free open source developer's licenses.
Getting ConnectedMailing lists, weekly open technical calls, etc. are all listed on the Get in touch! page.
All of our code is hosted on Github in the projecthydra account.
On-line Resources and Tutorials
For New and Potential Adopters:
- new adopters and potential adopters may find the pages here useful: http://projecthydra.org/
- See Hydra Heads (Known Implementations) for more information about each of the Hydra Heads.
- A Hydra Head interactive tutorial has been developed - see under the 'For developers' section below.
For Architecture Level:
- Code is hosted on Github: https://github.com/projecthydra
- Github’s wikis for projecthydra git repositories are targeted to developers: https://github.com/projecthydra/hydra-head/wiki
- Contributing to Project Hydra includes guidelines on bug reporting, using github, documenting code, testing, submitting and merging pull requests
Where Can Developers Get Training?
A developer needs a variety of skills, which are outlined in the Hydra Camp sylabus. The community offers multi-day public Hydra Camps at least once a year in Europe and North America. Additional single and half-day workshops are frequently offered in conjunction with other major Library and Library Technology Conferences. Hydra Camps are typically facilitated by Data Curation Experts who can also be engaged for private Hydra Camp events or custom training engagements. Contact Information is available at http://curationexperts.com
Tickets: Reporting Bugs & Requesting Features
We use Github, issues as our project tracker. Please report issues against the git repository for the specific gem you are having issues with. If you are unable to identify the gem in which your problem is occurring, please e-mail the firstname.lastname@example.org mailing list to help narrow your issue.
For examples, see the issues here: https://github.com/projecthydra/hydra-head/issues
To report a security vulnerability, email email@example.com and the Steering Group will coordinate the community response. In your message, please document to the best of your ability cases where the vulnerability is applicable, the potential negative effects, and any known workarounds or fixes to mitigate the risk. Steering will communicate this to the Partners and the rest of the community in a timely fashion.