-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Update old blog article about SIG Usability to mention dissolution #42390
Conversation
Welcome @fykaa! |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Minor suggestions added. PTAL
Co-authored-by: Nitish Kumar <justnitish06@gmail.com>
Co-authored-by: Nitish Kumar <justnitish06@gmail.com>
/retitle Update old blog article about SIG Usability to mention dissolution |
Co-authored-by: Dipesh Rawat <rawat.dipesh@gmail.com>
/honk |
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/test-infra repository. |
SIG Usability, which is featured in this Spotlight blog, has been deprecated and is no longer active. | ||
As a result, the links and information provided in this blog post may no longer be valid or relevant. | ||
Should there be renewed interest and increased participation in the future, the SIG may be revived. However, for the time being, it will be inactive as per the Kubernetes community policy. | ||
We encourage you to explore other [SIGs](https://github.com/kubernetes/community/blob/master/sig-list.md#special-interest-groups) and resources available on the Kubernetes website to stay up-to-date with the latest developments and enhancements in Kubernetes. |
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's one author (Kunal), so who does “we” refer to here?
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.
In this context, "we" refers to the Kubernetes community and not the author of the blog post. It's common for community announcements, updates to use "we" to represent the collective voice of the organization providing the information. In this case, "we" includes the community folks who are informing readers about the deprecation of SIG Usability and encouraging them to explore other resources and SIGs within the Kubernetes community.
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.
in the context of Note
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.
In this context, "we" refers to the Kubernetes community and not the author of the blog post. It's common for community announcements, updates to use "we" to represent the collective voice of the organization providing the information. In this case, "we" includes the community folks who are informing readers about the deprecation of SIG Usability and encouraging them to explore other resources and SIGs within the Kubernetes community.
That's fine, but: don't explain this only to the reviewers. Please make it clear to readers 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 a couple of tweaks to do here. (Source) wrapping does help, and I think we should write the note as the Kubernetes project for clarity.
This kind of clarity also helps localization teams correctly prepare localized versions of articles with a low risk of misunderstanding.
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
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.
Deploy preview: https://deploy-preview-42390--kubernetes-io-main-staging.netlify.app/blog/2021/07/15/sig-usability-spotlight-2021/
Since this is updating someone else's work, tagging the original author: @kunal-kushwaha
/lgtm
LGTM label has been added. Git tree hash: 567173c3262a56a627fdb012efe3f66d67049c9f
|
Hi @fykaa Looks like Netlify has got mixed up here. Can you rebase against main and, ideally, squash it to fewer commits? |
/lgtm |
LGTM label has been added. Git tree hash: 4b126b88c262a9ece71b491353cbffd9527d0e0b
|
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.
/approve
/hold
You can make a further fix here @fykaa, or you can say you'd prefer to go with this as-is (unhold the PR and merge what's there right now). Please let us know which way you'd like to go.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
As of June 15, 2023, SIG Usability has been shut down. The reason behind this decision was that there weren't enough active members to sustain the group. Many people who were initially interested in joining the SIG had to deal with changes in their jobs, roles, and focus due to the impact of the pandemic. As a result, momentum on the various projects within the SIG slowed down.
The Slack channel for the SIG is now archived, and the links on the Spotlight blog are no longer working since the SIG Usability page does not exist on the GitHub repository anymore. However, to keep interested readers informed, it's important to update the SIG spotlight blog on the website with this new development.
For more details, you can find the PR that closed SIG Usability here: GitHub PR and past discussions on the mailing list here: Mailing List Discussions.
This was also discussed in the recent SIG ContribEx meet on 4th August 2023
cc: @kaslin @fsmunoz