Closed Mitzi-Laszlo closed 5 years ago
Turns out each repository has separate labels, here are my suggestions on what labels to include and the corresponding description in each repo along with a link to the current labels. If I haven't mentioned the label here then my suggestion is to delete it.
solid-releases talks solid-platform [solid-apps]https://github.com/solid/solid-apps/labels) solid-idps https://github.com/solid/solid-idp-list
react-components ldflex-playground solid-zagel solid-sign-up solid-signup solid-signin-ui solid-dashboard-ui solid-profile-ui solid-notification solid-auth-tls solid-web-client kvplus-files solid-connections-ui wac-allow mavo-solid oidc-rs solid-auth-oidc solid-permissions solid-cli jose keychain solid-email oidc-web https://github.com/solid/solid-multi-rp-client https://github.com/solid/solid-inbox https://github.com/solid/solid-client https://github.com/solid/solid-takeout-import https://github.com/solid/folder-pane https://github.com/solid/pane-registry https://github.com/solid/solid-pane-source https://github.com/solid/oidc-rp https://github.com/solid/source-pane https://github.com/solid/issue-pane https://github.com/solid/solid-panes https://github.com/solid/meeting-pane https://github.com/solid/contacts-pane https://github.com/solid/acl-check https://github.com/solid/node-solid-ws https://github.com/solid/profile-viewer-react https://github.com/solid/solid-namespace https://github.com/solid/solid-tpf https://github.com/solid/chat-pane https://github.com/solid/solid-ui https://github.com/solid/solid-gitter https://github.com/solid/oidc-op https://github.com/solid/solid https://github.com/solid/solid-auth-client https://github.com/solid/oidc-auth-manager https://github.com/solid/node-solid-server https://github.com/solid/query-ldflex
solid.mit.edu solid-tutorial-angular solid-tutorial-rdflib understanding-linked-data solid-tutorial-pastebin intro-to-solid-slides https://github.com/solid/profile-viewer-tutorial https://github.com/solid/dweb-summit-2018 https://github.com/solid/userguide https://github.com/solid/solid-tutorial-intro https://github.com/solid/vocab https://github.com/solid/solid-architecture https://github.com/solid/solid-spec https://github.com/solid/web-access-control-spec https://github.com/solid/webid-oidc-spec/labels
I think the repo manager needs to liberty in choosing labels, but consolidation is certainly helpful.
The labels triage
, inrupt-planning
and inrupt-sprint
are used operationally, even not so much right now, so we need those were appropriate.
I think it is useful to look at what labels are in use, e.g. https://github.com/solid/oidc-rp/labels to inform the decision on what we should be using too. If a label is in widespread use, it is problematic to delete them, at least.
What would you want the labels to be on the repos you manage?
It depends on how you need to manage stuff from case to case, difficult to create a general rule.
How about once the community roles are updated by @timbl then the repo managers of each repository can make the ultimate decision on the appropriate labels and descriptions?
@kjetilk the community roles have been updated and you are the Solid specifications repository manager so could you make sure the labels are active and there is a description please.
Each repo has labels which need clear descriptions. Suggestions for new labels welcome too.