-
Notifications
You must be signed in to change notification settings - Fork 155
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 LinkedIn to K8s.io and K8s.dev #523
Comments
/sig contributor-experience |
@chris-short I can help if you need someone to work on this. just fyi: I am new to Kubernetes contribution. Thanks! |
Do you mean that adding linkedIn https://www.linkedin.com/company/kubernetes/ to the footer of the websites? There is also no x(twitter) link in the footer as well. But we have link in right side of blog. |
|
Ooof... I completely ignore the right hand column out of muscle memory... I refer to it in docs more than the website itself. However, shouldn't all the socials the project manages be listed in the footer? I think we all believe yes is the right answer here. But, there's an Twitter/X change in FontAwesome icon sets. Plus, I'm dealing with confusion of which version of FontAwesome is actually being used. |
Hi @chris-short, IMO we can use fontawsome 6.6.0 (the latest one rn), as it includes both Linkedin and Twitter icons. |
/transfer contributor-site |
@chris-short: The label(s) 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. |
We should either track a similar issue for k/website, or put a checklist on this one. |
hi, JFI: The following similar issue is opened in k8s/website, |
kubernetes/website#46405 is broadly similar, but is about 𝕏 not LinkedIn. |
yeah, you are right. I'm just wondering can we consider both icon 𝕏 and LinkedIn, while opening the the new issue or making a checklist on this issue? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/remove-lifecycle frozen |
I'm happy for people to do this; I'd rather support / coach / review than lead on the implementation. |
(SIG Docs current leadership can also help) |
Yes. I'm not cookie licking this. Anyone who isn't in the middle of a job search have time to take a look? |
We discussed this during today's Contributor Comms meeting and more in Slack after the meeting in the comms channel. At this point, we commit to taking X off both sites and have Bluesky, Mastodon, and LinkedIn accounts added to the footers. We will still post to X for now, as it's our largest audience, but the platform's engagement and our account's reach are declining. We need a more in-depth analysis/discussion before deprecating X altogether. If you have strong feelings about social media, WE HEAR YOU. Feel free to ping me on Slack (chris-short there, too) if you want to share opinions or ideas. As always, feel free to join the Comms meeting to discuss things with mouthwords. |
#568 Fixes this |
Now that the community has control of the LinkedIn page, it should be added to the web sites.
/sig contribex
The text was updated successfully, but these errors were encountered: