I don't think Microsoft will take down our icons.

This PR is ruining our collection.

Their terms specifically say you need permission to include them. Regardless of whether or not we think they'll send a take-down, we should obtain permission before continuing to have them in our collection.

Their terms specifically say you need permission to include them. Regardless of whether or not we think they'll send a take-down, we should obtain permission before continuing to have them in our collection.

Here's hoping the Microsoft (and/or Adobe) icons make a return in a future release!

This PR is ruining our collection.

It's a heavy blow, for sure - however we should've historically identified the need to ask for consent. The fact we did not at the time means the least we can do is retroactively remove the offending icons, and seek permission to add them again.

Given how long the icons have been in the collection without issue thus far, you're probably right in that they don't care too much - but that doesn't mean we should ignore their trademark terms.

The use of the F# Software Foundation Logo for F# is welcome and encouraged when used in a way that is supportive of the mission statement of the F# Software Foundation. Individuals and companies are encouraged to incorporate the F# Software Foundation logo for F# on their website, brochures, and other media for activities that support the mission of the foundation.

Refer: https://foundation.fsharp.org/logo

C++ is not owned by Microsoft.

https://isocpp.org/home/terms-of-use

We should probably update this logo though and ask for permission.

C is not owned by Microsoft either.

The current logo in simple icons is from the cover page of the book "The C Programming Language" published by Prentice Hall, now defunct company.

We can probably keep using the icon.

I think we need to refer to the threshold of originality where possible, and potentially adapt something similar (officially) ourselves. I would argue, given we're not restricted to one territory - we should adhere to the strictest possible rules on copyright, that being that if guidance is place, or the shape is complex enough to not be classed as a 'basic shape' (uses a custom font or illustration, essentially) then we have to adhere to copyright rules.

In that respect, both the C++ and C# icons we include would fall under 'too simple to copyright' - based on my understanding of the above link.

We might need to add Internet Explorer to this list. Anyway, it is kind of deprecated now...

Internet Explorer is already on the list ;)

Internet Explorer is already on the list ;)

Yesterday felt like a difficult day. You confirmed it was 😅

You will get the attention of a lot of GitHub users.

Oh I know it will, but in the absence of us having permission, we will need to remove them.

Guess what? Even Mircosoft is using them. Like this one:

https://github.com/MicrosoftDocs/azure-devops-docs/blob/main/docs/pipelines/includes/get-status-badge.md

Unless I'm missing something, that's a statically generated badge which, being the rightsholders to that icon, they're totally able to do. Point being I don't think we as a project should make their icons available without their permission, given the size of the org and the confusing nature of their ToS.

If we can get written permission from Microsoft to continue hosting these icons, then we're good.

Would you mind sending them an email? The email address of their open-source team can be found at https://github.com/microsoft.

See Discord :)

Microsoft were contacted 22nd April 2024, meaning by our guidelines they have until 22nd June 2024 to respond, before we should re-visit this removal.

My gut tells me at that point we should look to remove all Microsoft icons, and only retain/add where explicit permission is given moving forward. Probably one to line up for v13.

I'm not contempting for the trademark law, but I'm curious that do ALL of the icons in this repository have got explict permissions? If not, why do you only removing Microsoft-related icons?

Removing these widely-used icons will only break many things, such as many project badges (ones related to Microsoft technologies). As Microsoft didn't contacted the maintainers for taking down, I highly recommend you to think again before finally removing these. Thanks.

You're correct - a lot of other companies will not have given explicit permission. The difference here is that Microsoft (and Adobe, for that matter) are incredibly obscure with their Terms. Some documents say zero permission is granted, whereas others grant full access for specific use cases. We have reached out to Microsoft for guidance, but have yet to hear back.

man, rip

Response from Microsoft's lawyers is that we can only include icons from the architecture icon packs, and only if we do not alter them in any way (colour, path, etc). This therefore means all of the above icons (have removed a few) need to be removed.

@adamrusted Given that, why did you need to remove these specific icons? I don't not fully understand the reasoning behind it, could you please elaborate on that?

We need to optimize and merge the paths of the icons and they are presumably not like that from the source. Additionally, we remove the color from the logos - that constitutes changing the color.

Given the popularity and use-case of your's library im pretty sure another request should lead to success. Tell them that you would need to neutralize the color, and have to change path's due to local needs. Pretty sure it was a generic response, not knowing the scope of your's project and im pretty certain Microsoft doesnt want to be left out with many cool documentation icons.

We've informed them about our project and how we use their icons, described in the above comments. Another response won't change anything.