From e8d2711fcb58e7b8e51aae33ea7e4bb355a8fc4a Mon Sep 17 00:00:00 2001 From: Gregory Haynes Date: Tue, 23 Apr 2024 18:50:04 -0700 Subject: [PATCH 1/6] Add sig-idpbuilder Signed-off-by: Gregory Haynes --- README.md | 4 +++- SIG-Governance.md | 19 +++++++++++++++++ sigs/idpbuilder/charter.md | 42 ++++++++++++++++++++++++++++++++++++++ 3 files changed, 64 insertions(+), 1 deletion(-) create mode 100644 SIG-Governance.md create mode 100644 sigs/idpbuilder/charter.md diff --git a/README.md b/README.md index 2e94906..44d7e8b 100644 --- a/README.md +++ b/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 diff --git a/SIG-Governance.md b/SIG-Governance.md new file mode 100644 index 0000000..8bde5ae --- /dev/null +++ b/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 | \ No newline at end of file diff --git a/sigs/idpbuilder/charter.md b/sigs/idpbuilder/charter.md new file mode 100644 index 0000000..e9d3cd0 --- /dev/null +++ b/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 From 1928af690ad2dbbd7da9c37d8eef31c58bc911e5 Mon Sep 17 00:00:00 2001 From: Gregory Haynes Date: Tue, 23 Apr 2024 18:56:06 -0700 Subject: [PATCH 2/6] Fix table in sig governance roles Signed-off-by: Gregory Haynes --- SIG-Governance.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/SIG-Governance.md b/SIG-Governance.md index 8bde5ae..6c55d39 100644 --- a/SIG-Governance.md +++ b/SIG-Governance.md @@ -6,10 +6,6 @@ CNOE Special Interest Groups (SIGs) generally align with the scope, purpose, and 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 | | -----| ---------------- | ------------ | -------| From 373337244d096f188473e3209916874b77f31ac7 Mon Sep 17 00:00:00 2001 From: Greg Haynes Date: Wed, 24 Apr 2024 08:33:31 -0700 Subject: [PATCH 3/6] Add sig requirements Signed-off-by: Greg Haynes --- SIG-Governance.md | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-) diff --git a/SIG-Governance.md b/SIG-Governance.md index 6c55d39..c6b2713 100644 --- a/SIG-Governance.md +++ b/SIG-Governance.md @@ -2,6 +2,21 @@ 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. + ## 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. @@ -9,7 +24,7 @@ As we are a smaller community than Kubernetes, we have simplified the Roles for | 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 | \ No newline at end of file +| 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 | \ No newline at end of file From b3ea91c3b498fea43faabeef100cb983bff0e656 Mon Sep 17 00:00:00 2001 From: Greg Haynes Date: Wed, 24 Apr 2024 08:42:17 -0700 Subject: [PATCH 4/6] Add SIG approval info and bare OWNERS file Signed-off-by: Greg Haynes --- SIG-Governance.md | 6 +++++- sigs/idpbuilder/charter.md | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/SIG-Governance.md b/SIG-Governance.md index c6b2713..a8f34d2 100644 --- a/SIG-Governance.md +++ b/SIG-Governance.md @@ -17,7 +17,11 @@ CNOE Special Interest Groups (SIGs) generally align with the scope, purpose, and - Ensure contributing instructions (CONTRIBUTING.md) are defined in the SIGs folder located in the community repo. -## Roles +## 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. diff --git a/sigs/idpbuilder/charter.md b/sigs/idpbuilder/charter.md index e9d3cd0..90f297d 100644 --- a/sigs/idpbuilder/charter.md +++ b/sigs/idpbuilder/charter.md @@ -11,7 +11,7 @@ SIG Idpbuilder is responsible for developing common tooling for creating referen #### Code, Binaries and Services -- idpbuilder project +- [idpbuilder project](https://github.com/cnoe-io/idpbuilder) - related packaging tooling - suporting libraries for idpbuilder From 8aa103abedb0b1587e5791f836be62dacf04e8fd Mon Sep 17 00:00:00 2001 From: Greg Haynes Date: Wed, 24 Apr 2024 08:44:07 -0700 Subject: [PATCH 5/6] Add initial idpbuilder OWNERS Signed-off-by: Greg Haynes --- sigs/idpbuilder/OWNERS | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 sigs/idpbuilder/OWNERS diff --git a/sigs/idpbuilder/OWNERS b/sigs/idpbuilder/OWNERS new file mode 100644 index 0000000..e6e4a85 --- /dev/null +++ b/sigs/idpbuilder/OWNERS @@ -0,0 +1,3 @@ +owners: +approvers: +reviewers: From caedd2249ab7304d59bbcc1a8b0af6a84747152a Mon Sep 17 00:00:00 2001 From: Gregory Haynes Date: Thu, 25 Apr 2024 11:25:44 -0700 Subject: [PATCH 6/6] Change name to idp builders Signed-off-by: Gregory Haynes --- README.md | 2 +- sigs/{idpbuilder => idp-builders}/OWNERS | 0 sigs/{idpbuilder => idp-builders}/charter.md | 4 ++-- 3 files changed, 3 insertions(+), 3 deletions(-) rename sigs/{idpbuilder => idp-builders}/OWNERS (100%) rename sigs/{idpbuilder => idp-builders}/charter.md (86%) diff --git a/README.md b/README.md index 44d7e8b..302d10c 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ The steering committee consists of one member from each of the core member organ For information about the working group governance process, see [Working-Group-Governance.md](Working-Group-Governance.md). - - [IDPBuilder](working-groups/idpbuilder/README.md) + - [IDP Builders](sigs/idp-builders/charter.md) ## Contact diff --git a/sigs/idpbuilder/OWNERS b/sigs/idp-builders/OWNERS similarity index 100% rename from sigs/idpbuilder/OWNERS rename to sigs/idp-builders/OWNERS diff --git a/sigs/idpbuilder/charter.md b/sigs/idp-builders/charter.md similarity index 86% rename from sigs/idpbuilder/charter.md rename to sigs/idp-builders/charter.md index 90f297d..76f52f5 100644 --- a/sigs/idpbuilder/charter.md +++ b/sigs/idp-builders/charter.md @@ -1,11 +1,11 @@ -# SIG IDPBuilder +# 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 Idpbuilder is responsible for developing common tooling for creating reference CNOE internal developer platforms. +SIG IDP Builder is responsible for developing common tooling for creating reference CNOE internal developer platforms. ### In scope