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

Individuals in roles #9

Merged
merged 3 commits into from
Jan 11, 2019
Merged

Individuals in roles #9

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5b11cd8
Individuals in roles
kjetilk Dec 17, 2018
973c7a7
Fix Eduardo's name
kjetilk Dec 17, 2018
c3dfdeb
A paste went wrong
kjetilk Dec 17, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 11 additions & 0 deletions community-roles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,3 +47,14 @@ technical content writing.
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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be trying to get as much feedback from as many people as we can, and I worry that requiring them to assume a named role in the community just to try something and provide feedback is heavy-handed. I think having the role is OK, but I'm not sure that we should manage "membership" ranks associated with the role. Instead, possibly provide attribution of who was participated.

This description is also quite skewed only to UX, when we would expect that panelists could provide feedback and discussion on other topics, from developer experience and linked data conventions to security.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would like to propose a notion of community groups here, because I think they may provide some versatility. An example of some group ideas:

  • Identity and Security
  • Application Development
  • Linked Data
  • Solid Server
  • Protocols and Standards
  • User Experience
  • Recognized Contributors (Alumni that may not be as active today but have played a substantial role and should be recognized)

Groups are a way to recognize people that are contributing around a given subject matter, which may span "projects". It may also be another angle on project contributors, where you back that out to a group which is responsible for a given set of projects / repositories. For example, the Identity and Security group could be focused on those projects / repos directly related to authentication, authorization, etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think we need to have a look at such divisions. One general goal I think we need to discuss is to what extent we would design the groups to be orthogonal, which I think would require us to put quite a lot of thought into it, or if we should just let them emerge and let it be quite fluid what goes where. There will be quite a lot of overlap between the "protocols and standards", "solid server" and "linked data", for example.

## Individuals currently occupying roles

* **Community Leader** - Tim Berners-Lee
* **Community Manager** - Mitzi László
* **Repository Manager** - Kjetil Kjernsmo
* **Project Release Manager** - Kjetil Kjernsmo
* **Solid Core Contributors** - Ruben Verborgh, Arne Hassel, Justin Bingham, Kjetil Kjernsmo
* **Panel Coordinator** - Maya Rinehart, Felix Poon, Tony Morelli
* **Solid Panelist** - Eric Prud’hommeaux, Eduardo Ibacache Rodriguez, Teodora Petkova, David Booth