Add LinkedIn to K8s.io and K8s.dev

kubernetes / contributor-site

Code for kubernetes.dev

https://www.kubernetes.dev

Apache License 2.0

66 stars 154 forks source link

Add LinkedIn to K8s.io and K8s.dev #523

Open chris-short opened 7 months ago

chris-short commented 7 months ago

Now that the community has control of the LinkedIn page, it should be added to the web sites.

/sig contribex

chris-short commented 7 months ago

/sig contributor-experience

elan-devops commented 7 months ago

@chris-short I can help if you need someone to work on this. just fyi: I am new to Kubernetes contribution. Thanks!

pacoxu commented 5 months ago

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

pacoxu commented 5 months ago

https://github.com/kubernetes/website/issues/43842 (previous linkedin issue)
twitter: https://github.com/kubernetes/website/issues/46405

chris-short commented 5 months ago

@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.

Shubham82 commented 4 months ago

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!

mrbobbytables commented 3 months ago

/transfer contributor-site

k8s-ci-robot commented 3 months ago

@chris-short: The label(s) sig/contribex cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/contributor-site/issues/523): >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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

sftim commented 3 months ago

We should either track a similar issue for k/website, or put a checklist on this one.

Shubham82 commented 3 months ago

hi, JFI: The following similar issue is opened in k8s/website, https://github.com/kubernetes/website/issues/46405

sftim commented 3 months ago

https://github.com/kubernetes/website/issues/46405 is broadly similar, but is about 𝕏 not LinkedIn.

Shubham82 commented 3 months ago

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?

k8s-triage-robot commented 2 weeks ago

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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

Shubham82 commented 2 weeks ago

/remove-lifecycle stale /lifecycle frozen