<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes Contributors – SIG Apps</title><link>https://deploy-preview-776--kubernetes-contributor.netlify.app/community/community-groups/sigs/apps/</link><description>Recent content in SIG Apps on Kubernetes Contributors</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://deploy-preview-776--kubernetes-contributor.netlify.app/community/community-groups/sigs/apps/index.xml" rel="self" type="application/rss+xml"/><item><title>Community: SIG Apps Charter</title><link>https://deploy-preview-776--kubernetes-contributor.netlify.app/community/community-groups/sigs/apps/charter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-776--kubernetes-contributor.netlify.app/community/community-groups/sigs/apps/charter/</guid><description>
&lt;h1 id="sig-apps-charter">SIG Apps Charter&lt;/h1>
&lt;p>This charter adheres to the conventions described in the &lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md"
target="_blank" rel="noopener">Kubernetes Charter README&lt;/a>
and uses
the Roles and Organization Management outlined in &lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md"
target="_blank" rel="noopener">sig-governance&lt;/a>
.&lt;/p>
&lt;h2 id="scope">Scope&lt;/h2>
&lt;p>SIG Apps covers developing, deploying, and operating applications on Kubernetes with a focus on the application developer and application operator experience.&lt;/p>
&lt;h3 id="in-scope">In scope&lt;/h3>
&lt;h4 id="code-binaries-and-services">Code, Binaries and Services&lt;/h4>
&lt;ul>
&lt;li>APIs used for running applications (e.g., Workloads API)&lt;/li>
&lt;li>Tools and documentation to aid in ecosystem tool interoperability around apps (e.g., Application CRD/Controller)&lt;/li>
&lt;li>Grandfathered in tools used to aid in development of and management of workloads (e.g., Kompose)&lt;/li>
&lt;/ul>
&lt;h4 id="cross-cutting-and-externally-facing-processes">Cross-cutting and Externally Facing Processes&lt;/h4>
&lt;ul>
&lt;li>A discussion platform for solving app development and management problems&lt;/li>
&lt;li>Represent the needs and persona of application developers and operators&lt;/li>
&lt;/ul>
&lt;h3 id="out-of-scope">Out of scope&lt;/h3>
&lt;ul>
&lt;li>Code ownership of ecosystem tools. Discussion of the tools is in scope but ownership of them is outside the scope of Kubernetes aside from legacy situations&lt;/li>
&lt;li>Do not recommend one way to do things (e.g., picking a template language)&lt;/li>
&lt;li>Do not endorse one particular ecosystem tool&lt;/li>
&lt;/ul>
&lt;h2 id="roles-and-organization-management">Roles and Organization Management&lt;/h2>
&lt;p>This sig follows adheres to the Roles and Organization Management outlined in &lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md"
target="_blank" rel="noopener">sig-governance&lt;/a>
and opts-in to updates and modifications to &lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md"
target="_blank" rel="noopener">sig-governance&lt;/a>
.&lt;/p>
&lt;h3 id="additional-responsibilities-of-chairs">Additional responsibilities of Chairs&lt;/h3>
&lt;ul>
&lt;li>Report the SIG status at events and community meetings wherever possible&lt;/li>
&lt;li>Actively promote diversity and inclusion in the SIG&lt;/li>
&lt;li>Uphold the Kubernetes Code of Conduct especially in terms of personal behavior and responsibility&lt;/li>
&lt;li>Chairs oversee the subproject creation process&lt;/li>
&lt;/ul>
&lt;h3 id="deviations-from-sig-governance">Deviations from &lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md"
target="_blank" rel="noopener">sig-governance&lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>Generic technical leads are not appropriate for this SIG because sub-projects maintain their processes&lt;/li>
&lt;li>Chairs follow the Technical Leads process in the subproject creation process&lt;/li>
&lt;li>Proposing and making decisions MAY be done without the use of KEPs so long as the decision is documented in a linkable medium.&lt;/li>
&lt;/ul>
&lt;h3 id="subproject-creation">Subproject Creation&lt;/h3>
&lt;p>SIG Chairs following Technical Leads process defined in &lt;a href="https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md"
target="_blank" rel="noopener">sig-governance&lt;/a>
&lt;/p></description></item></channel></rss>