Project Director Meeting 1-3-14

Owned by Bill Branan
Jun 16, 2017
3 min read

Connection Info: 

Google Hangouts

Attendees

Agenda

  1. Facilitator: Rick Johnson
  2. Set Notetaker (Next up): Claire Stewart
  3. HydraConnect Meeting Planning (keep to 20 min)

    1. Possible Hydra Connect topics:  Straw Schedule for Hydra Connect 2014

      1. what it's like to be a manager for Curate
      2. what it's like to be a developer for Curate
      3. intro to scrum training (for anyone, not just Curate)
      4. Panel idea:  Collaborative projects, how we synchronize development and organize ourselves (could be with Avalon for example)
      5. Curate project update (include demos?)
      6. Lightning talk/demo station
      7. Social gathering?
      8. Workgroup
        • Dev, Tech Lead
        • PO: Product owners would benefit from Face to Face planning (should be on Friday but needs to consider overlap with other topics, like Avalon)
        • PD: Some time for strategic discussion (for example Share, Grants, Sharing infrastructure and code). Needs to be on Wednesday or Thursday due to Conflicts with Claire and Jon's schedules. 
  4. Remaining Governance Items
    1. Onboarding new partners
    2. Other?
  5. Title of project
    1. Curate
    2. Shared IR (can be confusing as just sharing code)
    3. Other?
  6. Review Draft Contribution pattern from DCE
    1. contributions on the behalf of a partner involved in this project would be handled jsut as any other institution joining
    2. contributions for work where they are using curate as a base, would involve a review by POs and then prioritization and implementation in the way other features are evaluated and implemented
    3. need for communication on what they are working on to prevent duplicative effort may be resolved by Mark Bussey's offer to be a PD/PO for DCE; PDs will handle focus and priority setting as a group and will address any obstacles as they arise
  7. Other questions at this point?

Notes

  • Project contributions (from just full partners?)
    • would welcome additional developers but need some framework and on boarding for both tech and no-tech
    • documentation is needed to clarify 
      • lead PO and Tech Lead will handle technical and non technical aspects of managing on boarding
      • expectations of what is required to be a Hydra dev (signed ICLA, skills, etc)
      • code vetting
      • commitment  levels
  • Hydra Connect planning; schedule is still evolving, but general thought is that Tuesday - Wednesday will be large-group oriented with presentations, posters, etc., and team/project work will start to happen during unconference time Thursday afternoon and all day on Friday. POs and PDs will all be attending, but not all developers. POs need some good face time to work on stories and talk about process.
  • Started the discussion about the name of the project: 'Shared IR' is confusing to some as it is not actually shared infrastructure. Discussion about the value of keeping 'IR' in the name somehow, but picking something that distinguishes the product & project. Curate is favored by some for being both distinctive and descriptive (though missing 'IR') but concern about confusion this might create around just the Curate gem.
  • PDs will review and make edits to the draft Non-partner Participation document and then we'll run it by the other leads (PO, Tech).

Action Items (with carryover)

@ Tech Lead backup

Claire Stewart add documentation on how non-participating institution developers may get involved including

  • lead PO and Tech Lead will handle technical and non technical aspects of managing on boarding
  • expectations of what is required to be a Hydra dev (signed ICLA, skills, etc)
  • code vetting
  • commitment  levels

Disseminate governance and process updates to larger group