Conversation
Updated role descriptions to accurately describe current roles and responsibilities as well as include conclusions from #10
@Mitzi-Laszlo If you have no objections, I can take on solid-spec as well. |
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. |
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. |
+1 I think the spec would benefit from a version number, with changes between versions subject to review. |
community-roles.md
Outdated
## 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo 'Respoitory' and 'repositosry'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also responisble
typo
There was a problem hiding this comment.
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."
@melvincarvalho is this along the lines of what you had in mind? https://github.com/solid/solid-spec/blob/master/CHANGELOG.md |
Perhaps include the W3C Solid Community Chair(s)? https://www.w3.org/community/solid/ |
@justinwb mentioned an interest to being a core contributor too |
Count me in too, but what exactly is "core"? Seems not yet defined. |
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. |
Here's a related pull request with a suggested route forward #80 |
Fix invalid header link from #44
Updated role descriptions to accurately describe current roles and responsibilities as well as include conclusions from #10