In December, it was realized that the original strategic plan had worked and were satisfied with those items being done, so a new 7-high level strategic plan was created. This is located at: https://wiki.duraspace.org/display/hydra/Progress+against+the+2013+Strategic+Action+Plan
Strategy 1: A solution bundle moved towards with the creation of Sufia (based on Scholarsphere). As a DSpace equivalent: About 75% of its functionality exists in various heads already currently. Although no one is working on a DSpace replacement, a lot of work has been done by institutes replacing a DSpace with Hydra components. May need more of a dialogue with a broader swatch of the DSpace community for a replacement to be successful? Perhaps.
Might be worth keeping in mind EPrints (http://www.eprints.org/us/) and how it compares Hydra and DSpace as well. Very similar and lots of institutes have implemented this.
Strategy 2. Turnkey applications. Some institutions are interested in what the larger institutions will do for the smaller ones to allow them to do repositories easier (ie. without much developer resources). WGBH is one head designed to be a turnkey application for other institutes to use.
Strategy 3. Grow the Vendor ecosystem. DCE very symbiotic but otherwise no reported progress on additional vendors?
Strategy 4: Three Railsbridge modules out there already for people to use. All have been tested in some form by groups (two by a larger event and one in a smaller local "Railscamp" thing DCE did). Seems like we are on track on this item.
Strategy 5: Andrew Myers will solve this for us! He has made some progress during the last weekend. Plans on asking those and start delegating work during the next planning topic up in a few minutes. Some progress and mostly organic.
Strategy 6: Chris Beer is working on the Hydra / Fedora 4.x stuff as part of his contribution to the Fedora project. Not much else new yet.
Strategy 7. All CLA's are in. Could use input from those that are new at the table about Hydra's benefits.
Bonus Round (or Another Issue Brought Up):
The roadmap is essentially the gem list. The hydra core is mostly done and should instead just be made faster or better to integrate different gems. Need perhaps a better vision for the core or some type of roadmap for it as most of the planning currently only involves the gems?
Blacklight is somewhat separate from Hydra. As are other components. Should we be more involved in those as they can hold back the development of Hydra features? A number of people from this community could go to the Blacklight community to make a request?
No identified technical lead of the community? If I am a developer with some cycles, not quite sure what I could do to contribute to the Hydra framework itself. Don't want to work on something that others would have no need for. Basically: the focus on only the pain points could be missing some of the cycles people could be contributing to the framework due to less of a clarification on where to put effort.