assigning issues based on area/X

[cmlu...@us.ibm.com]

SIG-ContribX discussed the possibility of auto-assigning SIG members to an issue during a triage. It would be useful to trigger a notification or have some way of alerting parties responsible for components within the SIG. For example if I know this issue relates to kube-proxy, I can add an area/kube-proxy label and notify kube-proxy contributors only. 

This workflow is similar to the OWNERS file for PRs, and adding a contributor section may be a viable solution. The repo splitting will certainly help with directing notifications, but k8s/kubernetes will still have pieces that need to be directed to the relevant parties.

Possible solutions:

• Github subteams under a SIG team for each component they want represented
  
• area/ labels trigger notifications to that subteam
• possibly auto-assign 2 members from the team
• Google mailing lists for different components
• area/ labels trigger notifications to that mailing list
• Extensions to the OWNERS mechanism adding contributors section
• area/ labels trigger notifications to the Github username
• possibly auto-assign 2 members from the team

- Christopher M Luciano (cmluciano)

[Michail Kargakis]

+sig-testing

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/61ad62a3-47b3-468e-8a84-ad16ff2a41e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.