Open VSX Registry: Awareness and Important Steps

[brianking]

@entepe85 has published this extension in the Open VSX Registry.

The service was recently transferred to the Eclipse Foundation and we want to ensure a seamless transition for our users. To ensure uninterrupted service and more exposure for your extension, I recommend the following.

To the maintainers: If you would like to take over publishing to open-vsx.org, here’s how: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

To the current publisher: Please sign the Eclipse Publisher Agreement. The signing process is explained in the Wiki (steps 1 and 2).

Claiming ownership of the namespace for your extension(s). To find out how to do this, see: https://github.com/eclipse/openvsx/wiki/Namespace-Access As owner you can add more namespace members (including service accounts) yourself in https://open-vsx.org/user-settings/namespaces. Note that publishing can be done by any contributor to the extension, namely those you add as namespace members once they have signed the Publisher Agreement as well.

Please also note that a license is now mandatory for publishing your extension to Open VSX. If your project doesn't have any license, please add one, preferably an open source license such as MIT. The publishing tool ovsx offers to automatically add the MIT license when you try to publish without a license.

Useful links: Eclipse Publisher Agreement Eclipse Foundation Open VSX Registry Frequently Asked Questions (FAQ)

More details are in these recent blog posts: https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry

Today, there’s growing momentum around open source tools and technologies that support Visual Studio (VS) Code extensions. Leading global organizations are adopting these tools and technologies. This momentum has spurred demand for a marketplace without restrictions and limitations. We hope you join us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!

[ScriptAutomate]

This has confused me, as I see the following when I look on the Open VSX portal:

Does this mean that the GitLens maintained there by @entepe85 can be deprecated/archived? Since it looks like @open-vsx is now maintaining a copy of GitLens? As said on the Open VSX page for eamodio.gitlens

This version of the “GitLens — Git supercharged” extension was published by open-vsx. That user account is not a verified publisher of the namespace “eamodio” of this extension. See the documentation to learn how we handle namespaces and what you can do to eliminate this warning.

Unless @eamodio was planning on taking ownership over the eamodio namespace on Open VSX, and then maintaining ownership themselves instead of letting the Open VSX CI tool: open-vsx/publish-extensions continue to publish it automatically?

[coryshack]

Be careful there are two of a lot of cryptos and one is an imposter, I am helping the government crackdown and there are two telegraphs too!

On Thu, Jun 17, 2021 at 10:22 PM Derek Ardolf @.***> wrote:

This has confused me, as I see the following when I look on the Open VSX portal https://open-vsx.org/?search=gitlens&category=&sortBy=relevance&sortOrder=desc :

[image: image] https://user-images.githubusercontent.com/5951023/122495839-5f992d80-cfb0-11eb-85d9-1da58e838e99.png

Does this mean that the GitLens maintained there by @entepe85 https://github.com/entepe85 can be deprecated/archived? Since it looks like @open-vsx https://github.com/open-vsx is now maintaining a copy of GitLens? As said on the Open VSX page for eamodio.gitlens https://open-vsx.org/extension/eamodio/gitlens

This version of the “GitLens — Git supercharged” extension was published by open-vsx https://github.com/open-vsx. That user account is not a verified publisher of the namespace “eamodio” of this extension. See the documentation https://github.com/eclipse/openvsx/wiki/Namespace-Access to learn how we handle namespaces and what you can do to eliminate this warning.

Unless @eamodio https://github.com/eamodio was planning on taking ownership over the eamodio namespace on Open VSX https://github.com/eclipse/openvsx/wiki/Namespace-Access, and then maintaining ownership themselves https://github.com/eclipse/openvsx/wiki/Publishing-Extensions instead of letting the Open VSX CI tool: open-vsx/publish-extensions https://github.com/open-vsx/publish-extensions continue to publish it automatically?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/eamodio/vscode-gitlens/issues/1327#issuecomment-863705724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASR3YZVB2RPKORRPPVCLFUTTTKUVPANCNFSM4WCWNQEA .

[brianking]

I would say the entepe85 extension was published before the eamodio version. If you think one should be taken down, please open and issue at https://github.com/EclipseFdn/open-vsx.org/issues