-
Notifications
You must be signed in to change notification settings - Fork 24
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
Request for team labels in GitHub #593
Comments
@robcraig-LF - If I create the labels, could you add them to the PR's when posting the minutes? I'll probably use the shorter name. |
It doesn't appear as if I have the required permission level to assign labels...sorry. |
@robcraig-LF I created all the label with the exception of "joint". Since "joint" is a joint call with tech and legal, I suggest we add both of those labels rather than having a "joint" label. If you could go through the backlog of open pull requests and add the labels, that would be very helpful. |
You can use this tracker #592 to assist that. |
I think we can close this issue. |
As there are growing numbers of issues and PRs, having labels will help contributors organise and audience find relevant info easier.
When open PR for a meeting minute, the contributor may assign a label (if they have a permission), so it can be easily tracked.
Purposed GitHub labels, taken from existing team and topical group names:
AI
* orAI and Data
Asia
* orAsia Tech
Build
*Canonical
* orCanonicalisation
General
*Implementers
*Joint
*Legal
*Outreach
*Safety
* (Functional Safety / FuSa)Security
*Serialisation
*Service
* (Software as a Service)Hardware
Steering
*Tech
*(*currently used as a folder name for the corresponding meeting minutes)
The text was updated successfully, but these errors were encountered: