-
Notifications
You must be signed in to change notification settings - Fork 104
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
Get a project logo #1325
Comments
+1, my laptop lid only has one sad, lonely RHEL-9 sticker. It absolutely needs an SPO sticker! |
I'd dig it! Preferably if it's a walrus |
Do we have someone who could support us with that? |
Yep, that's a great idea. @saschagrunert CNCF seems to offer this type of service: https://www.cncf.io/services-for-projects/#design-and-aesthetics. I am not entirely sure how it works for projects under kubernetes-sigs, but for projects directly under CNCF you just need to open a ticket. |
I tried to open a ticket but their site is within a scheduled maintance window right now. |
I have created a request for Logo and Website (CNCFSD-1502). Let me know if any of you have a Service Desk account so I can share the ticket with you. Hopefully we get a reply soon. 🤞 |
I had access to the CNCF service desk, but my account does not seem to exist any more. Anyways, thank you for opening the ticket @pjbgf. How will the website work? Do we get a domain, or will we host the website via GitHub pages directly? |
I am not sure how the website works, I am waiting for them to come back on the ticket to get more information about it. For the logo, I am assuming it is similar to the Security Audit services, in which we will have a follow-up meeting to discuss expectations. So as soon as I heard more I will relay here. |
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 |
Still waiting for a reply, sent a bump today. /remove-lifecycle stale |
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 |
So far no updates, sending a chaser. /remove-lifecycle stale |
Got a reply from CNCF Today:
I will ping the KSC 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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@pjbgf do we still want this? :) |
@saschagrunert I closed this one by mistake, I think we are still keen on a project logo. |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
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 |
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:
You can:
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:
You can:
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:
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. |
I think having a project logo would help the SPO to boost visibility within the community. The logo could also be re-used for operator hub and similar.
The text was updated successfully, but these errors were encountered: