Skip to content

Latest commit

Β 

History

History
44 lines (28 loc) Β· 3.77 KB

COMMUNITY_TEAM.md

File metadata and controls

44 lines (28 loc) Β· 3.77 KB

UV Community Team

UV community team members help shepherd the community. They are here to help mentor newcomers, review pull requests, and facilitate issue discussions.

Primary Role Descriptions

Supporting Success of the Project & Its Contributors

  • Responding to newcomer questions in Slack and on GitHub.
  • Helping select tasks for newcomers or other community members who are unsure of where to start.
  • Reviewing pull requests, with a goal of three (3) reviews per PR.
  • Where possible, helping bring a PR to a final acceptable state, based on engineering review.
  • Providing useful feedback in issues.

Building a Healthy and Inclusive Community

Active Community Team Members

Active Community Members are visibly active in our Slack and/or GitHub channels. We identify active members as being those whom contributors and staff can most count on for a response within 2-3 days.

(Ordered alphabetically, by first name)
Demian Demian is Director of Library Technologies and has been at Falvey Memorial Library in some capacity since 2009, living in Philadelphia US. Ask Demian about:
  • Universal Viewer
  • TypeScript
  • IIIF
Edward Edward is an applications developer at mnemoscene, living in Brighton UK. Ask Edward about:
  • React
  • three.js
  • Universal Viewer
  • TypeScript
  • IIIF

Joining the Team

We welcome active contributors to join the UV team. Specifically, we are looking for contributors with:

  • Passion for IIIF, TypeScript, React
  • Interest in helping other contributors, and fostering community growth
  • Two months of active contribution to the repository.

To apply, simply contact one of our staff or community team members via Slack or email, and we'll get right back to you.

We embrace diversity, and invite people from any and all backgrounds to get involved in the UV project. We don't discriminate based on family status, gender, gender-identity, marital status, sexual orientation, sex, age, ability, race and/or ethnicity, national origin, socioeconomic status, religion, geographic location, or any other dimension of diversity.

Review Periods

Once per year, we'll check in with our team members (both active and on break) to ensure they are feeling supported, and to check if they will remain active on our team for the coming months. If we do not hear back from members at check-in time, they will be transitioned to an alumni role.