-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update authorization-ucr's editors #309
Comments
I would be interested in focusing on authorization UCRs for the coming months. |
I have so much on my plate with priority much higher than UCRs, but I will try to link the folks on EU projects related to LinkedData that have their own use cases that are looking into their own UCRs which may be the occasion for looking at ours and providing feedback. /cc @woutslabbinck, @philippecarlo others? |
From Digita, we would definitely like to contribute our findings about use cases we encounter(ed) in the field. I'm not sure we have someone who has sufficient time to take on an editorial role, though. @tomhgmns? |
Thanks all. @matthieubosquet , may I ask you to PR to update the editors list and add yourself to get things rolling? I encourage others to consider and commit to specific roles (e.g., editor, author, contributor) by requesting changes to the PR. |
What are UCRs? Edit: totally missed that first link. Use Cases & Requirements, got it. |
https://solid.github.io/authorization-panel/authorization-ucr/ indicates "Solid Editors Team" as the Editors of the document (
authorization-panel/proposals/authorization-ucr/index.bs
Line 9 in b2d4dca
I recommend that individuals that would like to make the commitment to take on the editorial role of the authorization-ucr document say so here in the comments or make a PR.
CG Chair hat on: Anyone is generally welcome to take on the editor role, provided that they are a member of the Solid CG, there is an understanding about the commitment to maintain the document - ensuring that Group decisions are correctly reflected - follow the Solid contributing guidelines, no outstanding formal objection from another CG member, approval by the CG chair, and so on.
The text was updated successfully, but these errors were encountered: