Versions Compared

Key

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

...

4-5 Developers: Includes Hyrax Technical Lead, who is responsible for delivering releases in a timely fashion; Developer with UX skills when needed. All will be responsible for communication with Components Maintenance WG as needed.

1-2 Quality Assurance (QA) SpecialistSpecialists/Coordinator: Brought Coordinators: Testing issue backlog and brought in during release time to test or coordinate testing and documentdocumentation.

All code contributors must have an Individual Contributor License Agreement (iCLA) on file with the Samvera Steering Group. If the contributor works for an institution, the institution must have a Corporate Contributor License Agreement (cCLA) on file. See Samvera Community Intellectual Property Licensing and Ownership for more information.

...

  • The call for participation will be sent to samvera-partners@googlegroups.comsamvera-community@googlegroups.com, and samvera-tech@googlegroups.com, as well as through appropriate slack channels.
  • Regular meetings (for sprint planning, stand-ups, etc.) will be held remotely, and will be scheduled at a time and frequency that works best for WG members.
  • WG notes and activity, including working drafts of Release Notes, will be documented on the Hyrax Maintenance Working Group wiki page.

Team:

July 2021 - December 2021:

NameInstitutionRoleFTENotes
Julie HardestyIndiana UniversityProduct Owner0.2as part of overall 0.2 FTE as product owner
tamsin johnson
Note: only through September 2021
UC Santa BarbaraTechnical Lead0.2

as part of overall 0.5 FTE as tech lead 

Jessica HiltUC San DiegoProjects Lead0.2


Github issues tester (QA)0.5
Rebekah KatiUNC Chapel HillGithub issues tester (QA)0.25


Github issues tester (QA)0.25


Developer0.5


Developer0.5

January 2021 - June 2021:

...