contributor-site
contributor-site copied to clipboard
kubernetes
Add LinkedIn to K8s.io and K8s.dev
Now that the community has control of the LinkedIn page, it should be added to the web sites.
/sig contribex
@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.
/cc @sftim @tengqm
-
https://github.com/kubernetes/website/issues/43842 (previous linkedin issue)
-
twitter: https://github.com/kubernetes/website/issues/46405
@pacoxu
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. https://fontawesome.com/search PTAL!
@chris-short: The label(s) sig/contribex cannot be applied, because the repository doesn't have them.
In response to this:
Now that the community has control of the LinkedIn page, it should be added to the web sites.
/sig contribex
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.
hi, JFI: The following similar issue is opened in k8s/website, https://github.com/kubernetes/website/issues/46405
https://github.com/kubernetes/website/issues/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? @sftim your thoughts on this?
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle frozen Can we get this moving again? @chris-short @sftim? This was stuck on FontAwesome?
I'm happy for people to do this; I'd rather support / coach / review than lead on the implementation.
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.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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-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/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou 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.
We think this is dependent on fixes @SayakMukhopadhyay is making to k8s.dev. Also #568 which Chris mentioned, was closed but not merged.
@kaslin: Reopened this issue.
In response to this:
/reopen /remove-lifecycle rotten
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.
