you can label for area/platform/azure On Fri, May 19, 2017 at 2:43 PM, 'Eric Tune' via Kubernetes developer/contributor discussion <kubernetes-...@googlegroups.com> wrote: > I was just triaging new issues today and I wanted to label one sig/azure, > but I can't (yet). > > On Fri, May 19, 2017 at 2:42 PM, jack quincy <jazer2...@gmail.com> wrote: >> >> +1 >> >> On Monday, May 15, 2017 at 6:14:18 AM UTC-7, Jason Singer DuMars wrote: >>> >>> All, >>> >>> I'd like to revive the effort to create SIG-Azure that was referenced in >>> both this PR and this 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 and Cole Mickens. >>> >>> 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-dev+unsubscr...@googlegroups.com. >> To post to this group, send email to kubernetes-...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/kubernetes-dev/de76ed1e-185f-4c43-8733-71aba00ebd35%40googlegroups.com. >> >> 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-dev+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/kubernetes-dev/CAASt_VFTBEN5KvucC4Fam7TBrOXZoUiga-Jb6NZr6fgMmEsp7g%40mail.gmail.com. > > 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.
