One thing that is popping up now and again is that currently, our extension is tied to coreysharris as a "namespace". While the publisher name appears as Macaulay2, its official identifier is coreysharris.macaulay2:
On the open-vsx registry, this is displayed more prominently:
If we change this, vscode will recognize it as a new extension. As I see it, we can either:
- Keep
coreysharris as the namespace attached to this extension.
- Change it to
m2-team or Macaulay2 or something.
If we choose (2), we can handle this by marking the current package as "deprecated", and recommend a new package (see here). This would give the user a "migrate" button which would automatically switch them over to the new one. Personally, I don't mind keeping coreysharris that much as a nod to the initial package, but I can see how it might not look very official or be as trusted as attaching it to the Macaulay2 organization.
Anyways, we'd probably want to figure this out before trying to get our extension "verified".
One thing that is popping up now and again is that currently, our extension is tied to coreysharris as a "namespace". While the publisher name appears as Macaulay2, its official identifier is
coreysharris.macaulay2:On the open-vsx registry, this is displayed more prominently:
If we change this, vscode will recognize it as a new extension. As I see it, we can either:
coreysharrisas the namespace attached to this extension.m2-teamorMacaulay2or something.If we choose (2), we can handle this by marking the current package as "deprecated", and recommend a new package (see here). This would give the user a "migrate" button which would automatically switch them over to the new one. Personally, I don't mind keeping coreysharris that much as a nod to the initial package, but I can see how it might not look very official or be as trusted as attaching it to the Macaulay2 organization.
Anyways, we'd probably want to figure this out before trying to get our extension "verified".