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).
+
+ - [IDPBuilder](working-groups/idpbuilder/README.md)
 
 ## Contact
 

SIG-Governance.md

@@ -0,0 +1,19 @@
+# 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.
+
+## 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.
+
+### Leads
+
+SIG Leads are in line with Kubernetes SIG leads.
+
+
+| 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 | [sigs.yaml] subproject [OWNERS] file *owners* entry |
+| Lead | Set direction and priorities for a SIG | Demonstrated responsibility and excellent technical judgement for the SIG | sig [OWNERS] file *owners* entry |

sigs/idpbuilder/charter.md

@@ -0,0 +1,42 @@
+# SIG IDPBuilder
+
+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 Idpbuilder is responsible for developing common tooling for creating reference CNOE internal developer platforms.
+
+### In scope
+
+#### Code, Binaries and Services
+
+- idpbuilder project
+- 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