Hyku Community Role Descriptions

Owned by Heather Greer Klein
Dec 10, 2024
3 min read

Hyku Community Developer/Programmer

Role Description

Reporting administratively to the Sustaining the Hyku Repository Platform IMLS Grant Project Director and accountable to the community of Hyku users, the Hyku Community Developer/Programmer role adds development capacity to Hyku projects. Working in the core Hyku release, the developer will work on projects that support community-defined needs. Collaborating with the Hyku Tech Lead and Product Owner, the Community Developer will serve on a community maintenance group, providing programming support (in Ruby, JavaScript, etc.) for feature development, bug fixes, accessibility improvements, maintenance, testing, and code documentation. The goal is to add to the Hyku developer pool and strengthen the Hyku communityā€™s ability to contribute on a technical level.

Time Commitment

10 hours per week, flexible. Funding for this position is secured through XX/XX. Through the grant, the project is working to develop sustainable funding models for possible extension beyond the grant-funded phase.

Qualifications

Minimum: Junior-level programming background

  • Prior training or experience in web and/or application development

  • Excellent communication skills, without hesitation in raising concerns and sharing issues in Slack, meetings, etc.

  • Organizational skills, including a proactive attitude regarding asking questions, seeking clarification, following up on open issues, and getting clarity on priorities and action items

  • Demonstrated working knowledge of Ruby on Rails, JavaScript, Docker, GitHub

  • Familiarity with a Javascript framework, preferably ReactJS (or another JS framework like Angular, Vue, or Polymer), PostgreSQL, code validation, such as RuboCop

  • Ability to contextualize new information and to pick up new concepts quickly

  • Intellectual curiosity and desire to constantly expand technical knowledge

  • Experience creating code documentationĀ 

Desired Skills (not required):

  • Prior experience working with open-source software communities

  • Experience with Hyku and/or other Samvera stacks, e.g., Hyrax

  • Experience writing function tests and general familiarity with test-driven development

  • Experience in an agile development environment

Expectations - Role and Responsibilities

  • Complete a series of training workshops specifically designed for working in the Samvera Community

  • Participate in community maintenance sprints (2 weeks on, followed by 2 weeks off)Ā 

    • Work on tickets related to feature development, bug fixes, accessibility improvements, maintenance, testing, and documentation.

  • Use established test implementations to test and review code changes.

  • Completing tickets and milestones as prioritized by the Product Owner, in consultation with the Tech Lead and Roadmaps Alignment Group

  • Participate in quarterly Samvera Community Sprints

  • Participate in weekly Samvera Tech Calls and monthly Hyku Interest Group meetings

  • Participate in the Samvera Community on Slack (particularly #dev, #Hyku, #community-sprints)

Ā 

Hyku Product Owner

Role Description

The Hyku Product owner works with the Hyku Technical Lead to plan Hykuā€™s development strategy and represents Hyku on the Roadmaps Alignment Group. The Product Owner focuses on building efficiencies in the Hyku Roadmap by coordinating priorities of individual Hyku projects, building documentation, refining the backlog, prioritizing stories, creating milestones for Hyku maintenance, facilitating the Hyku Interest Group, and reducing duplication of effort across the various Hyku projects. In conjunction with the Samvera Community Manager and the Hyku User Community, the Hyku Product Owner facilitates responses to requests for information, demos, and outreach at conferences.Ā 

Ā 

Time Commitment

10 hours per week, flexible. Ideally, the term for Hyku Product Owner is two years.

Resources

  • Hyku Github repository

    • Issue reports with projects, milestones, and labels applied for organization and prioritization

    • Wiki with documentation contributed over time

  • Hyku product site - Information about Hyku for interested developers/managers

  • Hyku Documentation

  • Test implementations maintained by Samvera community. Tech Lead has permission to make changes to the servers. Hosted on AWS.Ā 

    • Valkyrized Hyku on Postgres/Fedora 6, auto-deployed from Hyku ā€œmainā€ branch)

    • Last ā€œstableā€ release. Needs to be manually deployed.Ā 

  • Hyku Interest Group

    • also Hyku Interest Group Google Shared Drive via Samvera (ask Community Manager for access)

  • Hyku Roadmap

Meetings

  • Hyku Interest Group (facilitator) - monthly

  • Samvera Roadmaps Alignment Group - biweekly

  • Samvera Tech Call (optional, Hyku Tech Lead attends) - weekly

  • Regular meetings with the Community Manager and Hyku Tech Lead - weekly

  • Community maintenance group standups ā€“ daily during sprints

  • May be asked to facilitate Community Sprints or themed sprints, which overlap with one week of the maintenance sprints, usually in January, May and October.

  • The Product Owner and Tech Lead typically present an update on Hyku at Samvera Connect and Virtual Connect. The Product Owner also presents an update on the Hyku Interest Group and maintenance working group at these meetings.

  • Other groups as assigned. The Product Owner may be asked to join other working or interest groups and partner meetings if needed.Ā