Maybe this is an opportunity to formalize "workgroups"? With the idea being that "workgroups" can be a focal point for cross-cutting concerns across multiple SIGs. Workgroups can be as big or small as needed, and either ephemeral (and disband as the original concerns are addressed) or remain indefinitely.
Not sure if this is the right forum to carry on the discussion from the community meeting, so please feel free to redirect me. On Thu, May 18, 2017 at 11:06 AM, <miche...@deis.com> wrote: > +1 on creating SIG Azure especially for representing the ACS-specific > Kubernetes community and their needs. > > +1 on Aaron's point. > > On Thursday, May 18, 2017 at 1:56:59 PM UTC-4, aa...@deis.com wrote: >> >> I'm +1 on creating a SIG-Azure, and additionally creating a SIG-Cloud or >> similar at some later date. There are certainly cross cutting concerns that >> in an ideal world, no cloud-specific SIG should figure out in isolation. In >> my mind a SIG-Cloud should be a gathering place for all the cloud-specific >> groups to come together, identify these concerns, and solve them together. >> >> On Thursday, May 18, 2017 at 10:52:50 AM UTC-7, Brandon Philips wrote: >>> >>> Hey Everyone- >>> >>> +1 for SIG formation from me. >>> >>> Someone from CoreOS can be involved in this SIG as we rely on the Azure >>> cloud integrations in CoreOS Tectonic. The same folks involved in SIG AWS >>> and pushing AWS features forward can help with cross-cloud SIG comms too. >>> >>> Aside, as it was mentioned during the call today: I had discussed >>> creating a SIG Cloud at some point in various forums. But, I have been too >>> busy with all of the bootstrap governance stuff to tackle that next. >>> Obviously getting governance in place is higher priority and should help >>> make that decision. >>> >>> Thank You, >>> >>> Brandon >>> >>> 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 >>>> <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-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/f8070053-d3cd-4b21-8c74-84a1bc1a644a% > 40googlegroups.com > <https://groups.google.com/d/msgid/kubernetes-dev/f8070053-d3cd-4b21-8c74-84a1bc1a644a%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.
