-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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.
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
Add initial draft of wg lts annual report #7910
base: master
Are you sure you want to change the base?
Add initial draft of wg lts annual report #7910
Conversation
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
/unassign /assign @palnabarun (Steering Committee Liaison) |
wg-lts/annual-report-2023.md
Outdated
- white papers | ||
- work not tracked in KEPs | ||
--> | ||
During 2023, we worked to restart the WG. |
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.
Can you also please add notes from the discussion that happened during KCS EU 23?
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.
Here are the notes for the discussion at KCS EU 2023: https://docs.google.com/document/d/1C7utWMjGpDcBc5TB_ooddERsid59sFLC7gqLzyS5aKY/edit?usp=sharing
|
||
We also hosted a [maintainer track session](https://www.youtube.com/watch?v=0fngdOlwZtQ) at KubeCon NA in Chicago to discuss what the working group wanted to achieve. | ||
|
||
We have been meeting on a bi-weekly cadence, but have not provided updates to the sponsoring SIGs as most of 2023 was spent forming and drafting the survey. We will provide updates to the sponsoring SIGS during 2024. |
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.
nit,
We have been meeting on a bi-weekly cadence, but have not provided updates to the sponsoring SIGs as most of 2023 was spent forming and drafting the survey. We will provide updates to the sponsoring SIGS during 2024. | |
We have been meeting on a bi-weekly cadence, but have not provided updates to the sponsoring SIGs as most of 2023 was spent forming and drafting the survey. We will provide updates to the sponsoring SIG during 2024. |
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.
the change SIG
is applicable on line 10 too..
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.
There are several sponsoring SIGs for this WG.
--> | ||
During 2023, we worked to restart the WG. | ||
|
||
We also designed and published a [survey](https://bit.ly/k8s-upgrade-survey) to capture pain points and better understand challenges Kubernetes users face with upgrading. We collected 223 survey responses. From this data, we identified some areas where we can better communicate improvements that have already been made to the project. We plan to work on several of these during 2024 and will present analyzed results from the survey to the community and sponsoring SIGs during 2024. |
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.
imo, its better to list out the main topics/areas listed over here. Please discard this comment if its not a practice.
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
Signed-off-by: Jeremy Rickard <jeremyrrickard@gmail.com>
1ce6153
to
175c1c5
Compare
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closed this PR. In response to this:
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. |
/reopen Please continue with the annual report... 😅 |
@pohly: Reopened this PR. In response to this:
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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jeremyrickard The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Which issue(s) this PR fixes:
Fixes #7790