Skip to content
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

Consider becoming a verified VS Code publisher #11978

Closed
isidorn opened this issue Apr 13, 2022 · 10 comments
Closed

Consider becoming a verified VS Code publisher #11978

isidorn opened this issue Apr 13, 2022 · 10 comments
Labels
A-vscode vscode plugin issues

Comments

@isidorn
Copy link

isidorn commented Apr 13, 2022

Hi VS Code PM here 👋

It would be great if you verify your extension author https://marketplace.visualstudio.com/items?itemName=matklad.rust-analyzer
More about this process can be found here https://code.visualstudio.com/api/working-with-extensions/publishing-extension#verify-a-publisher

Let me know if I can help in any way.

@Veykril
Copy link
Member

Veykril commented Apr 13, 2022

We are going to publish the extension under the rust-lang publisher in the coming month(s), is that one verified already (I don't know how to check that)?

And since you are here right now I guess I can drop the question here but is it possible to transfer extensions between publishers by any chance? It would be great if we could move the extension the rust-lang publisher (and as such keep the great rating we have accumulated over time :) ).

@Veykril Veykril added the A-vscode vscode plugin issues label Apr 13, 2022
@isidorn
Copy link
Author

isidorn commented Apr 14, 2022

@Veykril great that you will publish under rust-lang. And that one is also not verified
https://marketplace.visualstudio.com/publishers/rust-lang
So it would be great if you get that one verified :)

Yes, we can move the extension. For that the author of the extension needs to send an email to vsmarketplace@microsoft.com and me inikolic@microsoft.com and we can do the rest.
Keep in mind that moving the extension under a new publisher will:

  • break any extension packs that might have that extension - they will need to get updated to take into account the new extension publisher
  • break any extension recommendations if that extension is recommended - I can update this on the vscode side
  • break any extension dependencies if those extensions depend on the extension being moved

I think for all three you should be good.

fyi last milestone we changed our rust recommendation so we recommend this extension since we think you are doing great work 👏

@Veykril
Copy link
Member

Veykril commented Apr 14, 2022

Oh that is great to hear, I expected moving not to be an option actually so this is great news :)

I'll talk to the relevant people regarding the verification.

@isidorn
Copy link
Author

isidorn commented Apr 27, 2022

Thanks. Has there been any updates?

@Veykril
Copy link
Member

Veykril commented Apr 27, 2022

Oh yes, someone should've sent out the application for verifying rust-lang -> see https://rust-lang.zulipchat.com/#narrow/stream/301329-t-devtools/topic/verify.20the.20.60rust-lang.60.20publisher.20on.20the.20vscode.20marketplace

Regarding the extension move we still have to fix up some things on our side before we want to do that.

@isidorn
Copy link
Author

isidorn commented Apr 27, 2022

@Veykril thanks a lot for doing that!
Feel free to reach out to me in case you hit some issues.

@Veykril
Copy link
Member

Veykril commented May 5, 2022

Maybe a stupid question but has the rust-lang publisher been verified? I don't know where this is supposed to be visible on the publisher profile page.

@lnicola
Copy link
Member

lnicola commented May 5, 2022

@Veykril yeah:

image

@Veykril
Copy link
Member

Veykril commented May 5, 2022

Oh so this is only visible on the extensions pages, not the publisher

@Veykril
Copy link
Member

Veykril commented May 12, 2022

Closing then as it has been verified, will get in touch with the people necessary to start the publisher transfer.

@Veykril Veykril closed this as completed May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-vscode vscode plugin issues
Projects
None yet
Development

No branches or pull requests

3 participants