Skip to content
This repository has been archived by the owner on Jul 6, 2020. It is now read-only.

Commit

Permalink
Merge pull request #30 from solid/Mitzi-Laszlo-patch-14
Browse files Browse the repository at this point in the history
Update community-roles.md
  • Loading branch information
Mitzi László committed Jan 21, 2019
2 parents cba54ef + 89d6a3d commit 81bfc17
Showing 1 changed file with 17 additions and 26 deletions.
43 changes: 17 additions & 26 deletions community-roles.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,52 +3,43 @@ This document aims to identify the various roles within the Solid community,
and the responsibilities associated with each role, where applicable.

- [Community Leader](#community-leader)
- [Repository Manager](#repository-manager)
- [Community Manager](#community-manager)
- [Repositories Manager](#repository-manager)
- [Solid Core Contributor](#solid-core-contributor)
- [Project Core Contributor](#project-core-contributor)
- [Project Contributor](#project-contributor)
- [Project Release Manager](#project-release-manager)
- [User Testing Panel Coordinator](#user-testing-panel-coordinator)
- [Solid User Testing Panelist](Solid-user-testing-panelist)
- [Solid Event Organiser](Solid-Event-Organiser)

## Community Leader
The Community Leader defines the governing vision of the Solid project, and
channels that vision into the projects and initiatives created to realize it.
They are responsible for selecting core contributors, approving official
projects and initiatives, prioritizing official project roadmaps, and have the
final say on project disputes.

## Repository Manager
The Repository Manager controls Github, NPM, and other Solid organization
properties related to the storage, management, and distribution of official
Solid projects. They are responsible for keeping these properties clean and
well-organized on the community's behalf.
The Community Leader defines the governing vision of the Solid project, and channels that vision into the projects and initiatives created to realise it. They are responsible for selecting core contributors, approving official projects and initiatives, prioritising official project roadmaps, and have the final say on project disagreements. The Community Leader has admin rights of Solid tools and can optionally attend the weekly recurring community support meeting.

## Community Manager
Community Managers are responsible for community outreach, ensuring that
community members are able to realize the full value of solid, and have what
they need to contribute value back if they choose to do so.
The Community Leader defines the governing vision of the Solid project, and channels that vision into the projects and initiatives created to realise it. They are responsible for selecting core contributors, approving official projects and initiatives, prioritising official project roadmaps, and have the final say on project disagreements. The Community Leader has admin rights of Solid tools and can optionally attend the weekly recurring community support meeting.

## Repositories Manager
The Repositories Manager controls Github, NPM, and other Solid organisation properties related to the storage, management, and distribution of official Solid projects. They are responsible for keeping these properties clean and well-organised on behalf of the Solid community. The Repositories Manager has admin rights of Solid tools must attend the weekly recurring community support meeting.

## Solid Core Contributor
Solid Core Contributors work across projects on initiatives that enrich the
Solid ecosystem as a whole. They must attend regular stand-ups and strategy
meetings.
Solid Core Contributors work across projects on initiatives that enrich the Solid ecosystem as a whole. Solid Core Contributors must attend the weekly recurring community support meeting.

## Project Core Contributor
A Project Core Contributor is a key team member on an official Solid project.
They may have issues assigned to them, review and merge pull requests, and must
attend regular stand-ups and project strategy meetings.

## Project Release Manager
The Project Release Manager is responsible for determining which features and/or
bug-fixes will make a given project release. They must attend regular stand-ups
and project strategy meetings.
The Project Release Managers are responsible for determining which features and/or bug-fixes will be merged into the release of their respective projects. Project release managers must attend the weekly recurring community support meeting.

## Panel Coordinator
Panel Coordinators are responsible for designing and running tests with the Solid Panelists as well as publishing test results to the Solid community. Panel Coordinators are expected to join the weekly User Testing meeting which is moderated by the Community Manager.
## User Testing Panel Coordinator
Panel Coordinators are responsible for designing and running tests with the Solid Panelists as well as publishing test results to the Solid community. Panel Coordinators are expected to join the weekly user testing meeting which is moderated by the Community Manager.

## Solid Panelist
## Solid User Testing Panelist
Solid Panelists are individuals who are available for a range of tests over time to improve the Solid user experience. When there is a test set up by the Panel Coordinators, the Community Manager will reach out to the relevant Solid Panelists to ask if they would like to participate in that particular test. Each test will take approximately 30 minutes, Solid Panelists are not obliged to participate in all tests, and Solid Panelists can stop being on the Solid Panel at any point. Tests will be designed to improve the Solid experience.

## Solid Event Organiser
The [Solid Event](solid-events.md) Organiser is responsible for organising and coordinatiing a Solid Event in a stated city. The position of Solid Event Organiser will be filled by an individual for as long as an event is scheduled in the future.

## Individuals currently occupying roles

Expand All @@ -57,5 +48,5 @@ Solid Panelists are individuals who are available for a range of tests over time
* **Repository Manager** - [Kjetil Kjernsmo](https://github.com/kjetilk)
* **Project Release Manager** - [Kjetil Kjernsmo](https://github.com/kjetilk)
* **Solid Core Contributors** - [Ruben Verborgh](https://github.com/RubenVerborgh), [Arne Hassel](https://github.com/megoth_twitter), [Justin Bingham](https://github.com/justinwb), [Kjetil Kjernsmo](https://github.com/kjetilk)
* **Panel Coordinator** - [Maya Rinehart](https://github.com/mayarhinehart), [Felix Poon](https://github.com/fcfpoon), [Tony Morelli](https://github.com/tony-morelli)
* **User Testing Panel Coordinator** - [Maya Rinehart](https://github.com/mayarhinehart), [Felix Poon](https://github.com/fcfpoon), [Tony Morelli](https://github.com/tony-morelli)
* **Solid Panelist** - Eric Prud’hommeaux, Eduardo Ibacache Rodriguez, Teodora Petkova, David Booth, Pat McBennett

0 comments on commit 81bfc17

Please sign in to comment.