-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Replace links to 𝕏 with Bluesky #49546
base: main
Are you sure you want to change the base?
Conversation
1087ff1
to
4af2cc7
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
docsy current version apparently doesn't have fontawesome for bluesky... |
99cae12
to
3ac2698
Compare
3ac2698
to
ff56248
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cpanato 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 |
/lgtm cancel We should do this incrementally: change the English localization strings and the layout, then let localization teams pull this following their working pattern. Otherwise, we need n approvals and that includes teams such as Ukrainian who are short on capacity (due to geopolitics amongst other concerns). @rikatz please adjust accordingly and force-push (adding a second commit isn't the right approach; I want you to squash out the changes that touch non-English localizations). |
/retitle Replace links to 𝕏 with Bluesky |
While I fully support this change (funny enough, I made a similar change for another CNCF project on the very same day :-D), I'm a bit puzzled by the @kubernetes.io account activity on Bluesky. Its latest skeet is dated November only, while X/Twitter has newer posts from January. I suppose we want to see fresh and consistent activity in Bluesky before merging this change. |
There are two official bluesky acocunts, kubernetes.io (user facing) and kubernetes.dev (contributor facing), the latter has a post from this month. The recent cc @kubernetes/contributor-comms |
That makes sense; thank you for the clarification! If the localisation issue is the only one left to progress, I'm happy to assist with creating relevant language-specific PRs (if needed) to propagate these changes after they are removed from this main PR. |
PR needs rebase. 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. |
FYI: The Bluesky accounts are not in Buffer yet and aren't part of the comms automation. Hence, the missing content seen on other platforms. @kaslin has engaged the CNCF service desk and escalated to get more funding to add the accounts to Buffer. It's taking a while due to KCNA, holidays, etc. |
Description
Change footers and social media pages on Bluesky.
As this is a partial proposal, if the proposal is accepted we need to also add the right icons on static assets and request for localization teams to fix on their own contributing pages.
This change does not request for sig-contribex to drop X.com account, but instead we as a community to prioritize / give visibility to our bluesky account