This document is no longer being maintained (April 2014) and is superseded by documents for the 2014/2015 period.
- in progress - Complete
|Strategy 1: Develop A Full Suite of Solution Bundles||Status||Notes|
|By OR13, Hydra will have catalyzed work beginning on a DSpace-equivalent Hydra head.||As at early April a number of Hydra partners are being approached by DSpace users seeking to know more about Hydra and how it might be a migration path for them. Northwestern, Indiana, Cincinnati, UVA & ND are speccing an IR/DR solution for themeselves that would address this point. More details here: IR Solution Bundle Requirements Breakout|
|By OR14, an alpha of a DSpace-equivalent Hydra head will be available to the community.||'Curate' fits this bill and is well under way. An alpha might be available by OR14.|
|By OR14, Blacklight / Hydra users will have a robust & polished exhibits tool in Atrium (Omeka-equivalent)||See Spotlight! page on wiki.|
|By end of 2014, Blacklight / Hydra users will have a demonstrated, replicable approach to presenting Finding Aids and archival collections (XTF-equivalent)||The Samvera Archivists Interest Group is an active WG dedicated to meeting archival needs on the Hydra stack. Requirements gathering & visioning for a Blacklight-based finding aid solution ("BeadL") took place at LDCX 2014.|
|By end of 2013, there will be viable heads / solution bundles for time-based media (Avalon), images (DIL), and administration (Argo).||Avalon 1.0.0 released May 2013. Avalon 2.0 released October 2013.|
|Strategy 2: Develop Turnkey / Hosted Solutions|
|By end of 2013, Hydra will have fostered the beginnings of development of both hosted and turnkey Hydra solutions|
|By OR14, there will be a Hydra turnkey application available to the community via at least one provider.|
|By OR14, there will be a Hydra hosted solution available to the community via at least one provider.|
|Strategy 3: Grow the Vendor Ecosystem & Define the Vendor Community Structure|
|By end of 2013, Hydra will have X (x=3?) vendors in the ecosystem, performing consulting, training, integration, custom development, SAAS...|
|By end of 2013, Hydra will have a defined structure with vendors that is symbiotic with the overall community.|
|Strategy 4: Training Framework|
|By end of 2013, Hydra will have a training framework that includes a standard, shared Hydra curriculum, a method for offering onsite trainings at new adopters looking to launch quickly, and a way to deliver training multiple times a year at multiple locations (internationally).|
|Strategy 5: Documentation Framework|
By end of 2013, Hydra will have a documentation framework that will define targeted audiences, information needs, initial development / infill of any gaps, and mechanisms (including resourcing strategies) to maintain the project's documentation base.
|Strategy 6: Technical Framework|
|By end of 2013, Hydra will have demonstrated robust code-sharing and reuse across heads and sites, and a technical core that facilitates this.||See Rank, Interest, and Availability for Gemification for Solution Bundles|
|By end of 2013, Hydra will have co-developed and demonstrated / tested the viability of initial code in Fedora 4.x||See http://hydra.fcrepo.org/ Ongoing process. Rubydora and Active Fedora for Fedora 4 under development.|
|By end of 2013, Hydra will have investigated and framed its needs to provide maintenance support and continuity for deployed Hydra software (heads, gems), and identified approaches for meeting these support needs.||The hydra gem is a start on this.|
|By OR14, Hydra will have tested and adopted clear, proven methods for addressing needs for stable, supported software.||Well under way. See: Hydra Gem -- a pegged gemset for a stable distro|
|Strategy 7: Community Framework|
|By LDCX^4, we will have CLA's on file from all contributors|
|By Q1 2014, Hydra will have an updated and more polished articulation of its community principles, values, methods and benefits--the recipe that has defined the "hydra way" to date, and much of the project's success.||Added to agenda for June partners' meeting. Deferred to September with a suggestion that SG put up a "straw man" for discussion prior to that.|
|By OR13, Hydra will have more clearly defined the balance of roles between the Steering and Partners groups, promoting engagement, transparency, effectiveness and efficiency in community governance and administration||New definition of responsibilitiea approved at June 2013 meeting. Wiki and website changed to reflect these.|
|At OR13, Hydra will have a Hydra UG meeting as part of the official conference track.||?||Tried for it at OR13 but somehow it wasn't quite clear.|
|By end of 2013, Hydra will have established a framework for fostering & working with Solution Bundle communities.|
|By end of 2013, Hydra will have established a framework for fostering & structuring its relationship to vendors; this possibly includes registered service providers, endorsed events and products, etc.|
|By end of 2013, Hydra will have defined an approach for coordinating development and support activities of partners across Europe, North America and Australasia||Summer 2013: European Partners having regular calls to discuss participation in coming conferences and seeding others with publicity materials.|
(New 2013-06-27) By the end of 2013 Hydra will have established a mechanism for raising awareness at conferences etc where Hydra is not explicitly represented - eg publicity materials in delegate packs).
|Bookmark (similar to OR12 bookmark) being distributed as "Conference Goodies" material for (European) conferences.|
|Strategy 8: Community Expansion|
By OR14, assemble a kit of Hydra marketing collateral (glossies, tangibles) into a managed library for Partners' ready use.
By OR14, create a marketing and outreach plan to represent Hydra at relevant conferences (e.g., SPARC)
By OR14, create a plan for producing Hydra webinars and screencasts representing the project and various heads.
By OR14, launch a Twitter account for the Hydra project
|@HydraSphere February 2014|
By OR14, clarify the distinctions between Users and Partners, and the benefits and expectations of each.
|By OR14, create a registry of Hydra Users (for tracking and reporting on adoption, and managing project notifications).||http://projecthydra.org/community-2-2/partners-and-more/ and Users/adopters contact list|
|By Apr 30, 2014, establish a semi-annual communication to promote publishing articles about Hydra in journals (e or otherwise), in institution repositories (if appropriate) and raising awareness by populating the Hydra website with the information or a link to the digital version.|