content/legal/eca/faq/_index.md

+---
+title: Eclipse Contributor Agreement (ECA) FAQ
+author: Mike Milinkovich
+keywords:
+  - legal
+  - documents
+  - about
+  - contributor
+  - license
+  - agreement
+  - IP
+  - intellectual property
+  - ECA
+---
+
+{{< pages/legal/eca-faq >}}

content/legal/eclipse-foundation-quality-verification-suite-license/index.md

+---
+title: Eclipse Foundation Quality Verification Suite License - v 1.0
+author: Eclipse Foundation
+keywords:
+  - legal
+  - documents
+  - license
+  - quality verification
+---
+
+{{< pages/legal/eclipse-foundation-quality-verification-suite-license >}}

content/legal/efsl-1.1/index.md

+---
+title: Eclipse Foundation Specification License
+author: Eclipse Foundation
+keywords:
+    - legal
+    - Eclipse Foundation Specification License
+---
+
+**Do not modify the text of this license.**
+
+Specification project committers: include this text _verbatim_ in your specification document.
+
+An AsciiDoc version of this file is available [here](/legal/adoc/efsl-1.1.adoc). Plain HTML is [here](efsl.html).
+
+The Eclipse Foundation TCK License is [here](/legal/tck).
+
+↓ The actual licence text starts below this line. ↓
+
+***
+
+{{< pages/legal/inject-content >}}

content/legal/efsl/index.md

+---
+title: Eclipse Foundation Specification License
+author: Eclipse Foundation
+keywords:
+    - legal
+    - Eclipse Foundation Specification License
+---
+
+**Do not modify the text of this license.**
+
+Specification project committers: include this text _verbatim_ in your specification document.
+
+An AsciiDoc version of this file is available [here](/legal/adoc/efsl-2.0.adoc). Plain HTML is [here](efsl.html).
+
+The Eclipse Foundation Specification License version 1.1 is available [here](/legal/efsl-1.1).
+
+The Eclipse Foundation TCK License is [here](/legal/tck).
+
+↓ The actual licence text starts below this line. ↓
+
+***
+
+{{< pages/legal/inject-content >}}

content/legal/efsp-non-assert/index.md

+---
+title: Specification Non Assertion Covenant
+author: Wayne Beaton
+keywords:
+    - specifications
+    - non assert
+---
+
+April 13, 2020
+
+To the extent you submit or otherwise make available to an Eclipse Foundation Specification Project (as that term is defined by the Eclipse Intellectual Property Policy) any ideas, concepts, methods or other information, you agree that you will not assert, based on such submissions, any intellectual property rights that are essential to any implementation of the submission, against the Eclipse Foundation, its contributors, or its licensees, with respect to any implementation of such Specification (as that term is defined by the Eclipse Foundation Specification Process).
+To further clarify, such submissions include, but are not limited to, submissions made to any public communications channel such as an email list, forum, bug report, or GitHub issue submissions.

content/legal/epl-2.0/_index.md

+---
+title: Eclipse Public License 2.0 (EPL)
+layout: single
+author: Wayne Beaton
+hide_page_title: true
+keywords:
+  - epl
+  - epl-2.0
+  - legal
+  - foundation
+  - eclipse
+  - eclipse public license
+  - license
+  - licenses
+---
+
+{{< pages/legal/inject-content >}}

content/legal/epl-2.0/faq/_index.md

+---
+title: EPL-2.0 FAQ
+author: Wayne Beaton
+hide_page_title: true
+keywords:
+  - epl
+  - epl-2.0
+  - faq
+  - legal
+  - foundation
+  - eclipse
+  - eclipse public license
+  - license
+  - licenses
+---
+
+{{< pages/legal/inject-content >}}

content/legal/epl/about-file-templates/index.md

+---
+title: About File Templates
+author: Wayne Beaton
+keywords:
+  - about
+  - legal
+  - foundation
+page_css_file: public/css/legal/about-file-templates.css
+related:
+  links:
+    - text: EPL-2.0 - `about.html` in plain HTML
+      url: epl-2-about.html
+    - text: EPL-2.0 - Third-Party Content `about.html` in plain HTML
+      url: epl-2-longabout.html
+    - text: EPL-2.0 - Legal Documentation for Eclipse Platform Plug-ins and Fragments under the EPL-2.0
+      url: /projects/handbook/#legaldoc-plugins
+    - text: EPL-1.0 - `about.html` in plain HTML
+      url: epl-1-about.html
+    - text: EPL-1.0 - Third-Party Content `about.html` in plain HTML
+      url: epl-1-longabout.html
+    - text: EPL-1.0 - Legal Documentation for Eclipse Platform Plug-ins and Fragments under the EPL-2.0
+      url: /projects/handbook/#legaldoc-plugins
+---
+
+{{< pages/legal/about-file-templates >}}

content/legal/epl/faq/index.md

+---
+title: Eclipse Public License 1.0 (EPL) Frequently Asked Questions
+author: Mike Milinkovich
+keywords:
+  - epl
+  - cpl
+  - faq
+  - legal
+  - foundation
+  - eclipse
+  - license
+  - licenses
+related:
+  links:
+    - text: Eclipse Legal FAQ
+      url: /legal/faq
+    - text: Eclipse Software User Agreement
+      url: /legal/epl/notice
+---
+
+{{< pages/legal/epl-faq >}}

content/legal/epl/notice/index.md

+---
+title: Eclipse Foundation Software User Agreement
+author: Mike Milinkovich
+hide_page_title: true
+keywords:
+  - eclipse
+  - license
+  - user
+  - agreement
+  - sua
+related:
+  links:
+    - text: Software User Agreement in plain HTML
+      url: notice.html
+    - text: Software User Agreement in Java properties format
+      url: feature.properties.txt
+    - text: Guide to legal documents
+      url: http://www.eclipse.org/projects/handbook/#legaldoc
+---
+
+{{< pages/legal/inject-content >}}

content/legal/faq/index.md

+---
+title: "Eclipse Foundation Legal Frequently Asked Questions (FAQ)"
+author: Mike Milinkovich
+layout: single
+hide_page_title: true
+keywords:
+    - legal
+    - faq
+    - foundation
+---
+
+{{< pages/legal/inject-content >}}

