-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Use new .NET logo in NuGet packages. #77695
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsCurrently the .NET packages in NuGet have this logo: How about we change it into this? We can change the
|
The .NET logo is specified here. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsCurrently the .NET packages in NuGet have this logo: How about we change it into this? We can change the
|
(the .NET bot does not track PRs that close issues in another repository) |
I believe there's a sanctioned color scheme. @csharpfritz ? |
That's right... there is a sanctioned color scheme and logo to be used. As a thought exercise though, this is a good discussion for how to update the packages if a new default logo is assigned for NuGet packages |
I think the idea is that the current logo is using the old color scheme. See this patch where a similar change was made to the installer: dotnet/installer#389 |
Can someone also change the logo of the |
Looks like the default image is controlled via a gravatar.com profile for the dotnetframework org. Any ideas who may have access @richlander or @terrajobst? |
Yes, we own this. I finally managed to login to Gravatar and change the picture. Probably takes a bit for caches to reflect this. |
Currently the .NET packages in NuGet have this logo:
How about we change it into this?
We can change the
dotnetframework
NuGet organization logo as well. Besides the updated design, it would be a quick indicator of which packages haven't been updated in a while. I could do it myself if I knew where this image lives (if it's public).The text was updated successfully, but these errors were encountered: