Add sig-idpbuilder

README.md

@@ -36,7 +36,9 @@ The steering committee consists of one member from each of the core member organ
 
 ## Working Groups
 
-Over time we will formalize our working group proceses, pulling from standard OSS processes such at Kubernetes' SIGs. In the meanwhile, the steering committee is responsible for managing the working groups CNOE consists of.
+For information about the working group governance process, see [Working-Group-Governance.md](Working-Group-Governance.md).
+
+ - [IDP Builders](sigs/idp-builders/charter.md)
 
 ## Contact
 

SIG-Governance.md

@@ -0,0 +1,34 @@
+# SIG Governance
+
+CNOE Special Interest Groups (SIGs) generally align with the scope, purpose, and and governance processes defined by [Kubernetes SIG Governance](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md). Although there are many cases where we cannot replicate the specifics of this Kubernetes process, we aim to align ourselves with the spirit of this process.
+
+## Requirements for a SIG
+
+- Have an approved Charter under sigs/sig-name/charter.md.
+- Meet regularly, at least for 30 minutes every 3 weeks, except November and
+  December.
+- Keep up-to-date meeting notes, linked from the SIG's page in the community
+  repo..
+- Ensure related work happens in a project-owned GitHub org and repository,
+  with code and tests explicitly owned and supported by the SIG, including
+  issue triage, PR reviews, test-failure response, bug fixes, etc.
+- Use the community slack as the primary means of working, communicating,
+  and collaborating, as opposed to private emails and meetings.
+- Ensure contributing instructions (CONTRIBUTING.md) are defined in the SIGs
+  folder located in the community repo.
+
+## SIG Approval
+
+Approval of a SIG charter (and therefore creation of a SIG) is made by the CNOE Steering committee following their standard decision making processes.
+
+## SIG Roles
+
+As we are a smaller community than Kubernetes, we have simplified the Roles for SIG and their subprojects. We also are folding in [community roles](https://github.com/kubernetes/community/blob/master/community-membership.md) to SIGs and their subprojects.
+
+
+| Role | Responsibilities | Requirements | Defined by |
+| -----| ---------------- | ------------ | -------|
+| Reviewer | Review contributions from other members | History of review and authorship in a subproject | [OWNERS] file *reviewer* entry |
+| Approver | Contributions acceptance approval| Highly experienced active reviewer and contributor to a subproject | [OWNERS] file *approver* entry|
+| Subproject owner | Set direction and priorities for a subproject | Demonstrated responsibility and excellent technical judgement for the subproject | [OWNERS] file *owners* entry |
+| Lead | Set direction and priorities for a SIG | Demonstrated responsibility and excellent technical judgement for the SIG | sigs/sig-name/OWNERS file *owners* entry |

sigs/idp-builders/OWNERS

@@ -0,0 +1,3 @@
+owners:
+approvers:
+reviewers:

sigs/idp-builders/charter.md

@@ -0,0 +1,42 @@
+# SIG IDP Builders
+
+This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
+the Roles and Organization Management outlined in [sig-governance].
+
+## Scope
+
+SIG IDP Builder is responsible for developing common tooling for creating reference CNOE internal developer platforms.
+
+### In scope
+
+#### Code, Binaries and Services
+
+- [idpbuilder project](https://github.com/cnoe-io/idpbuilder)
+- related packaging tooling
+- suporting libraries for idpbuilder
+
+#### Cross-cutting and Externally Facing Processes
+
+- creating cnoe packaging standards or formats
+
+### Out of scope
+
+Defining what is vs is not considered CNOE or "core" compoents of CNOE.
+
+## Roles and Organization Management
+
+This sig follows adheres to the Roles and Organization Management outlined in [sig-governance]
+and opts-in to updates and modifications to [sig-governance].
+
+### Additional responsibilities of Chairs
+
+
+### Additional responsibilities of Tech Leads
+
+
+### Deviations from [sig-governance]
+
+
+### Subproject Creation
+
+1. SIG Technical Leads