Eclipse Foundation Legal Resources on Eclipse Foundation

About File Templates

webdev@eclipse-foundation.org (Wayne Beaton) — Mon, 01 Jan 0001 00:00:00 +0000

Abouts contain legal documentation and are maintained in the source code repository and subsequently included in builds in Eclipse Platform Plug-in and Fragments and other directories. They usually contain information about licensing and sometimes also information about any use of cryptography. By convention, every Eclipse Platform Plug-in and Fragment usually has an About.

About files are generally only applicable for content that that is delivered as Eclipse Platform Plug-ins and Fragments. For more information, please see The Eclipse Project Handbook

Approved Licenses for Non-Code Content

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

This document lists the licenses approved by the Board of Directors for use for Non-Code Content (as that term is defined in the Eclipse.org Terms of Use). They are:

Eclipse Public License 1.0

Approved Licenses for Non-Code, Example, and Other Content

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

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.

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.

Committer Due Diligence Guidelines

webdev@eclipse-foundation.org (Wayne Beaton) — Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Eclipse Committers play a very important role in the operation of the Eclipse Foundation open source projects. This document outlines the responsibilities and explains some of the basic concepts Eclipse Committers need to understand in their role as a committer. If you are an Eclipse Committer, should you have any questions after reading this document, your questions should be submitted to your Project Management Committee (PMC) or the Eclipse Management Organization (EMO).

Copyright Agent

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

We respect the intellectual property rights of others, and require that the people who use the Site do the same. We also maintain a policy under which the Web Site use privileges of users who are repeat infringers of intellectual property rights are terminated in appropriate circumstances. If you believe that your work has been copied in a way that constitutes copyright infringement, please forward the following information to Eclipse’s Copyright Agent, designated as such pursuant to the Digital Millennium Copyright Act, 17 U.S.C. § 512(c)(2), named below:

Developer Certificate of Origin

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

Eclipse Foundation Legal Frequently Asked Questions (FAQ)

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

Eclipse Foundation Open VSX Registry Frequently Asked Questions (FAQ)

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

Last Updated: 8 May 2024

What is Open VSX Registry?

The Open VSX Registry offers a community driven, fully open platform for publishing and consuming VS Code extensions. The Registry is built on Eclipse Open VSX, which is an open source project hosted at the Eclipse Foundation.

Eclipse Foundation Quality Verification Suite License - v 1.0

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

Redistribution and use of the Quality Verification Suite accompanying this license (the "QVS") in binary form is permitted subject to the following rules and conditions:

Use of the QVS and its documentation is permitted by Eclipse solely for the purpose of testing an implementation (the "Product") to determine if it meets the requirements of a quality verification suite (the "Suite") made available by Eclipse.
No modifications to the QVS in binary form are permitted, except as expressly permitted by the QVS and its documentation. The source code for the QVS accompanying this license is available from Eclipse under separate terms.
Redistribution of the QVS in binary form must be accompanied with, and be made pursuant to the terms of this Eclipse Foundation Quality Verification Suite License and must include the text of this License in whole, including the copyright notice above, this list of conditions and the following disclaimers in the documentation and/or other materials provided with the distribution.
A Product will be deemed to be "verified" by the QVS if it fully and completely meets and satisfies all requirements of the QVS.
Before any claim of quality verification (or any other claim suggesting quality verification) is made based on the QVS, the testing party must:

use the QVS to determine that the Product fully and completely meets and satisfies all requirements of the QVS; and
make QVS test results showing full and complete satisfaction of all requirements of the QVS publicly available on the testing party's website and send a link to such test results to Eclipse at qvs@eclipse.org.

The QVS test results must be continuously available on the testing party's website for at least as long as the testing party makes any representation or claim that the Product has been quality verified by the QVS.
The QVS may not be used as a basis for any statements of partial verification. The QVS may only be used as a basis for true, factual statements of full quality verification of Products that fully meet and satisfy all requirements of the QVS.
Nothing in this license is intended to grant any license to use any of the names, marks or logos associated with the QVS, Eclipse, or Eclipse's contributors or licensors. No such name, mark or logo may be used to endorse or promote products tested with the QVS, unless with the specific prior written permission of the rightholders. Nor may any such name, mark or logo be used in connection with any verification of a Product except as permitted in the QVS Guidelines (https://adoptium.net/qvs-policy). A determination that a Product has been quality verified by the QVS does not, in itself, give rise to the right to use any such name, mark or logo. Any use of any Eclipse Foundation names, marks, or logos must be in accordance with our Trademark Usage Policy.
Upon the request of Eclipse, any user of the QVS will remove and delete any statements of quality verification (or any other claim suggesting quality verification) which Eclipse reasonably determines to be false or misleading or in violation of the terms of this license.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON- INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER THE COPYRIGHT OWNER OR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Eclipse Foundation Software User Agreement

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

Eclipse Foundation Specification License

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

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. Plain HTML is here.

The Eclipse Foundation TCK License is here.

↓ The actual licence text starts below this line. ↓

Eclipse Foundation Specification License

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

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. Plain HTML is here.

