search

Azure / azure-powershell-migration

Tools and resources to help migrate PowerShell scripts between incompatible versions of Az and AzureRM modules
MIT License
35 stars 18 forks source link

Please change your logo #90

Open andyleejordan opened 3 years ago

andyleejordan commented 3 years ago

We are already using this graphic for the PowerShell (and PowerShell Preview) extension for Visual Studio Code. Can you please create a new logo that indicates this is specifically Azure PowerShell tools?

image

Thanks!

andyleejordan commented 3 years ago

Actually I just noticed that this entire extension is simply a copy of our extension, with modifications. Is there perhaps a better way we could collaborate? Our extension is very buggy and has improved immensely since you forked it. @SydneyhSmith are you in touch on the PM side of this project at all? We should probably follow up internally. I am sure @rjmholt has many ideas to improve this without having to take on the debt of forking.

keithbabinec commented 3 years ago

@andschwa -- The PM for this project is @dcaro, he can help with those conversations.

The goal of our project is a standalone extension that should not provide overlapping functionality with the vscode-powershell project.

Its likely that our extension developers leveraged vscode-powershell as a foundation or template since we required a similar code analysis pattern-- but then implemented our own features.

If our extension contains unnecessary pieces from vscode-powershell, they could be removed or cleaned up from this project and that sounds like a reasonable ask.

andyleejordan commented 3 years ago

I have since changed our extensions' logos to avoid this collision in the marketplace since your logo remains unchanged. I would still recommend that you change your logo to something that indicates your extension's specificity to the Azure PowerShell module(s) and not just PowerShell itself.