Hydramata Project Director Call May 9th

Homework ahead of time:

Review Process Proposals from May 8th meeting
- Ratify Role Changes, new roles
- Organization structure
- Resourcing (e.g. quantity, continuity, contiguous time)
- Identify critical and/or immediately actionable items in the proposal

Cincinnati PO and PD changes
Quick Review of Process Proposals from May 8^th meeting
- Ratify Role Changes, new roles
- Organization structure
- Resourcing (e.g. quantity, continuity, contiguous time)
Discussion Deliverables
- Approve any changes that are immediately critical or actionable
- Approve phasing and implementation plan for any process changes (I will suggest as a deliverable of Thursday)

Thinking for benefits of users for Hydramata (in response to call for clearer product vision) i.e. if you use Hydramata you get for example
- Integration with APTrust
- SHARE
- ORCID
- Spotlight
- Avalon
- Research Data Support
- Unified Heterogeneous Discovery Environment
- …
How does Hydramata fit into the Hydra Strategic Roadmap
- e.g. featured products, frameworks, configurability, solutions across hydra partners, adopters (sophisticated and non-sophisticated)
How can Hydramata impact dynamics of code development and sharing across all Hydra partners? Should we agree on a vision?
- Rick: I have been operating on a wait and encourage adoption once we have something in place perspective)
- However, there is was a call for a clear vision here from the team