You need an account for this wiki so that you can contribute to Hydra's pages. If you do not have one already, please request an account by sending an email to email@example.com.
This is a closed list available to Hydra Slack administrators. Send email to firstname.lastname@example.org if you're having trouble with Slack.
Hydra-Releases (1-2 messages a month)
Subscribe to this list at https://groups.google.com/forum/#!forum/hydra-releases/join if you want notification of every new point (bugfix) release of Hydra and related software. Most people will not need this density of release information. Major releases are notified to the Hydra-Announces list.
Hydra-Announces (2-5 messages a month)
Subscribe to this list at https://groups.google.com/forum/#!forum/hydra-announces/join if you want the minimum mailings - only the most important security, major release, and event announcements
Hydra-Community (5-10 messages a week on average)
Subscribe to this list at https://groups.google.com/forum/#!forum/hydra-community/join if you want a broader spectrum of non-technical information related to Hydra
- All messages to Hydra-Announces are sent also to the Hydra-Community list - if you’re subscribed to Hydra-Community, you don’t need to subscribe to Hydra-Announces
Hydra-Tech (15-20 messages per week on average)
Subscribe to this list at https://groups.google.com/forum/#!forum/hydra-tech/join if you want to follow current technical discussions about Hydra and all of its components
- All messages to Hydra-Announces are sent also to the Hydra-Tech list - if you’re subscribed to Hydra-Tech, you don’t need to subscribe to Hydra-Announces
Subscribe to this list at https://groups.google.com/forum/#!forum/hydra-metadata/join if you want to get help with or discuss metadata issues in Hydra
This is a closed list available only to formal Hydra Partners and is typically used only for community governance discussions
This is a closed list available to Steering Group members and is typically used for community maintenance and licensing activities
If you have general questions about adopting Hydra, project planning, requirements definition, etc., feel free to e-mail the Hydra-Community list
If you have technical questions about implementing or developing with Hydra, feel free to e-mail the Hydra-Tech list
If you have questions about becoming a partner, code licensing, or usage rights, please e-mail Hydra-Steering
While the #projecthydra room in IRC is in continuous use, most conversations now take place on Slack (as of spring/summer 2016).
If you don't already use an IRC client, connect through the web at http://webchat.freenode.net/
Nickname: pick a name,
For more information on how to start using irc, check out the instructions on the code4lib site.
Several Hydra Partners use Slack within their institutions for team communication and collaboration. There is a Hydra Slack team that is used for discussion, questions, announcements, interest groups, and working groups. Anyone can create a new channel within the Hydra Slack team once they have registered for an account.
Slack team: https://project-hydra.slack.com
Joining a Slack team requires an invitation, but anyone can generate an automatic invite using the following form: http://slack.projecthydra.org/. (If this form does not work, you may want to use this backup form: https://docs.google.com/forms/d/1cRJaOTo2pHAeMzfE3hKL3toPHF2_e4ZXw3ufOXlF2vU/viewform) If you need help getting connected, ping email@example.com and someone will be in touch.
A tutorial can be found at https://project-hydra.slack.com/getting-started. Slack has clients for Mac, PC, Linux, and mobile devices, and may be used via any web browser.
There is a weekly Hydra technical call for developers and other folks who are contributing code or are actively using the core Hydra plugins & components. Contributors should consult the Getting Connected page in the Developers section of this wiki for more information.
- Wednesdays at 9:00 AM Pacific Time;
- Check out this helpful time zone translation
Conference Line Information
Dial: +1 (641) 715 3660
Access Code: 651025#
Best methods of access are standard phone line or Google Talk. Skype has proven unreliable and is not recommended. Once you've dialed the main number, you'll be prompted for the access code.
Monthly Partner Call
There is a monthly Hydra Partners call among (signed) partners. This call complements the technical calls (above), but instead of a focus on code, the Partners call focuses on community & functional progress.
- 2nd Friday of the month;
- 8:30 AM - 9:30 AM Pacific Time;
- Check out this helpful time zone translation
This call used to use the conference line above but has recently been exploring other systems. For a given call, check the agenda on the right of the Hydra Partner Calls page for the dial-in (etc) information.
Hydra Connect, Partner & Steering Group Meetings
Once each academic year, there is a global Hydra Connect meeting; this is a chance for all Hydra Partners and users to meet at one time in one place to promote connections and collaboration throughout the rest of the year. The Hydra Partners also gather for a multi-day (usually three), face-to-face meeting a couple of times a year. These events provide regular forums for partners to focus on aligning road maps, coordinating resources, and extending the technical, community, documentation and training framework. See the Hydra Partner Meetings page for more details. The Hydra Steering Group, a smaller group of institutions that stewards the overall effort and provides central administration, also meets separately during these sessions.
Web Site, Wikis, Issue Tracking & Code Repos
- Hydra's Web Page http://projecthydra.org
- Hydra Wiki (this site) http://wiki.duraspace.org/display/hydra
- Code Repository https://github.com/projecthydra
If you have a question that is not addressed on these pages, send email to the Hydra-tech email list. Or if you have an inquiry that's not appropriate for any of the above channels, then try one of the Hydra Partners. If you don't know whom to contact and you really need to get in touch with someone, try Richard Green in the first instance.