Versions Compared

Old Version 14

changes.mady.by.user tamsin woo

Saved on

compared with

New Version 15

changes.mady.by.user Juliet Hardesty

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

https://iu.zoom.us/j/94019873775?pwd=cmlSb2tCNmQzbmlhUXgvNHVIVkxLUT09
enter pass: 175760

Notetaker: Rob Kaufman? Heather Greer Klein

Community Notes

  • Attendees
    • Julie Hardesty (Indiana University)
    • Maria Whitaker (Indiana University)
    • tamsin johnson (UC Santa Barbara)
    • Chris Colvard (Ubiquity Press)
    • Ilkay Holt (British Library- Advancing Hyku)
    • Heather Greer Klein (Samvera)
    • Moira Downey (Duke University)

Agenda:

  •  Welcome!
    • Hyrax IG/WG wiki reorg
  • Hyrax Maintenance Working Group update - Julie Hardesty and Tamsin Johnson
    • Call for new WG members (January-June 2021)
  • Organizing issues / (re)establishing roadmap
  • Topics and projects
    • Developers Congress, Nov. 16-18
    • Complex object use case (Repo Managers IG)
    • REST API in Hyku
    • Helm chart follow-up
    • Hyrax/Hyku implementations to invite for demo?
    • Hyrax a11y
  • Questions?
  • Next meeting - Tuesday, December 8, 4pm Eastern

Notes:

  • Welcome!
    • Hyrax IG/WG wiki reorg
    • Julie is now in the PO role, wants to engage the community more generally via this group than perhaps in the past
    • JH will move forward with these notes rather than on the old SIGHAR group
    • Want to make sure the scope and objectives are still relevant, and check on resources.
    • Under the Maintenance WG page, want to add info about the PO role. 
    • There are things from a past proposal to take on some of the previous PO responsibilities  in this IG, will make sure those are reflected in the charter.
  • Hyrax Maintenance Working Group update - Julie Hardesty and Tamsin Johnson
    • Call for new WG members (January-June 2021)
    • Currently --work towards 3.0 release. A few open merge requests, issue in 2.9 and 3.0 related to IIIF that is being treated as a blocker as not sure what deployments are affected. TJ has been trying to get a deployment to replace nurax, which is deployed and maintained by DCE, which is hard for the Community to maintain. A community-owned option will help address in a controlled way.
    • On sprint in theory; Crystal from Notch8 on QA but there is minimal other participation beyond TJ.
    • Is the working group working? Do we want to recommit to a strong call for the new year?
      • What is the value in continuing the standups; what is leading to the drop off in participation
      • Could be worth it to try a call and see what the reaction is. JH working on the draft of a call right now. Can’t say what our goals are for the next 6 months, but the WG might be devoted not just to development but to organizing to move the development work and get 3.0 out. Aiming for before Thanksgiving. 
      • Will be another 6 month call. Have been asking for 3 devs and one QA lead with PO and TL. Ideal to have a functional Agile team. 3 devs and QA lead half time, with 2 weeks on and two weeks off sprint model. 
  • Organizing issues / (re)establishing roadmap
    • JH and TJ are digging in on organizing, could ask this group for help. 
    • Roadmap hasn’t been updated for a while. In 2018 the roadmap was carried over from 2017. Focus on maintenance work; strategy to move community work back to the core. Pattern of things on the roadmap being implemented but not resurfaced to the community code. 
    • Plug-ins aren’t in Hyrax out of the box. That pattern is of concern. Ends up directing effort out of the core, and extension makes it harder to learn maintenance of the underlying code. Also worried about the maintainability of those plug-ins. That is an ongoing discussion for developers in the community with the Tech Lead.
  • Topics and projects
    • Developers Congress, Nov. 16-18
      • JH is trying to install using the instructions we provide, finding some confusing instructions. There are multiple ways to install. In GitHub there are other variations on the instructions. Proposing sorting those routes out and providing them clearly. Hoping it helps.
      • List of topics have been proposed, all encouraged to participate!
    • Complex object use case (Repo Managers IG)
      • Discussing how to show and provide access to born digital content. Is anyone implementing that, is that a potential interest or working group? A Hyrax use case.
    • REST API in Hyku
      • Any memory of this being discussed in the interest group? Currently Hyku specific, assumes multi-tenancy. Value now is to have an implementation to discuss the need and use cases and if we have forward direction on it. It is an implementation as an example right now (react frontend on Hyku). Can be demo-ed in the future.
    • Helm chart follow-up
      • There is a Helm chart, there are Hyrax containers, no publishing strategy. People who are doing cloud-native Hyrax, would love to see those folks engaging. Missed opportunities in employing to Kubernetes in fragmented repositories.
    • Hyrax/Hyku implementations to invite for demo?
      • Analytics work? 
      • Can look through what was shown at Connect presentations
      • Julie would like to get caught up on Hyku, will attend interest group
      • If things occur to you, please share them so they can be lined up for this meeting
    • Hyrax a11y
  • Questions?
  • Next meeting - Tuesday, December 8, 4pm Eastern

...

    • This is a late meeting for UK/EU. 
    • Many PT meetings happen at 9-10am PT. Would be better to set meeting earlier. 8am better than 9am. JH will contemplate this for January, and get feedback at Dec meeting.

Closed meeting at 4:55PM ET