Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

2023 Annual Report: SIG Multicluster #7775

Closed
6 tasks
palnabarun opened this issue Mar 17, 2024 · 4 comments · May be fixed by #7861
Closed
6 tasks

2023 Annual Report: SIG Multicluster #7775

palnabarun opened this issue Mar 17, 2024 · 4 comments · May be fixed by #7861
Assignees
@pmorie @JeremyOT
Labels
area/annual-reports Issues or PRs related to the annual reports committee/steering Denotes an issue or PR intended to be handled by the steering committee. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.

Comments

@palnabarun
Copy link
Member

2023 Annual Report: SIG Multicluster

Chairs: @JeremyOT @pmorie
Liaison: @mrbobbytables

Actions for the chair/organizer of the community group:

  • Consult your community group to complete draft of report
  • If needed, consult with Steering Committee liaison on any private issues or concerns that arrise while completing report
  • Submit PR to git.k8s.io/community repo with copy of report, assigning your Steering Committee liaison for review
  • Steering Committee reviews report, and may make comments/ask questions
  • Once all comments are addressed, Steering Committee will approve report to merge
  • If needed, any follow up items may be brought to the "Chairs, Tech Leads, and Organizers" meeting in April

Once all the above items are complete, this issue may be /close'd

Key dates:

  • Initial PR to communtiy repo should be opened by May 1, 2024
  • PR should be reviewed and merged by May 22, 2024

More detailed information on the annual reports process is available here.

Your group's report template is available here: https://git.k8s.io/community/sig-multicluster/annual-report-2023.md

If you have any questions or concerns about this process, you may reach the Steering Committee via the following methods:

  • Slack/E-mail your liaison directly
  • The public #steering-committee channel in Slack
  • The public mailing list [email protected]
  • The private mailing list [email protected] for any private or sensitive issues.

/assign @JeremyOT @pmorie
/sig multicluster
/committee steering
/area annual-reports
@k8s-ci-robot k8s-ci-robot added sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. committee/steering Denotes an issue or PR intended to be handled by the steering committee. area/annual-reports Issues or PRs related to the annual reports labels Mar 17, 2024
@lauralorenz lauralorenz mentioned this issue Apr 30, 2024
Open
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 15, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 15, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pmorie pmorie

@JeremyOT JeremyOT

Labels
area/annual-reports Issues or PRs related to the annual reports committee/steering Denotes an issue or PR intended to be handled by the steering committee. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[WIP] SIG-MC 2023 annual report update lauralorenz/community
5 participants
@pmorie @JeremyOT @palnabarun @k8s-ci-robot @k8s-triage-robot