The Eclipse Foundation Specification License version 1.1 is available here.

The Eclipse Foundation TCK License is here.

↓ The actual licence text starts below this line. ↓

Eclipse Foundation Technology Compatibility Kit License

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 01 Jan 0001 00:00:00 +0000

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. Plain HTML is here.

The Eclipse Foundation Specification License is here.

↓ The actual licence text starts below this line. ↓

Eclipse Foundation Trademark Usage Policy

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

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”

Effective as of May 19, 2021

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 Foundation Trademarks

webdev@eclipse-foundation.org (Wayne Beaton) — Mon, 01 Jan 0001 00:00:00 +0000

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

The Eclipse Foundation Trademark Usage Guidelines defines the allowable use of Eclipse Foundation names, marks and logos.

Supplemental guidelines:

Jakarta EE Trademark Guidelines

Trademark Disclaimers

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.

Eclipse Foundation Website Privacy Policy

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

15 February 2024

This Privacy Policy explains how the Eclipse Group (“Us”, “Our”, or “We”, as further identified below in section “Who We Are. Data Controllers and Our contact data”) collects and processes Personal Information (as defined below) from website visitors (“you” or “your”). All references to the “Website” in this Privacy Policy are deemed to refer to any Eclipse Group website or online resource that contains a reference or link to this Privacy Policy, including in the first place the Website at https://www.eclipse.org/ as well as any other Website of the Eclipse Group.

Eclipse Public License 1.0 (EPL) Frequently Asked Questions

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

Please see the Eclipse Public License 2.0 FAQ.

For informational purposes only.

This FAQ attempts to provide answers to commonly asked questions related to the Eclipse Public License 1.0 (EPL). It is provided for informational purposes only. It is not part of, nor does it modify, amend, or supplement the terms of the EPL. The EPL is a legal agreement that governs the rights granted to material licensed under it, so please read it carefully. If there is any conflict between this FAQ and the EPL, the terms of the EPL shall govern. This FAQ should not be regarded as legal advice. If you need legal advice, you must contact your own lawyer.

Eclipse.org Terms of Use

webdev@eclipse-foundation.org (Mike Milinkovich) — Mon, 01 Jan 0001 00:00:00 +0000

15 February 2024

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.

Guidelines for User Groups that Support Eclipse Foundation Projects and Working Groups

webdev@eclipse-foundation.org (Wayne Beaton) — Mon, 01 Jan 0001 00:00:00 +0000

This document provides guidelines for user groups that are based on Eclipse Foundation projects and/or working groups. These user groups may leverage one or more Eclipse Foundation brands (e.g., Eclipse® , Jakarta® , or Tangle™ ).

A User Group must first sign the Eclipse User Group Trademark License Agreement before using the relevant brand. The agreement provides more detail about how the brand can be used.

Any User Group must have a focus on an Eclipse Foundation open source project and/or a working group community. A User Group can be a separate organization, or a subgroup of a larger group.
User Groups should promote free software both within the group and in relationships with other organizations.
User Groups should make an effort to foster a positive message about both Eclipse and free software.
It is necessary for any User Group to have a contact person who can act as a representative for the group and who accepts responsibility to ensure that the guidelines are followed. If the User Group has a president, then the president would be a good person to fill this role. For example, this person will be responsible to ensure that the User Group follows the requirements regarding how to use the Eclipse brand.
User Group members are expected to follow the Eclipse Foundation Community Code of Conduct at functions and interactions.

If a User Group is interested in having its own domain (e.g. eclipse.xx), then please contact the Eclipse Foundation to discuss if this is possible before registering the domain yourself.

Specification Non Assertion Covenant

webdev@eclipse-foundation.org (Wayne Beaton) — Mon, 01 Jan 0001 00:00:00 +0000

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.

Eclipse Foundation Legal Resources on Eclipse Foundation

About File Templates

Approved Licenses for Non-Code Content

Approved Licenses for Non-Code, Example, and Other Content

Committer Due Diligence Guidelines

Introduction

Copyright Agent

Developer Certificate of Origin

Eclipse Foundation Legal Frequently Asked Questions (FAQ)

Eclipse Foundation Open VSX Registry Frequently Asked Questions (FAQ)

Table of Contents

What is Open VSX Registry?

Eclipse Foundation Quality Verification Suite License - v 1.0

Eclipse Foundation Software User Agreement

Eclipse Foundation Specification License

Eclipse Foundation Specification License

Eclipse Foundation Technology Compatibility Kit License

Eclipse Foundation Trademark Usage Policy

Eclipse Foundation Trademark Usage Policy

Purpose:

Eclipse Foundation Trademarks

Trademark Use

Trademark Disclaimers

Eclipse Foundation Website Privacy Policy

Eclipse Public License 1.0 (EPL) Frequently Asked Questions

Eclipse.org Terms of Use

Terms and Conditions of Use for the Eclipse Foundation Website and Related Services

Guidelines for User Groups that Support Eclipse Foundation Projects and Working Groups

Specification Non Assertion Covenant