Hydra Tech Call 2017-03-22

Owned by Bill Branan
Jun 16, 2017
3 min read


Time: 9:00am PDT / Noon EDT

Call-In Info: 1-641-715-3660, access code 651025

Moderator:  Steve Van Tuyl

Notetaker:  pbinkley

Attendees: 

Agenda

  1. Roll call by timezone per following order - ensure notetaker is present
    1. folks outside North and South America
    2. Eastern timezone
    3. Central timezone
    4. Mountain timezone
    5. Pacific timezone
    6. folks who were missed or who dialed in during roll call
  2. Call for additional agenda items (moderator)
  3. Updates on last week's items
    1. None
  4. Discuss Hydra Developer Congress 2017 topics ( Andrew Myers)
    1. March 2017 Developer Congress Meeting Agenda <== See topics and proposed development ideas here.  - we will populate the table at the bottom of the document, noting especially the "Well Defined" column so that Dev Congress time doesn't get devoted to defining tasks; Andrew and others (all welcome) will try to groom the list before Dec Congress so can hit the ground running - intend to meet at lunch on Wednesday or at the end of the LDCX program
    2. Identify overlap, and see if we can arrive at the conference with topics that don't have as much overlap.
    3. The goal here is to just do a little idea-grooming now, with the intent of providing a better starting point at the time of the conference.
    4. Below are topics submitted that may overlap with each other.
    5. Refactoring...
      1. "Refactor Hyrax for better integration points for plugins" ( Andrew Myers) 
        1. One of these is definitely derivative generation, which deals with Jobs and the Actor stack.
      2. "Document best practices around actors, provide an easy-to-find place to inject your own actor," submitted by  Trey Pendragon.
      3. "Identify places to refactor that a group could come back to," submitted by  Trey Pendragon.
      4. "Organize and charter a group to tackle refactoring and other feature-less sprints on core gems," submitted by Trey Pendragon.
      5. "Architecture solution for jobs in Hydra/CC/Sufia to allow "composeable" jobs," submitted by  Adam Wead.
    6. Document best practices...
      1. "Help make Plugin Guidelines readable, usable," submitted by  Andrew Myers
      2. "Document best practices around actors, provide an easy-to-find place to inject your own actor," submitted by  Trey Pendragon
    7. Others?
  5. Should we align Hyrax resource types with a standarized list? ( justin ?)
    1. For Hyrax 2.0? May require a data migration. - (Justin not on the call, no one else could speak to it, so tabled)
  6. Location of documentation and configuration files for apps built off Hyrax - Carrick: intend to build Avalon as consumer of Hyrax, intend to put stuff in Hydra derivatives, lots of other places, which can be turned on in Hyrax - how should the documentation for optional features like this be handled? Will not have a separate Avarax repository. Will put high-level page in main Hyrax docs, linking to more detailed pages in wiki - will be implemented according to new plugin rules for interfaces etc.
    1. Avarax (Avalon on Hyrax) as a specific example
    2. Store in Hyrax Wiki or other location
  7. (STANDING) Update on Sufia/CurationConcerns Consolidation Plan ( justin or Michael Joseph Giarlo) - (neither Mike nor Justin was on the call)
  8. Moderator/notetaker for next time: - No call during LDCX, so next call is April 5
    1. Moderator:  Jeremy Friesen
    2. Notetaker:  Steven Ng