...
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:
Ben Pennell volunteers to help some depending on the nature of the issues found
Emily Porter and Collin Brittle said Emory may be able to help, at least with testing
WG Scope and Objectives - https://docs.google.com/document/d/1abE8z8tl0s0SWOewt4zzDGgTB0iqXKp3agtmzVbMXbo/edit#heading=h.j3278pwce3hl
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
Revising Deliverables and Timelines:
We need to revise the language to change from planning to doing
Suggest instead of changing the scope, to organize the Planning as a completed milestone, and the Doing as a Phase 2 milestone
Anything missing as “Deliverables?”
Finalize Fedora connector
Document migration effort and monitor the need to get others involved
✅ 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
...