davraamides
commented
3 years ago Hi Brian,
I read the agreement and agree to it, but did not see a method to actually sign it. I also submitted an issue to claim the namespace "davraamides".
Let me know if there is anything else I need to do. -David
On Thu, Jan 7, 2021 at 10:04 AM Brian King notifications@github.com wrote:
Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please sign the Eclipse Publisher Agreement on or before January 8, 2021. If not signed by that date, your extensions will be delisted and will no longer appear on the site nor be available via the API. If you sign at a later date, your extensions will then be re-activated. The signing process is explained in the Wiki (steps 1 and 2).
Please also note that all extensions MUST have a license in order to be listed.
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
If you are the project maintainer, we urge you to claim the namespace for your extension(s). To find out how to do this, see: https://github.com/eclipse/openvsx/wiki/Namespace-Access
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. Thanks for joining us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/davraamides/todotxt-mode/issues/22, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOOZGJTCJUP234TKWN6JQ3SYXEPTANCNFSM4VZDGNOQ .
brianking
spoenemann
Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please sign the Eclipse Publisher Agreement on or before January 8, 2021. If not signed by that date, your extensions will be delisted and will no longer appear on the site nor be available via the API. If you sign at a later date, your extensions will then be re-activated. The signing process is explained in the Wiki (steps 1 and 2).
Please also note that all extensions MUST have a license in order to be listed.
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
If you are the project maintainer, we urge you to claim the namespace for your extension(s). To find out how to do this, see: https://github.com/eclipse/openvsx/wiki/Namespace-Access
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. Thanks for joining us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!