Close the sub-projects under SIG-Community Experience

codificat commented 2 years ago

Persona / User

Members of SIG-Community Experience

User's Story

The team has decided, over the last 2 meetings, to handle all the work of SIG-Community Experience directly by the SIG, without the need to distribute it through sub-projects

Reason

It is perceived that there is not enough volume to justify separate work streams.

Define Done

[x] SIG documentation is updated to reflect the change: charter document, information in sigs.yaml
[ ] Any outstanding issue/task assigned to the SIGs is moved/reassigned, or closed, where appropriate
[x] GitHub projects for each SP are archived (after the issues have been sorted out):
- [x] SP GovOrg: https://github.com/orgs/open-services-group/projects/7
- [x] SP ComCom: https://github.com/orgs/open-services-group/projects/8
- [x] SP Metrics Strategic: https://github.com/orgs/open-services-group/projects/9
- [x] SP Metrics: ~~https://github.com/orgs/open-services-group/projects/6~~ (this project is/was owned by SIG Data Science
[x] ~~area/ labels related to the SPs removed from labels.yaml~~ no need to do this, as long as it still serves to differenciate work within the SIG

Additional Info

See the meeting notes and recordings for 2022-04-20 and 2022-05-04.

codificat commented 2 years ago

/sig community-experience

codificat commented 2 years ago

I started to work on this: /triage accepted /assign /lifecycle active

However, it seems a SIG without any sub-project is not valid - at least according to the tooling: this happens if I try to remove all SPs from SIG-CE in sigs.yaml:

$ podman run --rm --volume $(pwd):/workdir:Z quay.io/open-services-group/community-tooling:v0.1.0-dev
Validating sigs.yaml
ERROR: sig-community-experience: has no subprojects

The Kubernetes community governance documentation says this about sub-projects within SIGs:

Specific work efforts within SIGs are divided into subprojects. Every part of the Kubernetes code and documentation must be owned by some subproject. Some SIGs may have a single subproject, but many SIGs have multiple significant subprojects[...]

sesheta commented 2 years ago

@codificat: The label(s) triage/accepted cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/open-services-group/community/issues/178#issuecomment-1129802659): >I started to work on this: >/triage accepted >/assign >/lifecycle active > >However, it seems a SIG without any sub-project is not valid - at least according to the tooling: this happens if I try to remove all SPs from SIG-CE in `sigs.yaml`: > >``` sh >$ podman run --rm --volume $(pwd):/workdir:Z quay.io/open-services-group/community-tooling:v0.1.0-dev >Validating sigs.yaml >ERROR: sig-community-experience: has no subprojects >``` > >The [Kubernetes community governance documentation](https://github.com/kubernetes/community/blob/3373d359399bd87a6bd729f4e07edf9e09a97fba/governance.md#subprojects) says this about sub-projects within SIGs: > >> Specific work efforts within SIGs are divided into subprojects. Every part of the Kubernetes code and documentation must be owned by some subproject. Some SIGs may have a single subproject, but many SIGs have multiple significant subprojects[...] Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

sesheta commented 1 year ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

schwesig commented 1 year ago

working on it right now

codificat commented 1 year ago

working on it right now

and it's done: all sig-community-experience issues are now closed. /close

sesheta commented 1 year ago

@codificat: Closing this issue.

In response to [this](https://github.com/open-services-group/community/issues/178#issuecomment-1269710870): >> working on it right now > >and it's done: all sig-community-experience issues are now closed. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

open-services-group / community