opentelemetry.io
opentelemetry.io copied to clipboard
Opentelemetry PHP SDK Icon
Desired feature or idea. What would you like to see happen?
We'd love an OpenTelemetry PHP icon similar to the ones that the rest of the SIGs have on the website: https://opentelemetry.io/docs/instrumentation/
Thanks in advance!
cc:\ @tidal
@jkowall Would we be able to get your designer to create logos for the SIGs that weren't covered by the original drop? PHP, Rust, Swift, and C++ are missing iconography.
We also have a few more top-level concepts on the docs that could use icons.
I see that there is a JS icon, but other than the list on the website is there anywhere else these icons are meant to be used? I saw @trask used it for the java bot user. Are there other suggested applications?
Yeah - presentations, workshops, internal slide decks, etc.
@jkowall Would we be able to get your designer to create logos for the SIGs that weren't covered by the original drop? PHP, Rust, Swift, and C++ are missing iconography.
We also have a few more top-level concepts on the docs that could use icons.
Yes I can get Ella to help us with more icons. Do you have an idea as to what we should base them off? The open source project icons or do you want us to be creative? I am sure Ella has a lot of ideas for us.
Let me know if this is the list or we need anymore graphics work.
There's probably some other stuff that we'll want to get later, but it'd be great to get the languages filled out for now. I think the icons should look consistent with the existing Otel ones.
Okay, cool. I will get it going.
You can assign to me or @ella-bz
Guys, I have a question. I have the icons for PHP, Rust, Swift, and C++. Do I understand right that you want me to add the sign of SDK like I did for some other languages or it just got lost in files somewhere?

@Ella-bz - would love to see the PHP one when you get a chance!
These are what you mentioned. Let me know if it's working fine for you, cause it's exported from Figma.
I'm able to see them here. Thank you!
Looks like this issue & #392 are related.
Will be fixed via #1694