Change Solid logo back to normal purple version

[KyraAssaad]

Needs to be changed on:

• Twitter - @MarrelleBailey
• This Month in Solid newsletter - @MarrelleBailey
• Solid Forums - @justinwb
• Solid Gitter - @justinwb

[jaxoncreed]

Is this an action we want to continue with? At the moment, the forum has not been swapped back.

[KyraAssaad]

The original intent was to change it to the rainbow version during Pride month (June) and keep it as the original purple version the rest of the year. I would propose that we swap it back to purple and then if there is an admin who can commit to swapping it in and out for June, we can proceed with that.

On Wed, Jan 11, 2023 at 3:06 PM jaxoncreed ***@***.***> wrote: Is this an action we want to continue with? At the moment, the forum has not been swapped back. — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZPSWIRTEVJYLEQRY6PPCDWR4HE3ANCNFSM47XEGXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Kyra Assaad*, Product Design Lead Connect | LinkedIn <https://www.linkedin.com/in/kyraassaad/>, WebID <https://id.inrupt.com/kyra> Explore | www.inrupt.com

…

-- This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged, confidential and/or proprietary information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), please do not disseminate, distribute, print or copy this e-mail, or any attachment thereto. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the email.

[megoth]

AFAICT this has been resolved? I'm closing it for now, but please reopen if I'm mistaken.

[KyraAssaad]

No, it's still the rainbow version [image: image.png] I don't know who the admin is who can change it back.

…

On Mon, Feb 19, 2024 at 9:58 AM Arne Hassel ***@***.***> wrote: AFAICT this has been resolved? I'm closing it for now, but please reopen if I'm mistaken. — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACZPSWPHWBEHA3X74X2OPVDYUNSC5AVCNFSM47XEGXHKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJVGI3DENZSHAYA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged, confidential and/or proprietary information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), please do not disseminate, distribute, print or copy this e-mail, or any attachment thereto. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the email.

[megoth]

Then it should be resolved ^_^ (Justin helped me with the change in the forum, so many thanks to him)

I'll close the issue for now, but let me know if I'm mistaken.