community, wg, arch: add wg, sig subprojects and charter for S390x and ARM #298
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -152,6 +152,33 @@ sigs: | |
| - https://raw.githubusercontent.com/kubevirt/kubevirt/main/hack/OWNERS | ||
| - https://raw.githubusercontent.com/kubevirt/kubevirt/main/hack/builder/OWNERS | ||
| - https://raw.githubusercontent.com/kubevirt/kubevirt/main/bazel/OWNERS | ||
| - name: arch-s390x | ||
| description: | | ||
| The arch-s390x subproject takes care of all matters related to building and compiling for s390x architecture. | ||
| leads: | ||
| - github: jschintag | ||
| name: "Jan Schintag" | ||
| company: IBM | ||
| - github: cfilleke | ||
| name: "Cheryl Fillekes" | ||
| company: IBM | ||
| - github: vamsikrishna-siddu | ||
| name: "vamsikrishna-siddu" | ||
| company: IBM | ||
| owners: | ||
| - https://raw.githubusercontent.com/kubevirt/kubevirt/main/OWNERS | ||
| - https://raw.githubusercontent.com/kubevirt/kubevirtci/main/OWNERS | ||
| - https://raw.githubusercontent.com/kubevirt/containerized-data-importer/main/OWNERS | ||
| - name: arch-arm | ||
| description: | | ||
| The arch-arm subproject takes care of all matters related to building and compiling for arm architecture. | ||
| leads: | ||
| - github: zhlhahaha | ||
| name: "Howard Zhang" | ||
| company: ARM | ||
| owners: | ||
| - https://raw.githubusercontent.com/kubevirt/kubevirt/main/OWNERS | ||
| - https://raw.githubusercontent.com/kubevirt/kubevirtci/main/OWNERS | ||
| mission_statement: | | ||
| SIG buildsystem takes care of all things building and automating for the KubeVirt project - they ensure new and existing contributors have a smooth contribution experience, i.o.w. contributors shouldn't have the feeling that they are wasting their time. | ||
| This includes bazel, test automation and updates, also support of failing builds or test lanes in case of infrastructural or configuration problems. | ||
|
|
@@ -201,6 +228,63 @@ sigs: | |
| teams: | ||
| - name: kubevirt-community | ||
| description: General Discussion | ||
| subprojects: | ||
| - name: ci-s390x | ||
| description: | | ||
| The ci-s390x subproject takes care of all matters related to CI for s390x architecture. | ||
| leads: | ||
| - github: jschintag | ||
| name: "Jan Schintag" | ||
| company: IBM | ||
| - github: cfilleke | ||
| name: "Cheryl Fillekes" | ||
| company: IBM | ||
| - github: vamsikrishna-siddu | ||
| name: "vamsikrishna-siddu" | ||
| company: IBM | ||
| - github: chandramerla | ||
| name: "Chandra Merla" | ||
| company: IBM | ||
| owners: | ||
| - https://raw.githubusercontent.com/kubevirt/project-infra/main/OWNERS | ||
| - name: ci-arm | ||
| description: | | ||
| The ciarch-arm subproject takes care of all matters related to CI for arm architecture. | ||
| leads: | ||
| - github: zhlhahaha | ||
| name: "Howard Zhang" | ||
| company: ARM | ||
| owners: | ||
| - https://raw.githubusercontent.com/kubevirt/project-infra/main/OWNERS | ||
| workinggroups: | ||
| - dir: wg-arch-s390x | ||
|
There was a problem hiding this comment. @cfilleke @jschintag @vamsikrishna-siddu hey, here's the entry for the wg arch S390x, please chime in here with the things you want to have added, I'll happily integrate them |
||
| name: S390x architecture working group | ||
| mission_statement: | | ||
| WG ARCH s390x takes care of all things related to supporting s390x architecture on KubeVirt clusters. | ||
| This includes all build processes, also support of failing builds or test lanes. | ||
| label: wg-arch-s390x | ||
| leadership: | ||
| chairs: | ||
| - github: jschintag | ||
| name: "Jan Schintag" | ||
| company: IBM | ||
| - github: cfilleke | ||
| name: "Cheryl Fillekes" | ||
| company: IBM | ||
| - github: vamsikrishna-siddu | ||
| name: "vamsikrishna-siddu" | ||
| company: IBM | ||
| - dir: wg-arch-arm | ||
| name: ARM architecture working group | ||
| mission_statement: | | ||
| WG ARCH ARM takes care of all things related to supporting ARM architecture on KubeVirt clusters. | ||
| This includes all build processes, also support of failing builds or test lanes. | ||
| label: wg-arch-arm | ||
|
There was a problem hiding this comment. @zhlhahaha hey, here's the entry for the wg arch arm, please chime in here with the things you want to have added, I'll happily integrate them There was a problem hiding this comment. Do we have a definition of what chairs/lead responsibilities are? I want to know that before agreeing. There was a problem hiding this comment.
if we map that to WG chairs then I figure WG chairs are responsible of WG operation and for communication and coordination with stakeholder SIGs. This is mostly organizational topics, see k8s wg-governance @aburdenthehand @fabiand @lyarwood WDYT? There was a problem hiding this comment. @awels we recently updated the membership policy by adding some roles here: https://github.com/kubevirt/community/blob/main/membership_policy.md#special-interest-group-sig-chair There was a problem hiding this comment. If @andymcc agrees I would be okay with being co-chair with him. |
||
| leadership: | ||
| chairs: | ||
| - github: zhlhahaha | ||
| name: "Howard Zhang" | ||
| company: ARM | ||
| usergroups: | ||
| - dir: kubevirt-community | ||
| name: KubeVirt Community | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| # WG ARM architecture Charter | ||
|
|
||
| ## Scope | ||
|
|
||
| The ARM architecture working group takes care of all things related to supporting ARM architecture on KubeVirt clusters. | ||
| This includes all build processes, also support of failing builds or test lanes. | ||
|
|
||
| ## Governance | ||
|
|
||
| ### Stakeholder SIGs | ||
|
|
||
| #### sig-buildsystem | ||
|
|
||
| subprojects: | ||
| * arch-arm | ||
|
|
||
| #### sig-ci | ||
|
|
||
| subprojects: | ||
| * arch-arm | ||
|
|
||
| ### Roles and responsibilities | ||
|
|
||
| #### Chairs | ||
| - @zhlhahaha | ||
|
|
||
| #### Subproject leads | ||
|
|
||
| ##### sig-buildsystem | ||
| - @zhlhahaha | ||
|
|
||
| ##### sig-ci | ||
| - @zhlhahaha |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| # WG S390x architecture Charter | ||
|
|
||
| ## Scope | ||
|
|
||
| The S390x architecture working group takes care of all things related to supporting s390x architecture on KubeVirt clusters. | ||
| This includes all build processes, also support of failing builds or test lanes. | ||
|
|
||
| ## Governance | ||
|
|
||
| ### Stakeholder SIGs | ||
|
|
||
| #### sig-buildsystem | ||
|
|
||
| subprojects: | ||
| * arch-s390x | ||
|
|
||
| #### sig-ci | ||
|
|
||
| subprojects: | ||
| * arch-s390x | ||
|
|
||
| ### Roles and responsibilities | ||
|
|
||
| #### Chairs | ||
| - @jschintag | ||
| - @cfilleke | ||
| - @vamsikrishna-siddu | ||
|
|
||
| #### Subproject leads | ||
| ##### sig-buildsystem | ||
| - @jschintag | ||
| - @cfilleke | ||
| - @vamsikrishna-siddu | ||
|
|
||
| ##### sig-ci | ||
| - @jschintag | ||
| - @cfilleke | ||
| - @vamsikrishna-siddu | ||
| - @chandramerla |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dhiller
A Question fust for my understanding-
Currently it seems these subproject names aren't used in any OWNERS files. So do we need to update/create OWNERS file along side the code files/dirs while we commit the code and hence we don't refer sub-project names anywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, exactly - my intent is to add the subprojects first, and when you add new OWNERS files where you take ownership of code, then the sigs.yaml will be updated with a reference (hopefully by some automation 😄 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when you say "the sigs.yaml will be updated with a reference ", do you mean updating the "owners:" section in the subprojects of sigs.yaml?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes