Skip to content
This repository was archived by the owner on Jul 6, 2020. It is now read-only.
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 30 additions & 33 deletions community-roles.md
Original file line number Diff line number Diff line change
@@ -1,49 +1,46 @@
# Solid Community Roles and Responsibilities
This document aims to identify the various roles within the Solid community,
and the responsibilities associated with each role, where applicable.
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)
- [Repository Manager](#repository-manager)
- [Project Release Manager](#project-release-manager)
- [Solid Core Contributor](#solid-core-contributor)
- [Project Core Contributor](#project-core-contributor)
- [Project Contributor](#project-contributor)
- [Project Release Manager](#project-release-manager)

## 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 Manager is responsible for community outreach to facilitate contributions and implementation of the governance of Solid. The Community Manager is responsible for merging pull requsets concerning the community repository and processing and implementing suggestions around Solid governance. The Community Manager has admin rights of Solid tools and must moderate 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 Contributor
A Project Contributor is anyone who contributes to an official Solid project.
Contributions come in many forms, from coding and qa to experience design and
technical content writing.
A Project Core Contributor is a key team member on an official Solid project. Project Core Contributors must attend the weekly recurring community support meeting.

## 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.

## Solid 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
The Solid panel engages in continuous tests to improve the user experience. When a test is set up by the Solid panel coordinators the community manager will reach out to the Solid panel to ask if they would like to participate in this test. Tests will take approximately half an hour each on average. If the user tester is available and willing to take the test, they will be sent instructions by the Solid panel coordinators. Solid panelist can withdraw from the panel at any point. To volunteer to become a Solid panelist contact the community manager.

## 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
* **Community Leader** - [Tim Berners-Lee](https://github.com/timbl)
* **Community Manager** - [Mitzi László](https://github.com/Mitzi-Laszlo)
* **Repositories 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, [Justin Bingham](https://github.com/justinwb), [Kjetil Kjernsmo](https://github.com/kjetilk)
* **Panel Coordinator** - Maya Rinehart, Felix Poon, [Tony Morelli](https://github.com/tony-morelli)
* **Solid Panelist** - [Eric Prud’hommeaux](https://github.com/ericprud), [Eduardo Ibacache Rodriguez](https://github.com/eduardoinnorway), [Teodora Petkova](https://github.com/TheodoraPetkova), [David Booth](https://github.com/dbooth-boston), [Pieter Hayvaert](https://github.com/pheyvaer)
* **Solid Event Organiser** - Solid event organisers are listed alongside the corresponsing [Solid Event](solid-events.md)