- Th & F: gather at 8:30 AM in Lathrop LIbrary 282 (with developers)
- Thursday, 9 AM - 5 PM: Lathrop 298 and 294 (spillover)
- Friday, 9 AM - 5 PM: Lathrop 296 and 294 (spillover)
Each year, the Hydra Steering Group convenes a meeting that has become known as “Power Steering”. This event serves as a forum for strategic planning and action, and an opportunity to take a longer term view of the direction of the project. For 2015, the focus of Power Steering will not be on brainstorming, a survey of the landscape, or a broad-based review of the state of the project (each accomplished in 2014); at this point, the overall strategies for the project are well established, and the greater need is to make intentional, deliberate and concrete progress in key areas.
Accordingly, this year’s Power Steering will focus on generating concerted action and progress for the project around the theme of “Cohesion”.
Cohesion can be defined as forming a united whole; the state of being logically or aesthetically consistent. As the Hydra community has expanded dramatically, keeping new partners, adopters and individuals informed and aligned with the project’s guiding principles and progress represents an increasing challenge. Likewise, as rich and advanced as the Hydra technology framework is, we have yet to achieve our full potential for producing a fully fledged product, or for facilitating code sharing and reuse across the Partners.
Power Steering 2015 will therefore tackle the theme of Cohesion along two parallel tracks:
Community Cohesion: How can we become more intentional and effective in structuring community growth and distributed activity leading to collective benefit? How can we best foster partner and community acculturation (onboarding), alignment, and contributions?
Product Cohesion: How can we become more intentional and effective in 1) producing feature-complete solutions; 2) developing an easy-to-adopt solution; 3) developing an easy-to-maintain solution; 4) facilitating the sharing of code and innovations across the project?
Hydra’s community growth is only going to continue. This track needs to explore community needs and opportunities to deliberately structure marketing & community expansion opportunities, to leverage IGs and WGs, to do better at onboarding, and to leverage training as a strategy for cohesion. This group might:
Characterize the growth of the potential and real community (regional, size, maturity, vertical new functions (like devOps/ sysAdmins).
Characterize the related needs to support this growth.
Identify and recommend concrete strategies and actions for Hydra IGs and WGs to undertake in the next year to support community cohesion.
Catalyze / firm up the interest groups & working groups; modeling exemplary IG/WG activity (including specific charters); enrolling active participants; making progress towards specific deliverables.
As successful as Hydra has been in producing a robust technical platform, it can be argued that the project can make advances in producing feature-complete solutions, consolidated content models, and facilitating code sharing and reuse. One can envision that a common, polished, easy to install, easy to maintain solution could be the keystone to Hydra’s technical efforts. It would drive code convergence, reuse of solutions, gemification, common modeling, facilitate data exchange, drive community expansion, simplify & focus documentation and training efforts. It would also provide an obvious and compelling focal point for how the distributed Hydra community can work together.
This group will define the parameters of an envisioned Hydra turnkey solution, in terms of models, features, code components, use of Fedora 4, non-functional requirements, communication and contribution strategies. This track will focus on both the product and technical elements of Hydra solutions. The group can also explore how a community-assembled effort might coalesce around producing this turnkey solution.
Participation in the meeting will be capped at 24-30 community leaders, drawing on Partners from across the HydraSphere (12-15 per track). This is to keep the meeting at a manageable size, to provide sufficient input, to enroll potential IG/WG group leaders and participants, and to keep with with the Hydra Community framework (which defines Partner responsibilities as “determining Project strategy” and “collaborative roadmapping” for both technical and community matters).
If you would like to participate or see a particular leader in the community participate in Power Steering this year, please nominate yourselves or colleagues on the 2015 Hydra Power Steering Participants nominations page by Thursday, February 26. The Hydra Steering Group will issue invitations to participants from among the Partners based on individual expertise, establishing diverse representation, engagement in Hydra IG & WGs, and willingness to take follow on action.
Structure for Power Steering 2015 (a two day meeting, March 26-27) is proposed to be…
brief plenary discussion on the the state of the project and the theme of Cohesion
two parallel tracks discussing each theme (Community Cohesion and Tech Cohesion)
plenary session, featuring report outs from each group
break out to WGs and individual action items
Also, keep in mind that the Hydra Developers congress will be happening in parallel to Power Steering, following in the wake of LDCX 2015. This will give us three parallel tracks of Hydra developer activity, with an approximate 50-60 HydraNauts in attendance in aggegate.
Output of Power Steering 2015 is envisioned to comprise 1.) strategy documents for technical and community cohesion, and 2.) identification of specific action items, including those delegated to individuals and named Working Groups.