In general, we'd prefer if people mentioning teams would mention them by using one of the following suffixes rather than misc:
Can we change the error message here to reflect this preference rather than suggesting the use of the misc suffix.
@bgrant0607 @kubernetes/sig-contributor-experience-feature-requests
There are no sig labels on this issue. Please add a sig label by:
(1) mentioning a sig: @kubernetes/sig-<team-name>-misc
e.g., @kubernetes/sig-api-machinery-* for API Machinery
(2) specifying the label manually: /sig <label>
e.g., /sig scalability for sig/scalability
_Note: Method (1) will trigger a notification to the team. You can find the team list here and label list here.
The asterisk has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals_
While the other team aliases are more specific, I'm not sure they've quite got the adoption. For example, for our own contribex, hitting feature-requests hits 5 people, vs -misc that hits 21. This would be the same for sig-testing (7 vs 18).
Is there a way we could encourage adoption if we continue down this path? or is it preferred to just move to mentioning a user and it sends to an e-mail list path (which I believe had started to be implemented, but not sure if it was ever finished).
I see user confused by the * : https://github.com/kubernetes/kubernetes/issues/48147#issuecomment-311454933
@xiangpengzhao I was suggested to have *. Please refer PR #3232 why we decided to have *.
@cblecker I could encourage adoption of other teams by deleting the misc teams. :-)
And hitting more people is not a good thing. Hitting the RIGHT people is what's important.
This was addressed. I'm going to
/close
this issue. Feel free to correct me if I'm wrong.