Allow migrating extension from namespace to another namespace

[jthomasmock]

Sometimes an individual developer might publish an extension under their own namespace, but then want to move it to their organization's namespace.

To the best of my knowledge, there is no migration on OpenVSX. The process is to publish elsewhere and deprecate the other one with a README update to tell the user to go to XXX to find the extension's new home.

Is it possible and/or would it be possible to build such a migration flow?

[netomi]

Right now there is the possibility to indicate that an existing extension is replaced by another one, see https://github.com/EclipseFdn/publish-extensions/blob/master/extension-control/extensions.json

moving an extension with all its versions to another namespace is an option, though we would need to ensure that the publisher of these extensions is also a member of the new namespace as some functionality is tied to the publisher.

[Shra-05]

I’m exploring how OpenVSX currently handles extension replacement and namespace ownership.
From what I see, extensions.json already supports marking an extension as replaced, but this doesn’t migrate versions or publisher ownership.

I’m trying to understand:

• whether namespace ownership checks are enforced at publish-time or registry-time
• whether a migration could reuse the existing replacement mechanism with additional metadata

Any guidance on constraints or preferred direction would be very helpful.