Either update your copy or remove it

[PeterWone]

Your website is pushing a version of my extension that is both obsolete and broken because it's missing dependencies in the repackaging that you took it upon yourselves to do.

This broken version is attributed to me even though it's YOUR fault and is damaging the reputation of my product.

A package without the dependencies is different from the extension as published by me so it's a derived work for licence purposes and since you aren't compliant with the MIT licence requirement to conspicuously acknowledge that it is a derived work, you are in violation of copyright.

Here are your options:

• Take it down
• Comply with the licence

If you choose to comply with the licence then I suggest you use the current version. Exercising my right to vary the terms of licence I have added a requirement to publish the current version within two weeks of its release on the Microsoft Marketplace or cease publishing it altogether.

[akosyakov]

Hi @PeterWone, sorry for the trouble.

If you choose to comply with the licence then I suggest you use the current version. Exercising my right to vary the terms of licence I have added a requirement to publish the current version within two weeks of its release on the Microsoft Marketplace or cease publishing it altogether.

Unfortunately, we cannot make use of vsix file from MS marketplace, since it will be violation of its terms of use. That's why vsix file is generated from sources.

Ideally we would take down the currently broken extension from automatic publishing by the service account and remove from OpenVSX and alternatively let you take the ownership of namespace and publishing: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions. Would you be opened it?

Another variant if you can either provide GH releases with vsix downloadable or a tag which corresponds to the release with steps how we can bundle dependencies. From that we should be able to compile with your requirements.

[PeterWone]

Thank you for responding. For the interim please take down the broken VSIX. I have been meaning to set up CICD to the MS website. While I am doing this I will also look at pushing updates to openvsx using the method you mention.

[akosyakov]

I removed the extension from publishing script: EclipseFdn/publish-extensions@160ba89

@brianking @spoenemann Could you take down the extension from OpenVSX please? 🙏

@PeterWone I am going to open an issue in your repo to publish to OpenVSX with some pointers and also to clarify for users.

[spoenemann]

Could you take down the extension from OpenVSX please?

All versions, or specific ones?

[akosyakov]

I think the entire extension. The request is to ensure that we publish within 2 weeks, and 0.9.8 is 5 months old.

[PeterWone]

I haven’t tested them all so I’m going to say ALL please. Next release is likely to be 1.0 so that’s a good place to start afresh.

[spoenemann]

Done, but next time please open an issue at https://github.com/EclipseFdn/open-vsx.org for deletion of extensions or anything else regarding the public instance at open-vsx.org

[akosyakov]

The issue on the extension to publish to OpenVSX: PDConSec/vsc-print#120