--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To post to this group, send email to stee...@kubernetes.io.
Visit this group at https://groups.google.com/a/kubernetes.io/group/steering/.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/c9ae28c7-8db7-4e8f-a016-7b5a96e86d28%40kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAHROWxRUGvr5o-DW9_9xd2gmyH1hBqO4pjPiKeiniBdmGAP_Eg%40mail.gmail.com.
I agree with Derek and Aaron.Thanks for asking.
On Wed, Apr 10, 2019, 7:42 AM Derek Carr <dec...@redhat.com> wrote:
I think stakeholders should only be parties that own the code for lack of a better term.If WG multitenancy is an implied stakeholder of WG Policy, then it really means that the SIGs that sponsor WG multitenancy are stakeholders to WG policy.
On Wed, Apr 10, 2019 at 10:38 AM Aaron Crickenberger <spi...@gmail.com> wrote:
My vote would be no. It's unclear to me what we would gain by the added complexity.--- aaron
On Tuesday, April 9, 2019 at 6:49:04 PM UTC-4, Nikhita Raghunath wrote:Hey Steering,Today WGs can only have other SIGs are stakeholders. While adding stakeholder SIGs for WG Policy (https://github.com/kubernetes/community/pull/3499), it was pointed out that WG Multitenancy would be a stakeholder as well.Can WGs have other WGs and committees as stakeholders too?-- Nikhita
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+unsubscribe@kubernetes.io.
To post to this group, send email to stee...@kubernetes.io.
Visit this group at https://groups.google.com/a/kubernetes.io/group/steering/.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/c9ae28c7-8db7-4e8f-a016-7b5a96e86d28%40kubernetes.io.
--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+unsubscribe@kubernetes.io.
+1 on the No.
On Wednesday, April 10, 2019 at 10:04:08 AM UTC-5, Brian Grant wrote:
I agree with Derek and Aaron.Thanks for asking.
On Wed, Apr 10, 2019, 7:42 AM Derek Carr <dec...@redhat.com> wrote:
I think stakeholders should only be parties that own the code for lack of a better term.If WG multitenancy is an implied stakeholder of WG Policy, then it really means that the SIGs that sponsor WG multitenancy are stakeholders to WG policy.
On Wed, Apr 10, 2019 at 10:38 AM Aaron Crickenberger <spi...@gmail.com> wrote:
My vote would be no. It's unclear to me what we would gain by the added complexity.--- aaron
On Tuesday, April 9, 2019 at 6:49:04 PM UTC-4, Nikhita Raghunath wrote:Hey Steering,Today WGs can only have other SIGs are stakeholders. While adding stakeholder SIGs for WG Policy (https://github.com/kubernetes/community/pull/3499), it was pointed out that WG Multitenancy would be a stakeholder as well.Can WGs have other WGs and committees as stakeholders too?-- Nikhita
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To post to this group, send email to stee...@kubernetes.io.
Visit this group at https://groups.google.com/a/kubernetes.io/group/steering/.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/c9ae28c7-8db7-4e8f-a016-7b5a96e86d28%40kubernetes.io.
--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To post to this group, send email to stee...@kubernetes.io.
Visit this group at https://groups.google.com/a/kubernetes.io/group/steering/.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAHROWxRUGvr5o-DW9_9xd2gmyH1hBqO4pjPiKeiniBdmGAP_Eg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To post to this group, send email to stee...@kubernetes.io.
Visit this group at https://groups.google.com/a/kubernetes.io/group/steering/.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/a90f4b39-a6e2-4c52-9191-707189f4fc10%40kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CANw6fcEieZXqGUjv_4cVipKk-99n3Kvq%3DZHEwKrcwUnFzg%3D0OQ%40mail.gmail.com.