-
Notifications
You must be signed in to change notification settings - Fork 17
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
Please change your logo #90
Comments
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. |
@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. |
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. |
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?
Thanks!
The text was updated successfully, but these errors were encountered: