2017-04-11 Meeting Agenda and Notes

Owned by Bill Branan
Jun 16, 2017

When: 2017-03-14; 12pm ET

Where: Google Hangouts: https://hangouts.google.com/hangouts/_/event/cd3blc5al8lb5v97fc9a3847id0?hl=en&authuser=1

Moderator: Andrew Myers (WGBH)

Notetaker:

Attendees:

Agenda:

  1. Notetaker†

  2. Review action items†

    1. Write a ticket to propose guidelines for how to handle plugin configuration (Andrew Myers)
      1. Carry forward
    2. Start filling out justifications for guidelines in PRs to be done by LDCX (Jenn Colt)
      1. Mostly done. Carry forward any outstanding tickets
    3. Turn Chris' observations on GA and config into actionable tickets (Chris Colvard (Deactivated))
    4. Put the google analytics plugin to the test as a topic for LDCX developers congress. (Andrew Myers)
      1. Done, kinda. Did not get a dedicated group.
    5. Come up with user stories (or better yet, actionable tickets) for refactoring derivative generation in Hyrax, that can be organized into a sprint during Hydra Dev Congress.
      1. Not done. Do not carry forward.
      2. Andrew Myers, Eliot Jordan, Matthew Barnett, Noah Botimer, Jenn Colt, cam156, Chris Colvard (Deactivated)
      3. When uploading, we need to map the uploaded file (or set of files) to a set of derivative generation processes.
      4. The set of derivative generation processes needs to be able to be configurable (i.e. added to, or removed from) by plugins, and also by the host application.
      5. When downloading derivatives, we need to be able to map a persisted record (in Fedora, Solr, or both) to the location of it's generated derivatives.

    6. Update README in https://github.com/projecthydra-labs/hyrax-google_analytics to define the scope of the gem to include 'custom event tracking downloads and then rendering of that in a dashboard' (Anyone)

      1. ???

  3. LDCX / HDC Update on what we did (Andrew Myers)
    1. Several new tickets filed
  4. Development update:
    1. Update
  5. Working Group Wrap Up
    1. Sunset is on Friday
    2. Expect Github repo to be archived? Or keep it around?
    3. What action should be taken re: the Guidelines?
      1. Publish somewhere (other than Github, if the repo is going away)
      2. Publish on the new Documentation website?
      3. an we expect Guidelines to evolve into more general "Hydra Programming Guidelines"
    4. Any appetite to continue work?
      1. Any appetite to expand the scope of Guidelines to be more about general "Hydra Programming Guidelines"?
  6. Next Meeting†
    1. When: 2017-21-14; 12pm ET

† - Standing agenda item


Action Items:

  1. Write a ticket to propose guidelines for how to handle plugin configuration (Andrew Myers)
  2. Close open github tickets that should be closed. (Everyone)
  3. Find notes from Dev Congress plugins sessions (Andrew Myers)
    1. Done: See discussion on this PR... https://github.com/projecthydra-labs/hydra_plugins_wg/pull/67
  4. Fix guideline formatting. https://github.com/projecthydra-labs/hydra_plugins_wg/pull/75 (Eliot Jordan)
  5. Address new tickets on hydra_plugins_wg #65 - #72. (Everyone)
  6. Report back to Hydra Community. 1 page summary and next steps. Summary on tech call and hydra-community mailing list. 
  7. Make list of upcoming projects that might make use of plugins guidelines.
  8. Link to github guidelines on Duraspace developers wiki.
  9. Add ticket to hydra_plugins_wg to publish to new documentation website.
  10. Report back to community at Hydra Connect 2017.