I 100% agree they shouldn't be the primary form of user support but it is really common to send people to a SIG mailing list or Slack channel if questions start to look like a bug or feature request. I think this is OK as it gets user feedback into the SIG loop.
On Thursday, May 18, 2017 at 10:55:35 AM UTC-7, Joe Beda wrote: > > Not taking a stand here but SIGs aren't really a user support mechanism. > We should have other support channels that don't have the long term > commitment of a SIG. > > Totally supportive of a slack channel or mailing list for azure user > support/help. > > Joe > > On Thu, May 18, 2017 at 10:47 AM Brendan Burns <brendan...@gmail.com > <javascript:>> wrote: > >> I'm very happy to see this SIG be recognized. We have a bunch of users >> and projects that this SIG can help support. >> >> >> On Monday, May 15, 2017 at 9:08:27 AM UTC-7, Tim Hockin wrote: >> >>> I'd rather see a sig-node that spawns topical subgroups. There are many >>> topics that cross-cultural all the clouds, and we have no such forum. >>> >> On May 15, 2017 8:34 AM, "Ihor Dvoretskyi" <ihor.dv...@gmail.com> wrote: >>> >> I'd be happy to see yet another member of a Cloud Providers SIGs family! >>> >>> On May 15, 2017 4:14 PM, "Jaice DuMars" <jdu...@gmail.com> wrote: >>> >>> All, >>>> >>>> I'd like to revive the effort to create >>>> <https://github.com/kubernetes/community/blob/master/sig-creation-procedure.md> >>>> >>>> SIG-Azure that was referenced in both this >>>> <https://github.com/kubernetes/community/pull/36> PR and this >>>> <https://github.com/kubernetes/community/issues/188> issue. >>>> >>>> *Proposed mission statement:* >>>> >>>> A Special Interest Group for building, deploying, maintaining, >>>> supporting, and using Kubernetes on Azure Container Service. >>>> >>>> *Secondary statement:* >>>> >>>> The SIG will be responsible for designing, discussing, and maintaining >>>> the Azure cloud provider and its relevant tests. The SIG will also be >>>> responsible for any roadmap and release requirements for Kubernetes on >>>> Azure. >>>> >>>> *Rationale and Raison D'être: * >>>> >>>> Since the time of the discussion linked above, Microsoft has become >>>> strategically-focused on Kubernetes as an indispensable component in the >>>> Azure ecosystem. This was underscored by the recent acquisition of Deis >>>> and GA rollout of Kubernetes in Azure Container Service. >>>> >>>> The purposes of the SIG are specifically: >>>> >>>> - Provide a consistent and accountable interface to the Kubernetes >>>> project/product management structure for features specific to the Azure >>>> cloud provider, as well as a readout space for efforts undertaken in other >>>> SIGs >>>> >>>> - Help organize the rapidly-growing ACS Kubernetes community for >>>> knowledge-sharing and feedback ~ ideally creating more engagement across >>>> the project as a whole >>>> >>>> - Establish a clear channel for ACS-specific Kubernetes community >>>> support, so it does not get misdirected into SIG-Windows >>>> >>>> - Building and curating documentation for Kubernetes on Azure >>>> - Provide a point of contact to build and maintain Azure-specific e2e >>>> tests for Kubernetes >>>> >>>> - Coordinating requirements for Azure integrators like ACS-Engine, >>>> CoreOS Tectonic for Azure >>>> >>>> - Raise visibility within Microsoft of opportunities to contribute and >>>> give back to Kubernetes >>>> >>>> *SIG Disambiguation:* >>>> >>>> To address potential overlap concerns with SIG-Windows, this group is >>>> specific to *workloads running in Azure Container Service*. The >>>> mission of SIG-Windows is complimentary not preemptory. Also, if a >>>> SIG-Cloud umbrella comes to fruition in the future, we will re-evaluate >>>> the >>>> need for this separate SIG at that point. The last thing we need is SIG >>>> sprawl. >>>> >>>> *Implementation:* >>>> >>>> For implementation, I will be the initial point of contact and will at >>>> a minimum ensure scheduling, documentation, transparency, and facilitation >>>> are consistent with Kubernetes community SIG standards. Initial (and >>>> possibly provisional) leadership will be Jason Hansen >>>> <https://github.com/slack> and Cole Mickens >>>> <https://github.com/colemickens>. >>>> >>>> An initial meeting cadence will be bi-weekly, and after the SIG is >>>> properly set up in Groups, Slack and other communications channels, the >>>> initial and subsequent meeting times will be radiated to the community. >>>> >>>> I'd like to work out concerns ahead of the 5/18 community meeting so >>>> that the SIG may be discussed and ideally approved at that time. >>>> >>>> Please let me know your questions and concerns. >>>> >>>> Kindest regards, >>>> Jaice Singer DuMars >>>> co-lead of SIG Cluster Ops >>>> ~ Formerly @Deis, Now @Microsoft >>>> >>>> -- >>>> 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-de...@googlegroups.com. >>>> To post to this group, send email to kuberne...@googlegroups.com. >>> >>> >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/kubernetes-dev/CAJHHSLyKNFC3BiM0tpBbqccDMha0UuKcPrFFfg4oi_q8yf1zQQ%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/kubernetes-dev/CAJHHSLyKNFC3BiM0tpBbqccDMha0UuKcPrFFfg4oi_q8yf1zQQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> 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-de...@googlegroups.com. >>> To post to this group, send email to kuberne...@googlegroups.com. >>> >>> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/kubernetes-dev/CA%2BhxP0v79jEfV5Vi%2BDOJhOMs3Qr8eW8Hi5S3VOmJXJ1YDkjasg%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/kubernetes-dev/CA%2BhxP0v79jEfV5Vi%2BDOJhOMs3Qr8eW8Hi5S3VOmJXJ1YDkjasg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >> 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-de...@googlegroups.com <javascript:>. >> To post to this group, send email to kuberne...@googlegroups.com >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/kubernetes-dev/65910432-b23b-4538-b602-725e57b1146e%40googlegroups.com >> >> <https://groups.google.com/d/msgid/kubernetes-dev/65910432-b23b-4538-b602-725e57b1146e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