content/legal/licenses/_index.md

+---
+title: "Third Party Content Licenses"
+author: Wayne Beaton
+keywords:
+    - legal
+    - privacy
+    - policy
+---
+
+{{< pages/legal/licenses >}}

content/legal/licenses/licenses.json

+{
+	"meta": {
+		"updated": "2023-07-13"
+	},
+	"approved": {
+		"0BSD": "BSD Zero Clause License",
+		"Adobe-Glyph": "Adobe Glyph List License",
+		"Apache-1.0": "Apache Software License 1.0",
+		"Apache-1.1": "Apache Software License 1.1",
+		"Apache-2.0": "Apache Software License 2.0",
+		"Artistic-2.0": "Artistic License 2.0",
+		"BlueOak-1.0.0": "Blue Oak Model License 1.0.0",
+		"BSL-1.0": "Boost Software License",
+		"BSD-2-Clause": "BSD 2-Clause “Simplified” License",
+		"BSD-2-Clause-FreeBSD": "BSD 2-Clause FreeBSD License",
+		"BSD-2-Clause-Views": "BSD 2-Clause with views sentence",
+		"BSD-3-Clause": "BSD 3-Clause “New” or “Revised” License",
+		"BSD-4-Clause": "BSD 4-Clause “Original” or “Old” License",
+		"CC-BY-2.5": "Creative Commons Attribution License 2.5",
+		"CC-BY-3.0": "Creative Commons Attribution 3.0 Unported",
+		"CC-BY-4.0": "Creative Commons Attribution 4.0 International",
+		"CC-BY-SA-3.0": "Creative Commons Attribution Share Alike 3.0 Unported",
+		"CC-BY-SA-4.0": "Creative Commons Attribution Share Alike 4.0 International",
+		"CC0-1.0": "Creative Commons Zero V1.0 Universal",
+		"CDDL-1.0": "Common Development and Distribution License (CDDL) Version 1.0",
+		"CDDL-1.1": "Common Development and Distribution License (CDDL) Version 1.1",
+		"CPL-1.0": "Common Public License Version 1.0",
+		"EPL-1.0": "Eclipse Public License, v1.0",
+		"EPL-2.0": "Eclipse Public License, v2.0",
+		"FTL" : "FreeType License",
+		"GFDL-1.3-only": "GNU Free Documentation License Version 1.3",
+		"IPL-1.0": "IBM Public License 1.0",
+		"ISC": "ISC License",
+		"LGPL-2.0-only": "GNU Library General Public License v2 only",
+		"LGPL-2.0-or-later": "GNU Library General Public License v2 or later",
+		"LGPL-2.1-only": "GNU Lesser General Public License v2.1 only",
+		"LGPL-2.1-or-later": "GNU Lesser General Public License v2.1 or later",
+		"LGPL-3.0-only": "GNU Lesser General Public License v3.0 only",
+		"LGPL-3.0-or-later": "GNU Lesser General Public License v3.0 or later",
+		"MIT": "MIT License",
+		"MIT-0": "MIT No Attribution",
+		"MPL-1.1": "Mozilla Public License Version 1.1",
+		"MPL-2.0": "Mozilla Public License Version 2.0",
+		"NTP": "NTP License",
+		"OpenSSL": "OpenSSL License",
+		"PHP-3.01": "PHP License v3.01",
+		"PostgreSQL": "PostgreSQL License",
+		"OFL-1.1": "SIL Open Font License 1.1",
+		"Unicode-TOU": "Unicode Terms of Use",
+		"Unicode-DFS-2015": "Unicode License Agreement – Data Files and Software (2015)",
+		"Unicode-DFS-2016": "Unicode License Agreement – Data Files and Software (2016)",
+		"UNLICENSE": "The Unlicense",
+		"UPL-1.0" : "Universal Permissive License v1.0",
+		"W3C": "W3C Software and Notice License (2002-12-31)",
+		"W3C-19980720": "W3C Software Notice and License (1998-07-20)",
+		"W3C-20150513": "W3C Software Notice and Document License (2015-05-13)",
+		"WTFPL": "Do What The Firetruck You Want To Public License",
+		"X11": "X11 License",
+		"Zlib": "Zlib License",
+		"ZPL-2.1" : "Zope Public License 2.1"
+	},
+	"valid": {
+		"EUPL-1.1": "European Union Public License 1.1",
+		"EUPL-1.2": "European Union Public License 1.2"
+	},
+	"restricted": {
+		"AGPL-1.0-only": "Affero General Public License v1.0 only",
+		"AGPL-1.0-or-later": "Affero General Public License v1.0 or later",
+		"AGPL-3.0-only": "GNU Affero General Public License v3.0 only",
+		"AGPL-3.0-or-later": "GNU Affero General Public License v3.0 or later",
+		"JSON": "JSON License"
+	}
+}

content/legal/logo-guidelines/index.md

