2017-10-17 Meeting

Date

17 Oct 2017 11:00 AM EST at https://cornell.zoom.us/j/703126880

Facilitator: LaRita Robinson

Notetaker: Andrew Myers

Attendees

• Lynette Rayle
• LaRita Robinson
• Andrew Myers
• Chris Diaz

Agenda / Notes:

1. Roll call (please log in above)
2. Review project board: https://github.com/projecthydra/projecthydra.github.io/projects/1
   No progress on tickets to report. It's been acknowledged that the working group has been extremely short on cycles for the past few months.
   
   1. Reporting on items completed since last meeting
   2. Review status of in-process tickets
   3. Discuss ready items & groom backlog
      1. Any new items needed?
      2. What should be moved to ready?
3. Other agenda:
   
   1. LaRita Robinson Discuss linking to testing documentation
      
      1. The release testing subgroup has prepared some documentation that should potentially be linked to... see: Re: Hyrax Release Testing Subgroup
      2. This is included in Chris's branch, and will come through with any submitted PR.
   2. Chris Diaz Manager's guide long-term solution
      1. At the same level as "Manager's Guide" there is a section called "User Interface Testing", which is like acceptance testing.. i.e. manual steps for users to go through, and evaluate correctness of the application by observing the UI.
         
      2. Jennifer Lindner had mentioned (before the meeting) that samvera.github.io was primarily targeted toward devloper documentation, and docs for managers may not be the best fit here, and may lead to maintainability problems if managers and non-developers are expected to submit changes, since the workflow currently requires some github knowledge.
         
      3. However, those of us in attendance agreed that avoiding "yet another site with documentation" was worthy enough to keep the new content at samvera.github.io.
      4. We talked with Jenn on Slack after the meeting and there seems to be general consensus.
      5. Also, we pointed out to Chris Diaz that he can add metadata to make is content more discoverable through the A-Z index, as well as the quick find box.
   3. Samvera Connect working group report
      1. Assinged to bess, but we ALL need to help with the content. It's only a 3 minute update, so shouldn't be too much work (see action item).
         
   4. (add your items here)
4. Pick facilitator / notetaker for next time
   
   1. Notetaker is responsible to copy template agenda into a new agenda for next meeting and add any followup items immediately.
   2. We didn't do this. Game time decision, i guess?

Action items 

• Chris Diaz will submit a PR for his new content.
• EVERYBODY work on the Working Group Update from Samvera Virtual Connect (summer, 2017) to include things that have happened since then so that we can present them at Samvera Connect 2017 in November at Northwestern. See: https://github.com/samvera/samvera.github.io/issues/136