Closed castrojo closed 3 years ago
+1
So to spec this out:
As long as the destination page is either k8s project or CNCF controlled, I don't see a problem with this.
go.k8s.io/logo makes more sense and follows other conventions.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
/remove-lifecycle stale
Adding the good-first-issue label. /good-first-issue
If you are picking this issue up, here's how to proceed:
What we want to do: Create a new shortlink go.k8s.io/logo to point to https://branding.cncf.io/projects/kubernetes
Background:
How to do it:
If you have questions on how to proceed here, please ping me in the #sig-contribex channel on the k8s slack.
@nikhita: This request has been marked as suitable for new contributors.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue
command.
/remove good-first-issue
/assign @RinkiyaKeDad
@nikhita: GitHub didn't allow me to assign the following users: RinkiyaKeDad.
Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
As a joke @marcoceppi made https://326ce5.com/ which is the hex color code for Kubernetes blue so that if you need it for slides or whatever you're working on. It then points to https://branding.cncf.io/projects/kubernetes/
We should just do k8s.io/blue and have it point right to the CNCF logo page. In order to prevent (or encourage!) this bikeshed issue, we could do k8s.io/logos or something.