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

Update Community Roles #44

Merged
merged 8 commits into from Apr 2, 2019
Merged

Update Community Roles #44

merged 8 commits into from Apr 2, 2019

Conversation

Mitzi-Laszlo
Copy link
Collaborator

Updated role descriptions to accurately describe current roles and responsibilities as well as include conclusions from #10

Updated role descriptions to accurately describe current roles and responsibilities as well as include conclusions from #10
@csarven
Copy link
Contributor

csarven commented Feb 5, 2019

@Mitzi-Laszlo If you have no objections, I can take on solid-spec as well.

@Mitzi-Laszlo
Copy link
Collaborator Author

Management of the Solid spec and architecture (which I understand is split over four repositories) is a key role that @timbl has recently spoken about. Perhaps we need a specific role for Solid specifications and architechture management? @michieldejong who previously worked on the Unhosted spec may also be a candidate. @timbl will need to make the final decision on allocating individuals to roles.

@RubenVerborgh
Copy link
Contributor

I think it is important that the governance of the spec is in the hands of people who know the history and have been involved in its writing.

This holds for any repository BTW: whenever possible, the people in governance roles preferably have a longer history with the repository itself. In general, we probably want to see roles as “earned” through contributions rather than “assigned”.

But indeed, definitely for the spec, @timbl should be very closely involved.

@melvincarvalho
Copy link

But indeed, definitely for the spec, @timbl should be very closely involved.

+1

I think the spec would benefit from a version number, with changes between versions subject to review.

## 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.
## Repository Manager
The Repository Manager is responisble for keeping the properties of their specific repository well-organised and communicating any changes clearly and publicly. The Respoitory Manager has admin rights of the repositosry they manage and is expected to attend the weekly recurring community support meeting.
Copy link
Contributor

Choose a reason for hiding this comment

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

typo 'Respoitory' and 'repositosry'

Copy link
Contributor

Choose a reason for hiding this comment

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

also responisble typo

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Include: "Repository Managers are responsible for moderating conversations to find consensus and merging pull requests on their respective repositories."

@cldwalker cldwalker mentioned this pull request Mar 6, 2019
@Mitzi-Laszlo
Copy link
Collaborator Author

I think the spec would benefit from a version number, with changes between versions subject to review.

@melvincarvalho is this along the lines of what you had in mind? https://github.com/solid/solid-spec/blob/master/CHANGELOG.md

cldwalker added a commit to cldwalker/community that referenced this pull request Mar 13, 2019
cldwalker added a commit to cldwalker/community that referenced this pull request Mar 14, 2019
cldwalker added a commit to cldwalker/community that referenced this pull request Mar 14, 2019
cldwalker added a commit to cldwalker/community that referenced this pull request Mar 14, 2019
@Mitzi-Laszlo
Copy link
Collaborator Author

Perhaps include the W3C Solid Community Chair(s)? https://www.w3.org/community/solid/

@Mitzi-Laszlo
Copy link
Collaborator Author

@justinwb mentioned an interest to being a core contributor too

@RubenVerborgh
Copy link
Contributor

Count me in too, but what exactly is "core"? Seems not yet defined.

@justinwb
Copy link
Contributor

@justinwb mentioned an interest to being a core contributor too

Just to keep the record accurate here - the point I raised was that this role was defined but was removed in an update approximately 4-6 weeks ago. @RubenVerborgh, @kjetilk, @megoth, and I were attributed to it prior to its removal. The point I raised was to restore it (which @timbl supported). I've pushed a couple commits to restore it and also make the description a bit more informative than what it was before.

@Mitzi-Laszlo
Copy link
Collaborator Author

Here's a related pull request with a suggested route forward #80

@Mitzi-Laszlo Mitzi-Laszlo merged commit 3bba1cd into master Apr 2, 2019
cldwalker added a commit to cldwalker/community that referenced this pull request Apr 2, 2019
Mitzi-Laszlo added a commit that referenced this pull request Apr 4, 2019
Fix invalid header link from #44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants