Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

\uD83D\uDDD3 Date

@11am Eastern

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Updates

  • Collaborative work on re-writing WG Scope & Objectives

\uD83D\uDDE3 Discussion topics

Time

Item

Notes

10:00am-10:05am

Welcome

Volunteer note taker?

10:05am - 10:25am

Updates

10:25am - 10:50am

WG Scope & Objectives

https://docs.google.com/document/d/1abE8z8tl0s0SWOewt4zzDGgTB0iqXKp3agtmzVbMXbo/edit?usp=sharing

10:50am - 11:00am

Wrap Up

Notes

Previous Action Items:

  • Sent overview document in December that listed interests of different institutions.

  • Finalized working group in community

  • Created a page to document, eg. performance testing

Updates:

Hyrax:

  • Working on resolving last few failing tests for Valkyrie-only test suite copy (30-something or less)

  • Next week’s maintenance sprint should get a Hyrax 5 release out

  • Status of Sirenia will be fully supported; currently experimental but seems to work well

  • Performance testing - after we get the connector solid, we’ll move forward with performance testing and identifying final adjustments

  • Would be good to get Nurax updated

Fedora 6.5:

  • Out by the end of February

Valkyrie:

  • Samvera Board has funded SoftServ work for migrating a Hyku instance into Valkyrie/Postgres

    • This was begun over the holiday’s but Kevin didn’t gather an update before this call

  • PALNI/PALCI have finalized plans to migrate to Postgres via Valkyrie, which SoftServ has started

Maintenance WG

  • We need to leverage the Maintenance WG for resolving

  • Daniel Pierce can’t be the only person contributing to this work

    • We need to do a call to source more dev hours for this work in the Maintenance WG

    • Do this after the dev congress so we can be specific about what work needs to be done

    • Volunteers:

WG Scope and Objectives

  • Originally slated for 3 months

    • This was focused on scoping work, but we should move beyond and expand the scope of the group

  • Who sources the dev work for resolving Fedora 6 connection issues that come out of the dev congress?

  • Juliet Hardesty will still consider chairing this group, cannot yet commit

  • Future work for this group, as a Part Two (out of scope for this WG):

    • A migration to Fedora 6

✅ Action items

  • More hands on Hyrax 5.0 testing and investigate Sirenia failures (next week’s dev congress)
  • AFTER DEV CONGRESS: Call for dev hours contributed to Maintenance WG to help resolve Fedora 6 issues that come from the dev congress

⤴ Decisions

  • No labels