+---
+title: "Eclipse Foundation Trademark Usage Policy"
+author: Mike Milinkovich
+hide_page_title: true
+keywords:
+    - certificate
+    - ECA
+    - contributor
+    - eclipse
+---
+
+{{< grid/div class="text-center" >}}
+
+# Eclipse Foundation Trademark Usage Policy
+
+of  
+Eclipse Foundation AISBL  
+a Belgian incorporated international not-for-profit association  
+Rond Point Schuman 11, Brussels 1040 Belgium  
+VAT BE / Enterprise number: 0760.624.114  
+RLE Brussels (French-speaking Enterprise Court)  
+
+and  
+
+Eclipse.org Foundation, Inc.  
+a Delaware incorporated 501(c)6 not-for-profit association  
+
+collectively, the “**Eclipse Group**”
+
+{{</ grid/div >}}
+
+Effective as of May 19, 2021
+
+## Purpose: { #purpose }
+
+This Policy (the “**Policy**”) defines the allowable use of names, marks and logos and related rights (referred to herein collectively as "**Trademarks**") owned by Eclipse.org Foundation, Inc. ("**Eclipse**") (such Trademarks, the “**Eclipse Trademarks**”). The Policy is intended to protect the goodwill associated with Eclipse Trademarks and to promote and improve the consistency of use of Eclipse Trademarks across all elements of the Eclipse Group community and otherwise. This is important, among other reasons, to demonstrate that Eclipse Group open source projects (“Eclipse Projects”) are part of a common community of developers, adopters and users, all associated with the highest levels of quality.
+
+Eclipse owns all Trademarks that are related to the business of the Eclipse Group, including the Trademarks related to Eclipse Projects (“**Eclipse Project Trademarks**”) and working groups and their specifications, if any (“**Eclipse WG Trademarks**”). A list of Eclipse Trademarks and any trademark usage guidelines implemented by Eclipse Foundation Working Groups (each, a “**WG**”) (e.g., Jakarta EE, Sparkplug, etc.) which should be read to supplement this Policy (with conflicts governed by this Policy) can be found at [https://www.eclipse.org/projects/tools/trademarks.php](/projects/tools/trademarks.php).
+
+The Eclipse Trademarks are symbols of the quality and community support that people have come to associate with the Eclipse Group. To ensure that the Eclipse Trademarks continue to serve these functions, we need to keep control over their use. People should be able to tell when something is from Eclipse or one of the Eclipse Projects or working groups. Also, Eclipse Trademarks should not be used in a way which tarnishes the reputation or image of Eclipse technology, Eclipse, the Eclipse Group, its projects, its working groups, or its Members.
+
+As discussed in this Policy, there are also specific requirements applicable to Eclipse Trademarks that are logos (“**Eclipse Logos**”), Eclipse Foundation “branded” Trademarks (some of which are Eclipse Logos) (“**Eclipse Foundation Trademarks**”), Eclipse Project Trademarks (some of which are Eclipse Logos), and Eclipse WG Trademarks (some of which are Eclipse Logos).
+
+As detailed below and except as provided herein, the use of any name, mark, or logo which may create confusion with, or falsely implies an endorsement, affiliation or relationship with Eclipse or the Eclipse Group, or is otherwise in violation of Eclipse’s rights or applicable law is a violation of this Policy.
+
+If you have any questions regarding this Policy, wish to report an infringement or improper use of Eclipse Trademarks, or wish to use an Eclipse Trademark in a way not explicitly provided for in this Policy, then contact us by sending an email to [**license@eclipse-foundation.org**](mailto:license@eclipse-foundation.org).
+
+We recognize that there may be certain circumstances where a “fair use” of an Eclipse Trademark may deviate from this Policy. Nothing in this Policy should be interpreted to interfere with the right to make such fair uses of Eclipse Trademarks as provided for under applicable law and all of the guidance in this Policy is subject to applicable law.
+
+## General Usage of Eclipse Logos { #general-usage-of-eclipse-logos }
+
+1. These requirements apply generally to the use of Eclipse Logos.
+  
+2. Eclipse-owned logos and related production specifications are available at [https://www.eclipse.org/org/artwork/](/org/artwork). The use of Eclipse-owned logos should follow these specifications and applicable guidelines. Eclipse logos include logos for 'Eclipse', 'Eclipse Foundation', 'EclipseCon', 'Eclipse Summit', 'Eclipse Foundation Member', 'Built on Eclipse', 'Eclipse Ready', 'Jakarta', 'Jakarta EE and any Eclipse Project Trademarks and Eclipse WG Trademarks which are logos. Eclipse Logos cannot be modified in any way without the advanced written permission (email is permissible) of Eclipse. Any Eclipse Project or working group that wishes to seek such permission may do so by sending an email to <license@eclipse-foundation.org>.
+  
+3. To ensure the consistency of our corporate brand identity, please see our [Brand Guidelines Handbook](/legal/documents/eclipse-foundation-branding-guidelines.pdf). This style guide outlines usage standards to ensure that the “Eclipse Foundation” logo is instantly and consistently recognizable however and wherever it is used by Foundation members and the community.
+
+## Proper Usage of Eclipse Foundation Trademarks { #proper-usage-of-eclipse-foundation-trademarks }
+
+These requirements apply to the use of any Eclipse Foundation Trademarks such as the Eclipse Foundation name and logo and the Eclipse Foundation Member logo. Use of the Eclipse Foundation Trademarks are restricted to identifying the Eclipse Foundation and its members. 'Eclipse' must always be capitalized, except when used as part of an Eclipse logo.
+
+Unless otherwise agreed to in advance in writing (which may be in email form) by Eclipse, the following restrictions apply to the use of Eclipse Foundation Trademarks:
+
+1. All of the guidance set out in Section 2 regarding Eclipse Logos apply to Eclipse Foundation Trademarks that are logos.
+  
+2. You may not incorporate an Eclipse Foundation Trademark into the name of your company or software product or service name.
+  
+3. You may not include an Eclipse Foundation Trademark in the name of a publication, certification program, domain name or book.
+  
+4. Only Eclipse Projects are authorized to develop or maintain software packages that use Eclipse Foundation namespaces such as 'org.eclipse' in their namespace. An important use of an Eclipse Trademark is the 'org.eclipse' string used on all namespaces for Eclipse Projects. This naming convention is used to identify code that has been developed as part of an Eclipse Project.
+  
+5. The 'Eclipse Foundation Member' Trademark is meant to identify those organizations and individuals that are members of the Eclipse Group. Only current members of the Eclipse Group are authorized to use this Eclipse Trademark.
+
+## Proper Usage of Eclipse Project Trademarks { #proper-usage-of-eclipse-project-trademarks }
+
+1. All of the guidance set out in Section 2 regarding Eclipse Logos apply to Eclipse Project Trademarks that are logos.
+  
+2. The Eclipse Foundation claims the names and logos of all Eclipse Projects as trademarks.
+  
+3. While every project manages its own development within the broader [Eclipse Development Process](/projects/dev_process/development_process.php), Eclipse holds the Eclipse Project Trademarks for the benefit of the Eclipse community as a whole. The Eclipse Project Naming Policy allows for Eclipse Projects to have a descriptive name, an optional nickname and an acronym. These names (e.g. Theia), and acronyms (e.g. CDT), can become effective identifiers of certain technologies, and therefore it is important to establish maintain proper usage of such identifies. All identifiers used by Eclipse Projects (including project names, nicknames, logos, and acronyms) are the intellectual property of the Eclipse Foundation, and shall constitute Eclipse Trademarks and must be treated as such.
+  
+4. For clarity, projects are not required to include 'Eclipse' or use the Eclipse logo in their project logos. (Please see proper notice and attribution below.)
+  
+5. All Eclipse Projects must be identified as being Eclipse projects. Therefore, when referencing an Eclipse Project, we ask that both the first and the most prominent reference to the project on each page is identified as "Eclipse \[project name\]" (e.g., Eclipse Graphical Modeling Framework (GMF) or in the case of a project name that already includes Eclipse, Eclipse Communication Framework (ECF)). Subsequent references may drop the Eclipse identifier.
+  
+6. You may not incorporate the name of an Eclipse Project Trademark into the name of your company or software product name. If you have a software product that works with an Eclipse Project, you may only use the following phrases: '<product name> for <Eclipse project name>' or '<product name>, <Eclipse project name> Edition'.
+  
+7. You are required to request permission to include an Eclipse Project Trademark in the name of a publication, certification program, domain name or book. At a minimum, it will be required that a) the appropriate ™ or ® symbol is associated with the Eclipse Project Trademark and appropriate attribution as discussed below, b) the Eclipse Project name is not concatenated with another word, e.g. TheiaPortal, and c) the usage does not imply or infer that the publication, domain name or book is supported or authorized by Eclipse, the Eclipse Group, or any Eclipse Project. If you wish to seek such permission, you may do so by sending an email, prior to any use of an Eclipse Project Trademark, to [license@eclipse-foundation.org](mailto:license@eclipse-foundation.org), together with a presentation of the projected use of the Eclipse Project Trademark.
+
+## Proper Usage of Eclipse WG Trademarks { #proper-usage-of-eclipse-wg-trademarks }
+
+All of the guidance set out in Section 2 regarding Eclipse Logos apply to Eclipse WG Trademarks that are logos.
+
+The Eclipse Foundation claims the names and logos of all Eclipse Foundation working groups as trademarks. Some Eclipse Foundation working groups produce specifications. The Eclipse Foundation claims the names and logos of each specification as trademarks.
+
+The identifiers of Eclipse WGs are Eclipse WG Trademarks and the intellectual property of Eclipse and must be identified as such in all uses. (Please see proper notice and attribution below.) The use of Eclipse WG Trademarks is restricted to identifying the applicable WG or their deliverables, which may include specifications, as applicable. No other uses of Eclipse WG Trademarks are permitted unless authorized in advance in writing by Eclipse, or in adherence with any supplemental trademark usage guidelines made available at [https://www.eclipse.org/projects/tools/trademarks.php](/projects/tools/trademarks.php). Any organization wishing to seek such authorization may do so by sending an email to [license@eclipse-foundation.org](mailto:license@eclipse-foundation.org).
+
+Each WG may, at its discretion, develop guidelines for use of the Eclipse WG Trademarks by third parties, provided such guidelines are consistent with this Policy. These WG-specific guidelines will be made available at [https://www.eclipse.org/projects/tools/trademarks.php](/projects/tools/trademarks.php).
+
+One is not permitted to create any trademarks which may create confusion with an Eclipse WG Trademark or suggest endorsement, association or affiliation with a WG or Eclipse Trademark without prior written approval of Eclipse, which, in the event of a request, will consult with the Steering Committee of the relevant Working Group. Any organization wishing to seek permission to create such a Trademark may do so by sending an email to [license@eclipse-foundation.org](mailto:license@eclipse-foundation.org).
+
+Use of any namespaces created by a WG including but not limited to ‘jakarta’, 'org.locationtech' or 'org.polarsys' is not permitted by this Policy unless authorized in advance in writing by Eclipse.
+
+## Proper Notice and Attribution { #proper-notice-and-attribution }
+
+The appropriate trademark symbol (i.e. ™ or ®) must appear at both the first and most prominent use of Eclipse Trademarks, and with all occurrences of the Eclipse Trademarks.
+
+When you use an Eclipse Trademark you must include a statement attributing the Trademark to the Eclipse Foundation, Inc., by the use of the following sentence:"'\[e.g. Eclipse', 'Built on Eclipse' and 'Eclipse Ready', CDT, Theia\] are trademarks of Eclipse Foundation, Inc."

content/legal/non-code-licenses/index.md

+---
+title: "Approved Licenses for Non-Code, Example, and Other Content"
+author: Mike Milinkovich
+keywords:
+    - license
+    - content
+related:
+  links:
+    - text: Legal resources
+      url: /legal
+    - text: Guide to legal documents
+      url: /projects/handbook#legaldoc
+---
+
+December 6, 2017
+
+The following licenses have been approved by the Board of Directors for use with Non-Code Content, as that term is defined in the [Eclipse.org Terms of Use](/legal/terms-of-use/).
+
+1. the [Eclipse Public License 2.0](/legal/epl-2.0/),
+2. the [Creative Commons Attribution-Share Alike 3.0 (Unported) license](http://creativecommons.org/licenses/by-sa/3.0/),
+3. the [Creative Commons Attribution 3.0 (Unported) License](http://creativecommons.org/licenses/by/3.0/),
+4. the [Creative Commons Attribution-Share Alike 4.0 (International) License](http://creativecommons.org/licenses/by-sa/4.0/), or
+5. the [Creative Commons Attribution 4.0 (International) License](http://creativecommons.org/licenses/by/4.0/).
+
+In addition, the following licenses have been approved by the Board of Directors for use with example code or build scripts and artifacts within Eclipse projects.
+
+1. the [Eclipse Public License 2.0](/legal/epl-2.0/),
+2. the [Eclipse Distribution License](/org/documents/edl-v10.php) (EDL).
+
+For additional details on the definition of example code or build scripts and artifacts and how to seek PMC approval for using the EDL, please refer to the [policy document](/org/documents/Licensing_Example_Code.pdf).

content/legal/open-vsx-registry-faq/index.md

+---
+title: "Eclipse Foundation Open VSX Registry Frequently Asked Questions (FAQ)"
+tags: ["frequently asked questions", "faq", "open vsx", "open vsx registry", "extensions", "theia", "vscodium", "licensing"]
+---
+
+Last Updated: 8 May 2024
+
+{{< table_of_contents >}}
+
+## What is Open VSX Registry?
+
+The [Open VSX Registry](https://open-vsx.org/) offers a community driven, fully
+open platform for publishing and consuming VS Code extensions. The Registry is
+built on [Eclipse Open VSX](https://github.com/eclipse/openvsx), which is an
+open source project hosted at the Eclipse Foundation.
+
+Open VSX is integrated into multiple software applications that support VS Code
+extensions, including [Eclipse Theia IDE](https://theia-ide.org/). There is
+strong demand for a fully open alternative to the Visual Studio Marketplace,
+and with hundreds of great extensions already available, it is the intent of
+the Eclipse Foundation to enable continued and accelerated growth.
+
+## Eclipse Foundation Management
+
+The Open VSX Registry is managed by the Eclipse Foundation's [Open VSX Working Group](https://open-vsx.org/members). 
+Through this management, all stakeholders can benefit from vendor-neutral, open
+source operation and governance.
+
+## What do I need to know as a Consumer of Open VSX?
+
+If you are consuming extensions in applications that use the Open VSX Registry
+(e.g. in Gitpod, VSCodium or Eclipse Theia IDE) there will be no usage impact.
+You can expect a seamless experience while we work to add more extensions,
+raise the visibility of extensions, and increase the number of consumers to
+ensure the long-term viability and vibrancy of the registry.
+
+## What do I Need to Know as a Publisher to Open VSX?
+
+All publishers are required to:
+
+- Sign the [Eclipse Foundation Open VSX Publisher Agreement](/legal/documents/eclipse-openvsx-publisher-agreement.pdf); and
+- Ensure all extensions are published under a license.
+
+## Why do I need to Sign a Publisher Agreement?
+
+The purpose of the Eclipse Foundation Open VSX Publisher Agreement is to
+provide a written record that you have the authority to enter into and agree to
+the terms outlined in the agreement to publish extensions under a license to
+the Open VSX Registry.
+
+## How Do I Sign the Publisher Agreement?
+
+Publishers can sign the Eclipse Foundation Open VSX Publisher Agreement via
+their profile page on Open VSX Registry.
+
+The following steps are required in order to sign the agreement:
+
+- Create an account at [eclipse.org](https://eclipse.org) and include your GitHub username in the account information;
+- Log in at [open-vsx.org](https://open-vsx.org) by authorising the service with your GitHub account;
+- Connect Open VSX with your Eclipse account on the [Open VSX account profile](https://open-vsx.org/user-settings/profile) (click on "Log in with Eclipse"); and
+- Access and sign the *Eclipse Foundation Open VSX Publisher Agreement* from the [Open VSX account profile](https://open-vsx.org/user-settings/profile) page.
+
+## What Happens if I do not Sign the Publisher Agreement?
+
+If you choose not to sign the Eclipse Foundation Open VSX Publisher Agreement,
+you will not be able to publish extensions.
+
+## Do I Need to Sign the Eclipse Contributor Agreement in order to Publish Open VSX Extensions?
+
+No, there is no requirement to sign the [Eclipse Contributor Agreement](/legal/eca/).
+You do, however, need to sign the Eclipse Foundation Open VSX Publisher
+Agreement.
+
+## Can I sign the Publisher Agreement on behalf of a Service Account?
+
+Yes, the Publisher Agreement accounts for this. If you are able to sign the
+Publisher Agreement based on a service account and related service GitHub ID,
+coupled with the ability to enter into the Publisher Agreement (necessary
+rights to do so based on the terms of the Publisher Agreement), then you may do
+so.
+
+Please note if you wish to publish as an individual at a later time, you will
+need to create an individual account against a personal GitHub ID and sign the
+Publisher Agreement with that ID as an individual.
+
+## Licensing 
+
+### Does my Extension have to be licensed?
+
+Yes, all extensions must be licensed. Your extension's license should be
+expressed by including a license expression in the
+[package.json](https://docs.npmjs.com/cli/v6/configuring-npm/package-json#license)
+manifest. If you have questions about what license is best for you, we
+recommend that you read about open source licenses at the [Open Source Initiative](https://opensource.org/licenses).
+
+### Must I Offer my Extension under an Open Source License?
+
+No, you may use a license that is not recognized as an open source license by
+the [Open Source Initiative](https://opensource.org/licenses).
+
+### Must the License I Publish my Extension under Match the Source Code License?
+
+No. You can have one license for your source code, e.g. in your GitHub
+repository, and a different license specified in your
+[package.json](https://docs.npmjs.com/cli/v6/configuring-npm/package-json#license)
+manifest for publishing.
+
+### How do I know what License an Extension is Published under?
+
+The applicable licenses of Open VSX Registry extensions are listed on the
+respective Overview page in the registry and are included in the JSON metadata
+of each extension. This may be an explicit statement regarding the license or a
+link to a separate license file.
+
+## How do I Publish Extensions?
+
+The publishing process is described in the [Open VSX Wiki](https://github.com/eclipse/openvsx/wiki/Publishing-Extensions#how-to-publish-an-extension).
+
+## How do I Unpublish an Extension, or a Specific Version of an Extension?
+
+Please file an [issue](https://github.com/eclipse/open-vsx.org/issues) with the
+project and a team member will provide this assistance.
+
+## Are Open VSX Registry Extensions Royalty Free?
+
+The Open VSX Registry does not collect fees to publish or consume extensions.
+All extensions in the Open VSX Registry are made available without fee, subject
+to the terms of the respective licenses.
+
+## How Much is the Open VSX Account Fee?
+
+There are no fees associated with publishing or consuming content from the Open
+VSX Registry.
+
+## How do I Opt Out of Auto-Updates?
+
+Auto-update is a feature of VS Code, Eclipse Theia IDE (or other applications
+consuming extensions). Please configure the client application accordingly if
+you wish to disable auto-updates of extensions. Open VSX Registry itself does
+not provide any auto-update facility.
+
+## How do I get Technical Support?
+
+The Open VSX Registry and the Eclipse Foundation cannot provide support for
+extensions that you have installed from the registry. The individual publishers
+are responsible for providing support for their own offerings. Most extensions
+provide links for their source code repositories and/or to report bugs. Or you
+can submit a rating and a review using the 'Write a Review' link on the
+extension's 'Ratings & Reviews' page.
+
+Users can ask questions, search for answers, enter issues and feature requests
+for the Open VSX Registry itself in the project's GitHub [repository](https://github.com/eclipse/open-vsx.org/issues).
+
+## What do I do about an Extension that Appears to be in Violation of the Publisher's Agreement?
+
+The page for each extension has a 'Report Abuse' `mailto:` for this purpose.
+These reports are investigated by the project team. You will get a response
+once the investigation completes.
+
+## How do I get help with the Publisher Agreement?
+
+Questions related to the Eclipse Foundation Open VSX Publisher Agreement,
+licenses, privacy, etc. should be sent to
+[license@eclipse-foundation.org](mailto:license@eclipse-foundation.org).
+

content/legal/privacy/index.md

+---
+title: Eclipse Foundation Website Privacy Policy
+author: Mike Milinkovich
+keywords:
+    - legal
+    - foundation
+    - guidelines
+    - trademarks
+related:
+  links:
+    - text: Legal resources
+      url: /legal
+    - text: Guide to legal documents
+      url: /projects/handbook#legaldoc
+---
+
+{{< pages/legal/privacy >}}

content/legal/tck/index.md

+---
+title: Eclipse Foundation Technology Compatibility Kit License
+author: Eclipse Foundation
+keywords:
+    - legal
+    - Technology Compatibility Kit License
+---
+
+**Do not modify the text of this license.**
+
+Specification project committers: include this text _verbatim_ with your TCK.
+
+An AsciiDoc version of this file is available [here](/legal/adoc/eftl-1.1.adoc). Plain HTML is [here](tck.html).
+
+The Eclipse Foundation Specification License is [here](/legal/efsl/).
+
+↓ The actual licence text starts below this line. ↓
+
+***
+
+{{< pages/legal/inject-content >}}

content/legal/terms-of-use/index.md

+---
+title: Eclipse.org Terms of Use
+author: Mike Milinkovich
+keywords:
+    - terms
+    - legal
+    - website
+    - terms of use
+---
+
+15 February 2024
+
+## Terms and Conditions of Use for the Eclipse Foundation Website and Related Services
+
+As used herein, the term "you" or "your" means the individual accessing any Eclipse Foundation website or online resource that contains a reference or link to these Terms of Use, including in the first place at [https://www.eclipse.org/](/) as well as those websites of its industry collaborations and any other website of the Eclipse Group ("Website"), as well as any person or entity which has granted to such individual the authority to enter into this agreement on its behalf. By accessing, browsing, or using this Website, you acknowledge that you have read, understand, and agree to be bound by these terms.
+
+This Website and related services are made available by the Eclipse Foundation AISBL , and/or its affiliated Eclipse Foundation organisations, including Eclipse Foundation Canada, Eclipse.org Foundation, Inc, and Eclipse Foundation Europe GmbH (collectively, "Eclipse Foundation"). All software, documentation, information and/or other materials provided on and through this Website ("Content") and all of the related services offered by the Eclipse Foundation may be used solely under the following terms and conditions ("Terms of Use").
+
+This Website and related services are not meant for or targeted to anyone under the age of 16. You must be at least 16 years of age, or the age of consent under your location’s applicable laws for using websites intended for adults if your location uses a different age, to use the Website or related services; otherwise, your parent or guardian must review and accept these Terms on your behalf. To learn how Eclipse Foundation collects, processes, and shares personal information, please consult Eclipse Foundation’s [Website Privacy Policy](/legal/privacy).
+
+This Website may contain other proprietary notices and copyright information, the terms of which must be observed and followed. The Content on this Website may contain technical inaccuracies or typographical errors and may be changed or updated without notice. The Eclipse Foundation may also make improvements and/or changes to the Content at any time without notice.
+
+Neither the Eclipse Foundation nor its members ("Members") assume any responsibility regarding the accuracy of the Content and use of the Content is at your own risk. Neither the Eclipse Foundation nor its Members provide any assurances that any reported problems with any Content will be resolved. Except as otherwise expressly stated herein or in another applicable licence, by providing the Content, neither the Eclipse Foundation nor the Members grant any licences to any copyrights, patents, or any other intellectual property rights in the Content.
+
+The Eclipse Foundation and its Members do not want to receive confidential information from you through this Website and related services. Please note that, with the exception of the personal information submitted by you in the process of either creating or updating the personal information associated with your Eclipse account or when executing an agreement with us such as the Eclipse Contribution Agreement, any information or material submitted through the Website will be deemed NOT to be confidential and will be publicly available.
+
+You are prohibited from posting, transmitting, or storing to or from this Website or to any service offered by the Eclipse Foundation (each referred to as a "Submission") any unlawful, threatening, libellous, defamatory, obscene, scandalous, inflammatory, pornographic, or profane material, or any other material that could give rise to any civil or criminal liability under the law. Further, all Submissions made by you to the Website must be in conformance to the Eclipse Community Code of Conduct, which may be found here: [https://www.eclipse.org/org/documents/Community_Code_of_Conduct.php](/org/documents/Community_Code_of_Conduct.php) and the Eclipse Foundation Communication Channel Guidelines which may be found here: [https://www.eclipse.org/org/documents/communication-channel-guidelines/](/org/documents/communication-channel-guidelines/) .
+
+Should the Eclipse Foundation determine that a Submission violates these Terms of Use or should we be informed thereof by a third party, the Eclipse Foundation reserves the right to remove any such Submissions made by you to the Website at its sole discretion.
+
+If your Submission has been removed for violation of these Terms of Use or for violation of any applicable law, we will inform you of the reasons thereof. Should you disagree with us, you may send an e-mail to [transparency@eclipse-foundation.org](mailto:transparency@eclipse-foundation.org) within six months from the date we informed you of the removal of your Submission, stating the reasons why, in your opinion, your Submission should be reinstated. Your complaint will be logged in our systems, and we will review it and respond to you without undue delay.
+
+If you believe that Content residing or accessible on or through this Website or any User Data Services ("UDS") infringes a copyright, please send a notice of copyright infringement to our designated agent pursuant to the procedures set forth here: [https://www.eclipse.org/legal/copyright](/legal/copyright)
+
+If you repeatedly provide manifestly illegal Content or if you repeatedly issue infringement notices, or if you frequently send e-mails about alleged infringement Content that are manifestly unfounded, we will issue a warning to you, and subsequently we may bar you, for a reasonable period of time, from using our Website or UDS, or from issuing infringement notices. Examples of facts and circumstances we take into account before we decide to bar you as mentioned are the gravity and/or frequency of the misuses, including the nature of illegal content and its consequence.
+
+Should you disagree with our response or our reaction to the complaint you addressed to us via e-mail or via [https://www.eclipse.org/legal/copyright](/legal/copyright), you may refer the matter to a certified out-of-court settlement body that is competent to address content moderating issues. Please note that no such out-of-court settlement bodies have been certified by the competent authorities yet. We will update these Terms of Use once more information becomes available.
+
+### User Data Services ("UDS")
+
+As a service to you, Eclipse.org services or Eclipse software may offer functionality whereby you can store or share certain information on Eclipse Foundation’s computer systems, so that it is accessible to you from various devices that you use. Examples include, but are not limited to, Eclipse IoT sandbox servers and the User Storage Service. PLEASE BE AWARE THAT ALL INFORMATION THAT YOU STORE OR SHARE WITH ECLIPSE WILL BE PUBLICLY ACCESSIBLE ON THE INTERNET IN UNENCRYPTED FORM AND WITHOUT ANY ACCESS RESTRICTIONS. Do not store or share passwords, any personally identifiable information ("PII"), any confidential business information, or anything else that you do not want to be generally and publicly available. By using this functionality, any information that you store or share (the "Stored Information") will be subject to the [CC0 1.0 Creative Commons](https://creativecommons.org/publicdomain/zero/1.0/legalcode) licence, where, for purposes of that licence, the Stored Information shall constitute the "Work" and you shall be the "Affirmer". What that means is that anybody who accesses your information on the Internet has a worldwide, unrestricted, royalty free, irrevocable, perpetual, non-exclusive licence to use, make, reproduce, prepare derivative works of, publicly display, publicly perform, transmit, sell, distribute, sublicense or otherwise transfer the Stored Information without any obligation to you, including any obligation of attribution.
+
+The Eclipse Foundation reserves the right to discontinue these services at any time or to remove any specific Stored Information from owned or controlled computer systems at any time, and Eclipse Foundation does not commit to making Stored Information available at all times in the future.
+
+### Licenses
+
+Except for Content available through the UDS, and except as otherwise stated herein, the Content provided on this Website is provided under the terms and conditions of the [Eclipse Foundation Software User Agreement](/legal/epl/notice/) and those additional terms, conditions and notices referenced therein.
+
+If Content is licensed to you under the terms and conditions of a version of the Eclipse Public License ("[EPL](/legal/epl-2.0/)"), with respect to such Content, the term "Contributions" as used herein shall have the meaning provided in the EPL, and any such Contributions uploaded, submitted, or otherwise made available by you to the Eclipse Foundation and/or the Members and/or users of this Website shall be governed by the terms and conditions of the EPL and can be made available to others under the terms of the EPL.
+
+If Content is licensed to you under licence terms and conditions other than the EPL ("Other Licence") with respect to such Content the term "Contributions" as used herein shall mean any modifications, enhancements and/or other code and/or documentation related to such Content uploaded, submitted, or otherwise made available by you to the Eclipse Foundation and/or the Members and/or users of this Website, and such Contributions shall be subject to and governed by the terms and conditions of the Other License. In addition, with regard to such Contributions, you agree to provide the Contributions under the terms and conditions of the Other License, provided however that the Eclipse Foundation shall have the right to reject any Contributions if the acceptance by the Eclipse Foundation would be in any way inconsistent with the Eclipse Foundation's Intellectual Property Policy.
+
+In addition to the licences granted above, you grant a non-exclusive, worldwide, perpetual, royalty-free licence of all necessary rights under your copyright in and to your Contributions (the "Specification Grant"): (a) for the Eclipse Foundation (and its contributors solely as a part of Eclipse Foundation projects) to create, reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense specifications subject to the terms of the then-current [Eclipse Foundation Specification License](/legal/efsl/), based on or derived from the Specification Content (as defined below) and (b) for recipients of such specifications to create, reproduce, and distribute implementations thereof based on the portion of your Contributions or material derived from them in the specifications, subject to the terms of the then-current [Eclipse Foundation Specification License](/legal/efsl/).
+
+"Specification Content" is the collection of interface definitions for the application or user interfaces ("Interfaces") provided by the work to which your Contribution was made, descriptions of the structure and semantic behaviour of those Interfaces, and data formats and protocols associated with those Interfaces, all of which as are reasonably necessary to enable the development of independent implementations of those Interfaces. For the sake of clarity, Specification Content does not include implementation detail of how the Eclipse project code or your Contribution implements the Interfaces in the Specification and the Specification Grant provided above would not cover such additional material.
+
+To the extent you submit or otherwise make available to an Eclipse Foundation Specification Project (as that term is defined by the Intellectual Property Policy) any ideas, concepts, methods or other information, you agree that you will not assert, based on such submissions, any intellectual property rights that are essential to any implementation of the submission, against the Eclipse Foundation, its contributors, or its licensees, with respect to any implementation of such Specification (as that term is defined by the [Eclipse Foundation Specification Process](https://www.eclipse.org/projects/efsp/)). To further clarify, such submissions include, but are not limited to, submissions made to any public communications channel such as an email list, forum, communication channel, or issue.
+
+To the extent you wish to upload, submit, or otherwise make Non-Code Content (as defined below) available to the Eclipse Foundation and/or the Members and/or users of this Website, you may make that material available under the terms and conditions of the EPL or any other licence stipulated for that purpose at [Eclipse Foundation Legal Resources](/legal/). Non-Code Content is Content for which you own or control all rights, and which is not program code intended to be submitted to a Project or Eclipse Industry Collaboration (or documentation related to such activities) and which is not Stored Information. For example, Non-Code Content would include white papers, dissertations, articles or other literary works, presentations, encyclopaedias, anthologies, wikis, blogs, diagrams, drawings, sketches, photos or other images, audio Content, video Content, and audiovisual materials.
+
+For all other software, information and other material including, without limitation, ideas, concepts, know-how and techniques, uploaded, submitted or otherwise made available to the Eclipse Foundation, the Members, and/or users of this Website, (collectively "Material"), if the paragraphs above are inapplicable, and if the Material is not Stored Information, you grant (or warrant that the owner of such rights has expressly granted) a licence under either the applicable Project License(s) (as that term is defined in the Eclipse Intellectual Property Policy), or, if no such Project License(s) is applicable, you grant (or warrant that the owner of such rights has expressly granted) the Eclipse Foundation and the users of this Website a worldwide, unrestricted, royalty free, fully paid up, irrevocable, perpetual, non-exclusive licence to use, make, reproduce, prepare derivative works of, publicly display, publicly perform, transmit, sell, distribute, sublicense or otherwise transfer such Materials, and/or derivative works thereof, and authorise third parties to do any, some or all of the foregoing including, but not limited to, sublicensing others to do any some or all of the foregoing indefinitely.
+
+You represent and warrant that to your knowledge, you have sufficient rights in the Materials to grant the foregoing rights and licences.
+
+All logos and trademarks contained on this Website are and remain the property of their respective owners. No licences or other rights in or to such logos and/or trademarks are granted to you.
+
+The [Eclipse Foundation Website Privacy Policy](/legal/privacy/) provides more information about how we process your personal data.
+
+### Disclaimers
+
+The Eclipse Foundation and the Members make no representations whatsoever about any other Website that you may access through this Website. When you access a non-Eclipse Foundation Website, even one that may contain the organisation’s name or mark, please understand that it is independent from the Eclipse Foundation, and that the Eclipse Foundation and the Members have no control over the Content on such Website. In addition, a link to a non-Eclipse Foundation Website does not mean that the Eclipse Foundation or the Members endorse or accept any responsibility for the Content, or the use, of such Website. It is up to you to take precautions to ensure that whatever you select for your use is free of such items as viruses, worms, Trojan horses, and other items of a destructive nature.
+
+IN NO EVENT WILL THE ECLIPSE FOUNDATION AND/OR THE MEMBERS BE LIABLE TO YOU (AN INDIVIDUAL OR ENTITY) OR ANY OTHER INDIVIDUAL OR ENTITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, SPECIAL OR CONSEQUENTIAL DAMAGES RELATED TO ANY USE OF THE WEBSITE, THE CONTENT, STORED INFORMATION, OR ANY OTHER LINKED WEBSITE, INCLUDING, WITHOUT LIMITATION, ANY LOST PROFITS, LOST SALES, LOST REVENUE, LOSS OF GOODWILL, BUSINESS INTERRUPTION, LOSS OF PROGRAMS OR OTHER DATA ON YOUR OR OUR INFORMATION HANDLING SYSTEMS OR OTHERWISE, EVEN IF THE ECLIPSE FOUNDATION OR THE MEMBERS ARE EXPRESSLY ADVISED OR AWARE OF THE POSSIBILITY OF SUCH DAMAGES OR LOSSES.
+
+ALL CONTENT IS PROVIDED BY THE ECLIPSE FOUNDATION AND/OR THE MEMBERS ON AN "AS IS" BASIS ONLY. THE ECLIPSE FOUNDATION AND THE MEMBERS PROVIDE NO REPRESENTATIONS, CONDITIONS AND/OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY AND NONINFRINGEMENT. THE ECLIPSE FOUNDATION MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE SECURITY OF ANY INFORMATION OR CONTENT STORED WITH THE ECLIPSE FOUNDATION.
+
+The Eclipse Foundation and the Members reserve the right to investigate complaints or reported violations of these Terms of Use and to take any action they deem appropriate including, without limitation, reporting any suspected unlawful activity to law enforcement officials, regulators, or other third parties and disclosing any information necessary or appropriate to such persons or entities relating to user profiles, e-mail addresses, usage history, posted materials, IP addresses, and traffic information.
+
+The Eclipse Foundation and the Members reserve the right to seek all remedies available at law and in equity for violations of these Terms of Use, including but not limited to the right to block access from a particular Internet address to this Website.

content/legal/trademarks/index.md

+---
+title: Eclipse Foundation Trademarks
+author: Wayne Beaton
+keywords:
+    - legal
+    - Trademarks
+---
+
+The names and logos of all open source projects, working groups, specifications, and all downloadable software products, are trademarks of the Eclipse Foundation. In addition the Eclipse Foundation logo is a trademark of the Eclipse Foundation.
+
+This document captures a list of trademarks claimed by the Eclipse Foundation.
+
+## Trademark Use { #use }
+
+The [Eclipse Foundation Trademark Usage Guidelines](/legal/logo-guidelines) defines the allowable use of Eclipse Foundation names, marks and logos.
+
+Supplemental guidelines:
+
+- [Jakarta EE Trademark Guidelines](https://jakarta.ee/legal/trademark_guidelines/)
+
+## Trademark Disclaimers { #attribution }
+
+Content on this web site, including the names listed on this page, may make reference to the trademarks in the following list. We disclaim any claim to trademark rights in their usage.
+
+- Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.
+- Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
+- UNIX is a registered trademark of The Open Group in the United States and other countries.
+- Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
+- Android is a trademark of Google Inc.
+- Other company, product, and service names may be trademarks or service marks of others.
+
+{{< pages/legal/trademarks-list >}}