Open VSX Registry: Awareness and Important Steps

[brianking]

@marcdumais-work 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

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.

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!

[marcdumais-work]

Hi,

My team has a committer in this project, @marechal-p . Would he be considered an "owner" and be able to publish to open-vsx? If so I think he could at least re-publish one version of the extension, so that it's there to be tried.

[brianking]

@marechal-p could yes potentially take on this role, though it is not necessary for publishing. We could add him as a contributor, and once he signs the Publisher Agreement he can publish.

@jonahgraham has expressed interest in being the namespace owner, however whoever wants to lay claim to that needs to file an issue. More details at:
https://github.com/eclipse/openvsx/wiki/Namespace-Access

[marcdumais-work]

Thanks @brianking. I think it would make sense for @jonahgraham to be the namespace owner. Paul could potentially help punctually, if needed.

[spoenemann]

In the case of an eclipse project, IMO it's up to the project team (leads + committers) to decide who should manage the open-vsx.org namespace. It can be a committer, a project lead, or even multiple persons.

A namespace can have multiple owners and multiple contributors.

[brianking]

fyi, the extension has now been deavtivated.

For it to be active again, a new version will need to be published by someone who has signed the publisher agreement.

[jonahgraham]

@brianking - thanks - It is on my todo list.

@marechal-p as there can be multiple owners, do you want to be one of them please? I am somewhat limited on time to look at this.

[marcdumais-work]

In the meantime I have open a PR to attempt to auto-build and publish the latest version (by user "open-vsx"). The project can take-over the namespace and starts publishing at any time.

[GitMensch]

Is it still reasonable to have that on Open VSX? It seems that this extension is "stale" and as its README says

This is a preliminary milestone release

and the last commit to master was over a year ago this may mean that it is not ready for use yet?
If it is then I highly suggest to bump the version number to 1.0, remove the note from the README and release another version (maybe adding a CHANGELOG file and cleanup package.json for a nicer view in the Open VSX Registry and in the vscode extension view).

[jonahgraham]

@GitMensch - you are correct on all counts. At the moment some companies are building their own extensions off of forks of this bundle and cdt-gdb-adapter. The open question is there demand and support for someone to actually turn this into a "product" of its own.

So far I have not had the time (really received the demand to readjust my time!) to take this on.

I provide this comment to more clearly communicate my personal intentions in this regard as this has been on my "todo" list for quite a while and has not moved up it.

If others are interested in doing what is required, I am more than happy to facilitate!

[jonahgraham]

This has increased in priority now - we need to get this published to open-vsx in such a way to make the cycle back to CDT cloud blueprint / simrel easier.