diff --git a/COMMUNITY_TEAM.md b/COMMUNITY_TEAM.md index c3f5c1a61..05c327f62 100644 --- a/COMMUNITY_TEAM.md +++ b/COMMUNITY_TEAM.md @@ -1,33 +1,37 @@ # 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. +The Universal Viewer [Governance Document](https://github.com/UniversalViewer/universalviewer/blob/dev/GOVERNANCE.md) explains how the project's open source community operates. -## Primary Role Descriptions - -### Supporting Success of the Project & Its Contributors +The [Contribution Guide](https://github.com/UniversalViewer/universalviewer/blob/dev/CONTRIBUTING.md) explains some of the more technical aspects of participating in the project. -- Responding to newcomer questions in [Slack](http://universalviewer.io/#contact) 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. +All community members are expected to adhere to the project's [Code of Conduct](https://github.com/UniversalViewer/universalviewer/blob/dev/CODE_OF_CONDUCT.md). -### Building a Healthy and Inclusive Community +This page expands upon some specific roles that members of the community may wish to take on. -- Leading by example, through adherence to [Mozilla's Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/) ("CPG"). -- [Looking for and reporting any violations of the Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/). -- Ensuring opportunities for all levels of contribution, confidence, and background. +## Primary Role Descriptions ### 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. +These individuals are willing and able to help with some or all of the following tasks: + +- Responding to newcomer questions in [Slack](http://universalviewer.io/#contact) and on GitHub. +- Helping select tasks for newcomers or other community members who are unsure of where to start. +- Reviewing pull requests. +- Where possible, helping bring a PR to a final acceptable state, based on engineering review. +- Providing useful feedback in issues. + | | (Ordered alphabetically, by first name) | | --------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| ![Demian](https://avatars.githubusercontent.com/demiankatz?s=460&v=4) | **[Demian](https://github.com/demiankatz)** is Director of Library Technologies and has been at Falvey Memorial Library in some capacity since 2009, living in Philadelphia US. Ask Demian about: | +| ![Demian](https://avatars.githubusercontent.com/demiankatz?s=460&v=4) | **[Demian](https://github.com/demiankatz)** is Director of Library Technologies and has been at Villanova University's Falvey Library in some capacity since 2009, living near Philadelphia in the US. Ask Demian about: | | ![Edward](https://avatars.githubusercontent.com/edsilv?s=460&v=4) | **[Edward](https://github.com/edsilv)** is an applications developer at [mnemoscene](https://mnscene.io), living in Brighton UK. Ask Edward about: | -### Joining the Team +### Translation Team + +The Universal Viewer's interface has been translated into several languages. If you have language skills and would like to assist in adding support for a new language or helping to maintain an existing one, please join the #translations channel in the project's Slack. + +## Joining the Team We welcome active contributors to join the UV team. Specifically, we are looking for contributors with: @@ -37,8 +41,6 @@ We welcome active contributors to join the UV team. Specifically, we are looking 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. +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. Alumni will be acknowledged here as thanks for their past service and are still welcome to participate in the community, but they are no longer expected to respond quickly to inquiries or meet other specific standards of community service. Alumni can have their names entirely removed from the list by request.