2017-04-11 Meeting Agenda and Notes
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:
- Andrew Myers (WGBH)
- Eliot Jordan (Princeton)
- Jenn Colt (Cornell)
- Carolyn Cole (Penn State)
- Chris Colvard (Deactivated) (Indiana University)
Agenda:
Notetaker†
Review action items†
- Write a ticket to propose guidelines for how to handle plugin configuration (Andrew Myers)
- Carry forward
- Carry forward
- Start filling out justifications for guidelines in PRs to be done by LDCX (Jenn Colt)
- Mostly done. Carry forward any outstanding tickets
- Turn Chris' observations on GA and config into actionable tickets (Chris Colvard (Deactivated))
- Put the google analytics plugin to the test as a topic for LDCX developers congress. (Andrew Myers)
- Done, kinda. Did not get a dedicated group.
- 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.
- Not done. Do not carry forward.
- Andrew Myers, Eliot Jordan, Matthew Barnett, Noah Botimer, Jenn Colt, cam156, Chris Colvard (Deactivated)
- When uploading, we need to map the uploaded file (or set of files) to a set of derivative generation processes.
- 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.
- 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.
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)
???
- Write a ticket to propose guidelines for how to handle plugin configuration (Andrew Myers)
- LDCX / HDC Update on what we did (Andrew Myers)
- Several new tickets filed
- Development update:
- Update
- Working Group Wrap Up
- Sunset is on Friday
- Expect Github repo to be archived? Or keep it around?
- What action should be taken re: the Guidelines?
- Publish somewhere (other than Github, if the repo is going away)
- Publish on the new Documentation website?
- an we expect Guidelines to evolve into more general "Hydra Programming Guidelines"
- Any appetite to continue work?
- Any appetite to expand the scope of Guidelines to be more about general "Hydra Programming Guidelines"?
- Next Meeting†
- When: 2017-21-14; 12pm ET
† - Standing agenda item
Action Items:
- Write a ticket to propose guidelines for how to handle plugin configuration (Andrew Myers)
- Close open github tickets that should be closed. (Everyone)
- Find notes from Dev Congress plugins sessions (Andrew Myers)
- Done: See discussion on this PR... https://github.com/projecthydra-labs/hydra_plugins_wg/pull/67
- Done: See discussion on this PR... https://github.com/projecthydra-labs/hydra_plugins_wg/pull/67
- Fix guideline formatting. https://github.com/projecthydra-labs/hydra_plugins_wg/pull/75 (Eliot Jordan)
- Address new tickets on hydra_plugins_wg #65 - #72. (Everyone)
- Report back to Hydra Community. 1 page summary and next steps. Summary on tech call and hydra-community mailing list.
- Make list of upcoming projects that might make use of plugins guidelines.
- Link to github guidelines on Duraspace developers wiki.
- Add ticket to hydra_plugins_wg to publish to new documentation website.
- Report back to community at Hydra Connect 2017.