content/ide/images/theia_logo.svg

-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-/********************************************************************************
- * Copyright (C) 2018 TypeFox and others.
- *
- * This program and the accompanying materials are made available under the
- * terms of the Eclipse Public License v. 2.0 which is available at
- * http://www.eclipse.org/legal/epl-2.0.
- *
- * This Source Code may also be made available under the following Secondary
- * Licenses when the conditions for such availability set forth in the Eclipse
- * Public License v. 2.0 are satisfied: GNU General Public License, version 2
- * with the GNU Classpath Exception which is available at
- * https://www.gnu.org/software/classpath/license.html.
- *
- * SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
- ********************************************************************************/
--->
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
-<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0" y="0" preserveAspectRatio="xMinYMin meet" viewBox="0, 0, 3851.35, 540.6">
-  <g id="Layer_1" fill="#000000">
-    <path d="M3635.123,3.912 C3635.124,3.912 3658.62,3.912 3668.435,11.1 C3668.435,11.1 3678.299,18.288 3685.883,40.247 L3850.208,519.688 C3850.208,519.688 3852.488,525.736 3850.604,530.693 C3850.604,530.693 3848.721,535.6 3840.343,535.6 L3770.697,535.6 C3770.698,535.6 3762.37,535.6 3757.462,533.717 C3757.462,533.717 3752.505,531.833 3749.481,523.505 L3716.17,419.755 L3523.789,419.755 L3490.478,522.712 C3490.478,522.712 3488.198,529.553 3484.034,532.576 C3484.034,532.576 3479.87,535.6 3470.799,535.6 L3401.103,535.6 C3401.104,535.6 3392.776,535.6 3390.496,530.693 C3390.496,530.693 3388.265,525.736 3390.496,519.688 L3554.076,40.247 C3554.076,40.247 3557.893,28.896 3561.661,22.105 C3561.661,22.105 3565.478,15.264 3571.129,11.497 C3571.129,11.497 3576.829,7.68 3584.413,5.796 C3584.413,5.796 3591.948,3.912 3602.556,3.912 L3635.123,3.912 z M3620.748,106.175 L3616.981,106.175 L3585.9,211.363 L3546.542,340.741 L3691.931,340.741 L3652.572,213.593 L3620.748,106.175 z"/>
-    <path d="M2071.209,5.35 C2071.209,5.35 2081.817,5.35 2085.584,8.027 C2085.584,8.027 2089.352,10.654 2089.352,21.262 L2089.351,217.658 L2324.908,217.658 L2324.908,21.262 C2324.908,21.262 2324.908,11.397 2329.122,8.374 C2329.122,8.374 2333.285,5.35 2342.357,5.35 L2400.056,5.35 C2400.056,5.35 2410.664,5.35 2414.084,8.027 C2414.084,8.027 2417.505,10.654 2417.505,21.262 L2417.505,519.688 C2417.505,519.688 2417.505,530.296 2414.084,532.973 C2414.084,532.973 2410.664,535.6 2400.056,535.6 L2342.356,535.6 C2342.357,535.6 2333.285,535.6 2329.122,532.576 C2329.122,532.576 2324.908,529.553 2324.908,519.688 L2324.908,297.119 L2089.351,297.119 L2089.351,519.688 C2089.352,519.688 2089.352,530.296 2085.584,532.973 C2085.584,532.973 2081.817,535.6 2071.209,535.6 L2013.707,535.6 C2013.708,535.6 2005.38,535.6 2000.869,532.576 C2000.869,532.576 1996.309,529.553 1996.309,519.688 L1996.308,21.262 C1996.309,21.262 1996.309,11.397 2000.869,8.374 C2000.869,8.374 2005.38,5.35 2013.708,5.35 L2071.209,5.35 z"/>
-    <path d="M1840.411,5.35 C1840.411,5.35 1848.739,5.35 1851.416,8.374 C1851.416,8.374 1854.043,11.447 1854.043,19.775 L1854.043,72.17 C1854.043,72.17 1854.043,79.755 1851.416,82.778 C1851.416,82.778 1848.739,85.802 1840.411,85.802 L1696.559,85.802 L1696.559,519.688 C1696.559,519.688 1696.559,530.296 1693.139,532.973 C1693.139,532.973 1689.718,535.6 1679.11,535.6 L1619.924,535.6 C1619.924,535.6 1610.853,535.6 1606.689,532.576 C1606.689,532.576 1602.525,529.553 1602.525,519.688 L1602.525,85.802 L1461.647,85.802 C1461.647,85.802 1453.319,85.802 1451.039,82.778 C1451.039,82.778 1448.759,79.755 1448.759,72.17 L1448.758,19.775 C1448.759,19.775 1448.759,11.447 1451.039,8.374 C1451.039,8.374 1453.319,5.35 1461.647,5.35 L1840.411,5.35 z"/>
-    <path d="M881.099,2.2 C1029,2.2 1148.8,122 1148.8,269.9 C1148.8,417.7 1029,537.6 881.1,537.6 L291,537.6 C269.9,537.6 252.8,520.5 252.8,499.4 C252.8,478.3 269.9,461.2 291,461.2 L428.5,461.2 C449.5,461.2 466.6,444.1 466.6,423 C466.6,401.9 449.5,384.8 428.5,384.8 L397.899,384.8 C376.8,384.8 359.7,367.7 359.7,346.6 C359.7,325.5 376.8,308.4 397.9,308.4 L489.603,308.4 C510.818,308.341 527.273,291.05 527.8,270.2 C527.8,249.1 510.7,232 489.6,232 L168.7,232 C147.6,232 130.5,214.9 130.5,193.8 C130.5,172.7 147.6,155.6 168.7,155.6 L405.504,155.6 C426.718,155.541 443.173,138.25 443.7,117.4 C443.7,96.3 426.6,79.2 405.5,79.2 L352.1,79.2 C331,79.2 313.9,62.1 313.9,41 C313.9,19.9 331,1.8 352.1,1.8 L881.099,2.2 z M838.3,91.4 L838.3,91.4 C756.1,91.4 689.6,158 689.6,240.1 L689.6,299.6 C689.6,381.8 756.1,448.3 838.3,448.3 C920.4,448.3 987,381.8 987,299.6 L987,240.1 C987,158 920.4,91.4 838.3,91.4 L838.3,91.4 z M889.1,232 C908.9,232 925,248.1 925,267.9 L925,272.5 C925,292.3 908.9,308.4 889.1,308.4 L777.5,308.4 C757.7,308.4 741.6,292.3 741.6,272.5 L741.6,267.9 C741.6,248.1 757.7,232 777.5,232 L889.1,232 z"/>
-    <path d="M171,461.2 C190.9,461.2 206.9,477.2 206.9,497.1 L206.9,501.7 C206.9,521.5 190.9,537.6 171,537.6 L38.9,537.6 C19.1,537.6 3,521.5 3,501.7 L3,497.1 C3,477.2 19.1,461.2 38.9,461.2 L171,461.2 z"/>
-    <path d="M2952.904,4.854 C2952.905,4.854 2962.719,4.854 2965.396,9.068 C2965.396,9.068 2968.023,13.232 2968.023,22.303 L2968.023,70.088 C2968.023,70.088 2968.023,79.953 2965.396,83.373 C2965.396,83.373 2962.719,86.793 2952.905,86.793 L2751.452,86.793 C2751.452,86.793 2722.652,86.793 2710.904,99.632 C2710.904,99.632 2699.205,112.52 2699.205,136.71 L2699.205,216.171 L2927.872,216.171 C2927.872,216.171 2937.736,216.171 2940.413,219.988 C2940.413,219.988 2943.04,223.755 2943.04,234.314 L2943.04,275.903 C2943.04,275.903 2943.04,284.974 2940.413,289.089 C2940.413,289.089 2937.736,293.252 2927.872,293.252 L2699.205,293.252 L2699.205,403.942 C2699.205,403.942 2699.205,428.182 2711.697,440.674 C2711.697,440.674 2724.188,453.215 2751.452,453.215 L2957.415,453.215 C2957.415,453.215 2968.023,453.215 2970.7,456.982 C2970.7,456.982 2973.327,460.749 2973.327,471.357 L2973.327,518.201 C2973.327,518.201 2973.327,526.529 2970.303,531.04 C2970.303,531.04 2967.28,535.6 2957.415,535.6 L2741.587,535.6 C2741.588,535.6 2701.436,535.6 2675.659,524.249 C2675.659,524.249 2649.883,512.897 2634.318,493.961 C2634.318,493.961 2618.753,475.026 2612.706,450.786 C2612.706,450.786 2606.608,426.596 2606.608,400.076 L2606.608,141.172 C2606.608,141.172 2606.608,114.652 2613.796,90.065 C2613.796,90.065 2621.033,65.429 2637.342,46.493 C2637.342,46.493 2653.65,27.607 2679.427,16.206 C2679.427,16.206 2705.253,4.854 2741.588,4.854 L2952.904,4.854 z"/>
-    <path d="M3219.328,5.35 C3219.328,5.35 3229.887,5.35 3233.704,8.027 C3233.704,8.027 3237.471,10.654 3237.471,21.262 L3237.471,519.688 C3237.471,519.688 3237.471,530.296 3233.704,532.973 C3233.704,532.973 3229.887,535.6 3219.328,535.6 L3161.827,535.6 C3161.827,535.6 3152.756,535.6 3148.592,532.576 C3148.592,532.576 3144.428,529.553 3144.428,519.688 L3144.428,21.262 C3144.428,21.262 3144.428,11.397 3148.592,8.374 C3148.592,8.374 3152.756,5.35 3161.827,5.35 L3219.328,5.35 z"/>
-    <path d="M232.2,2.8 C252,2.8 268,18.9 268,38.7 L268,43.4 C268,63.2 252,79.2 232.2,79.2 L84.7,79.2 C64.9,79.2 48.8,63.2 48.8,43.4 L48.8,38.7 C48.8,18.9 64.9,2.8 84.7,2.8 L232.2,2.8 z"/>
-    <path d="M278,308.4 C297.8,308.4 313.9,324.5 313.9,344.3 L313.9,348.9 C313.9,368.7 297.8,384.8 278,384.8 L197,384.8 C177.2,384.8 161.1,368.7 161.1,348.9 L161.1,344.3 C161.1,324.5 177.2,308.4 197,308.4 L278,308.4 z"/>
-  </g>
-</svg>
\ No newline at end of file

content/legal/_index.md

+---
+title: "Eclipse Foundation Legal Resources"
+layout: single
+keywords:
+    - legal
+    - documents
+    - about
+---
+
+Legal resource page for the Eclipse Foundation.
+
+> * [Getting Started](./#GettingStarted)
+> * [Agreement and Licenses](./#Agreements)
+> * [Privacy and Trademarks](./#Trademarks)
+> * [Committer Agreements](./#CommitterAgreements)
+> * [Committer Resources](./#Committers)
+
+### Getting Started { #GettingStarted }
+
+* The [Guide to the Legal Documents](/projects/handbook/#legaldoc) provides an in-depth look at the many legal documents related to the Eclipse open source community. This content is of value to committers, contributors, redistributors of Eclipse content, developers of Eclipse-based products and users of Eclipse technologies;
+* Unless otherwise noted in the project documentation, the [Eclipse Public License](epl-2.0) (EPL) is the default license for Eclipse Foundation projects (please see the [Eclipse Public License Frequently Asked Questions](/org/documents/epl-2.0/faq.php));
+* The [Eclipse Foundation Legal Frequently Asked Questions](faq) answers some of the commonly asked questions about Eclipse.org licensing, contributions, working as a committer, and cryptography;
+* [Third Party Content Licenses](licenses) provides a list of licenses that are approved for third party content used by Eclipse projects; or
+* For other questions, email: [license@eclipse-foundation.org](mailto:license@eclipse-foundation.org).
+
+### Agreements and Licenses { #Agreements }
+
+* [Web Site Terms of Use:](terms-of-use) By accessing, browsing or using this web site, you acknowledge that you have read, understood, and agree to be bound by the terms and conditions contained in this agreement.
+* [Eclipse Public License](epl-2.0) (EPL): The default license for Eclipse Foundation projects.
+* [Eclipse Distribution License](/org/documents/edl-v10.php) (EDL): The BSD license used by some Eclipse Foundation projects which implement permissive dual-licensing along with the EPL. Other than for [example code or build scripts](non-code-licenses).
+* [Eclipse Contributor Agreement:](eca) If you are contributing code or documentation to Eclipse Foundation projects you are required to complete this agreement.
+* [Developer Certificate of Origin:](dco) If you are contributing code or documentation to Eclipse Foundation projects, and using the git signed-off-by mechanism, you are agreeing to this certificate.
+* [Copyright Agent:](copyright) Contact information for the Eclipse Foundation's Copyright Agent.
+* [Eclipse Foundation Software User Agreement:](epl/notice) By downloading binaries or accessing Eclipse Foundation source code repositories, you acknowledge that you have read, understood, and agree to be bound by the terms and conditions contained in this agreement.
+* [Approved Licenses for Non-Code, Example, and Other Content:](non-code-licenses) The Board of Directors has approved the use of certain licenses for specific types of content on eclipse.org.
+* [Eclipse Foundation Adoptium Marketplace Publisher Agreement:](documents/eclipse-adoptium-marketplace-publisher-agreement.pdf) The license agreement Adoptium Working Group Members must agree to before publishing links in the Adoptium Marketplace from which publisher makes Java SE distributions in binary form.
+* [Eclipse Foundation Open VSX Publisher Agreement:](documents/eclipse-openvsx-publisher-agreement.pdf) The license agreement Eclipse Open VSX Registry publishers must agree to before publishing extensions for VS Code compatible editors on [open-vsx.org](https://open-vsx.org/). You may read the Open VSX Registry FAQ [here](open-vsx-registry-faq/).
+* [Eclipse Foundation Specification License:](efsl) The license used by Eclipse Foundation specifications created under the Eclipse Foundation Specification Process.
+* [Eclipse Foundation TCK License:](tck) The binary license used by Technology Compatibility Kits to demonstrate compatibility with their corresponding Specifications.
+* [Eclipse Foundation Quality Verification Suite License:](eclipse-foundation-quality-verification-suite-license) The license that governs the use and redistribution of the Eclipse Quality Verification Suite (QVS) in binary form.
+* [Eclipse Foundation User Group Trademark License Agreement:](user-groups) Guidelines and agreements for user groups that are based on Eclipse Foundation projects and/or working groups.
+
+### Privacy and Trademarks { #Trademarks }
+
+* [Privacy Policy:](privacy) Your privacy is important to us. This statement discloses the information practices for this web site, including what type of information is gathered and tracked, how the information is used, and with whom the information is shared.
+* [Eclipse Foundation Trademark Usage Guidelines:](logo-guidelines) Guidelines on permissable use of Eclipse logos and trademarks.
+* [Trademark and Domain Name Assignment Agreement:](/legal/trademarks/trademark-transfer-agreement.pdf) 
+  Pre-existing projects which move to the Eclipse Foundation will be required
+  to execute this agreement to ensure that the Eclipse Foundation has rights to
+  any trademarks associated with the project name. Send the completed agreement
+  to <trademarks@eclipse-foundation.org>.
+* [Eclipse Foundation Trademarks:](trademarks) The list of trademarks claimed by the Eclipse Foundation.
+* [Trademark Attributions:](trademarks#attribution) Content on this web site may make reference to trademarks requiring attribution.
+
+### Committer Agreements { #CommitterAgreements }
+
+For Eclipse projects (and the open source world in general), _committers_ are the ones who hold the keys. Committers decide what code goes into the code base, they decide how a project builds, and they ultimately decide what gets delivered to the adopter community. Committer status is assigned following a demonstration of merit (generally a record of high-quality contribution to a project) and a successful [committer election](/projects/handbook#elections-committer).
+
+The specific agreements required depends on the nature of the project. For committers on an open source _software_ project (i.e., most Eclipse Foundation projects), the [traditional agreements](/projects/handbook/#paperwork-documents) are required. For committers on an open source _specification_ project, additional [working group agreements](/projects/handbook/#specifications-agreements) are required.
+
+Committer status is assigned on a project-by-project basis. That is, individuals have committer rights only on those projects for which they hold committer status. For all other projects, they are contributors.
+
+**Our committer provisioning process is automated**: new committers will—following their successful election—be contacted by email to engage in our _agreement workflow_ (also referred to as our [paperwork process](/projects/handbook/#paperwork)), which guides them through signing those agreements that they need. The agreements are provided below for convenience.
+
+* [Member Committer and Contributor Agreement:](committer-process/eclipse-member-committer-agreement.pdf) The Member Committer and Contributor Agreement (MCCA) is used by organizations that are [members of the Eclipse Foundation](/membership) to cover all of their employees who participate in Eclipse Foundation open source projects as committers and contributors. This agreement allows employees of our member organizations to participate in Eclipse Foundation projects without any additional paperwork.
+* [Individual Committer Agreement:](/legal/committer-process/eclipse-individual-committer-agreement.pdf) This agreement is used by committers participating in Eclipse open source projects whose employers are either not [members of the Eclipse Foundation](/membership) or are members that have not signed the Member Committer and Contributor Agreement.
+* [Employer Consent Agreement for Eclipse Foundation Specification Projects:](documents/employer-consent-agreement-for-specification-projects-v1.0.pdf) The Employer Consent Agreement for Eclipse Foundation Specification Projects ("Employer Consent Agreement") is to be completed by the employer of a committer who is seeking Individual Committer status on an Eclipse Foundation [Specification Project](/projects/efsp) operating under the purview of an Eclipse Foundation Working Group. Note that this form is only required when the employer is not a participant of the corresponding [working group](/org/workinggroups).
+
+### Resources for Committers { #Committers }
+
+A committer is a person that has been granted commit rights to systems on the Eclipse servers such as Git repositories, web pages, download servers, mailing lists and so forth. In addition to writing project content, committers play a critical role is other aspects of managing an open source project.
+
+* [Eclipse Project Handbook:](/projects/handbook) This Eclipse Project Handbook is a reference guide for working as a committer on an Eclipse open source project.
+* [Intellectual Property Due Diligence:](/projects/handbook/#ip) At least in some cases, the Eclipse Foundation's IP Team needs to be engaged to review third-party content, or contributions of project content from non-committers. Committers have an important role to play in this process.
+  * [Eclipse Committer Due Diligence Guidelines:](committer-guidelines) This document outlines the issues to be aware of and the processes one should follow when working as a committer on Eclipse projects.
+  * [Project Content:](/projects/handbook/#ip-project-content) Project Content is content that is managed by the project team. This includes content that is produced by project committers, along with content that is contributed to the project by outside contributors.
+  * [Third-party Content:](/projects/handbook/#ip-third-party) The Eclipse Foundation IP Due Dilience Process defines three different types: Prerequisite, Exempt Prerequisite, and Works With Dependency.
+  * [IP Logs:](/projects/handbook/#ip-iplog) An IP Log is a record of the intellectual property contributions to a project. This includes such as a list of all committers, past and present, that have worked on the code and (especially) those who have made contributions to the current code base.
+* [Legal Documentation:](/projects/handbook/#legaldoc) This provides templates for `NOTICE`, `CONTRIBUTING`, `LICENSE` and other files that accompany project source code and distributions.
+* [Committer Elections:](/projects/handbook/#elections) Contributors may become committers via committer election.

content/legal/approved-content-licenses/index.md

+---
+title: "Approved Licenses for Non-Code Content"
+author: Mike Milinkovich
+keywords:
+    - legal
+    - guide
+    - summary
+---
+
+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](/legal/terms-of-use)). They are:
+
+- Eclipse Public License 1.0

content/legal/committer-guidelines/index.md

+---
+title: "Committer Due Diligence Guidelines"
+author: Mike Milinkovich
+hide_page_title: true
+keywords:
+    - legal
+    - foundation
+    - committer
+    - committers
+    - diligence
+    - guidelines
+    - IP
+    - intellectual property
+    - policy
+    - procedure
+---
+
+{{< pages/legal/inject-content >}}

content/legal/compliance/_index.md

+---
+title: Compliance
+hide_sidebar: true
+hide_page_title: true
+layout: single
+---
+
+{{< pages/legal/compliance >}}

content/legal/compliance/dsa/index.md

+---
+title: "DSA Compliance Disclosure"
+date: "2024-02-12"
+lastmod: "2024-02-12"
+tags: ["digital services act", "content management", "moderation practices", "algorithm", "policy"]
+hide_sidebar: true
+container: "container padding-bottom-30"
+---
+
+Last Updated: 6 February 2025
+
+This page was created to ensure our adherence to the Digital Services Act
+(DSA). It includes information on our content management and moderation
+practices across our various online platforms.
+
+{{< table_of_contents >}}
+
+## Semi-Annual Moderation Report
+
+This table provides transparency regarding key statistics for our moderation
+practices across our online platforms from 1 July 2024 to 31 December 2024.
+
+| Website                    | Total Actions Taken | Content Removed | Content Altered | Reason: Spam | Reason: Violation of ToU | User Notified | Appeals Received | Appeals Upheld |
+|----------------------------|---------------------|-----------------|-----------------|--------------|--------------------------|---------------|------------------|----------------|
+| Adoptium Marketplace       | 0                   | 0               | 0               | 0            | 0                        | 0             | 0                | 0              |
+| Eclipse Bugzilla           | 0                   | 0               | 0               | 0            | 0                        | 0             | 0                | 0              |
+| Eclipse Chat Service       | 0                   | 0               | 0               | 0            | 0                        | 0             | 0                | 0              |
+| Eclipse Forums             | 4                   | 4               | 0               | 4            | 0                        | 0             | 0                | 0              |
+| Eclipse GitHub             | 2                   | 2               | 0               | 2            | 0                        | 0             | 0                | 0              |
+| Eclipse GitLab             | 6                   | 6               | 0               | 6            | 0                        | 0             | 0                | 0              |
+| Eclipse Marketplace        | 2                   | 2               | 0               | 2            | 0                        | 0             | 0                | 0              |
+| Eclipse Newsroom           | 2                   | 1               | 1               | 1            | 0                        | 0             | 0                | 0              |
+| Jakarta Blogs              | 0                   | 0               | 0               | 0            | 0                        | 0             | 0                | 0              |
+| Open VSX                   | 6                   | 6               | 0               | 0            | 6                        | 6             | 0                | 0              |
+| Eclipse Wiki               | 0                   | 0               | 0               | 0            | 0                        | 0             | 0                | 0              |
+| Planet Eclipse             | 0                   | 0               | 0               | 0            | 0                        | 0             | 0                | 0              |
+
+## Moderation Practices & Algorithm Information
+
+The general moderation guidelines for the Eclipse Foundation's web properties
+include removing content that:
+
+1. Is off-topic for the conversation or content
+2. Include third-party links with misleading labels
+3. Unsolicited advertisements
+4. AI-generated content or incomprehensible text
+5. Contains illegal material or exposes personal risk (e.g., residential
+   address)
+6. Reveals secrets (e.g. passwords) or infringes on intellectual property
+7. Appears to manipulate posting requirements or limits
+8. Is believed to be spam or in violation of our policies
+9. The content was submitted in a language not supported by the platform. All
+   our sites default to English unless the platform explicitly supports
+   multiple languages. This is to ensure that the content is accessible to our
+   global audience
+
+These guidelines are designed to ensure that all content on Eclipse Foundation
+web properties respects user privacy, aligns with our policies and processes,
+including our [Terms of Use](https://www.eclipse.org/legal/terms-of-use/),
+our [Privacy Policy](https://www.eclipse.org/legal/privacy/), and our
+[Community Code of Conduct](https://www.eclipse.org/org/documents/Community_Code_of_Conduct.php),
+and maintains the integrity and quality expected by our community.
+
+To dispute a moderation decision, or to report any content that may violate our
+Terms of Use or the Digital Service Act (DSA), please contact
+<transparency@eclipse-foundation.org>.
+
+## Adoptium Marketplace
+
+*URL: https://adoptium.net/marketplace/*
+
+The Adoptium Marketplace promotes high-quality, TCK certified and Eclipse
+AQAvit verified runtimes for use across the Java ecosystem.
+
+For details on our publication guidelines, please visit our
+[Adoptium® Marketplace Publisher Guide](https://adoptium.net/docs/marketplace-guide/)
+page and the [Adoptium® Software Products Marketplace Policy](https://adoptium.net/docs/marketplace-policy/)
+page.
+
+## Eclipse Bugzilla
+
+*URL: https://bugs.eclipse.org/bugs/*
+
+Eclipse Bugzilla is a bug-tracking and reporting platform for the Eclipse
+community. This platform allows users and developers to submit and discuss
+issues related to Eclipse projects.
+
+Content moderation is done when users report content that does not adhere to
+Eclipse Foundation’s moderation guidelines. A foundation staff member will
+review and remove it if necessary.
+
+## Eclipse Chat Service
+
+*URL: https://chat.eclipse.org*
+
+Eclipse Chat Service is a messaging platform for the Eclipse community, built
+on the Matrix protocol for secure, decentralized communication.
+
+Content moderation is performed when users report content that does not adhere
+to the Eclipse Foundation’s moderation guidelines. A foundation staff member or
+project maintainer will review and remove content if necessary. Additionally,
+an automated moderation tool is used to detect and remove spam.
+
+## Eclipse Forums
+
+*URL: https://www.eclipse.org/forums/*
+
+The Eclipse Forums is an interactive platform where the Eclipse community can
+engage in discussions, seek help, share information, and collaborate on various
+topics related to Eclipse projects and technologies.
+
+Content moderation is done when users report content that does not adhere to
+Eclipse Foundation’s moderation guidelines. A foundation staff member will
+review and remove it if necessary.
+
+## Eclipse GitHub
+
+*URL: https://www.github.com*
+
+GitHub is a third-party platform used by the Eclipse Foundation to host and
+manage open-source projects. It allows users to submit issues, participate in
+discussions, and collaborate on code development.
+
+Content moderation is performed when users report content that does not adhere
+to the Eclipse Foundation’s moderation guidelines. A foundation staff member or
+project maintainer will review and remove content if necessary.
+
+## Eclipse GitLab
+
+*URL: https://gitlab.eclipse.org/*
+
+GitLab is a DevOps platform for Git repository management, issue tracking, and
+CI/CD for open source projects. This is a self-managed instance of Gitlab
+maintained by the Eclipse Foundation.
+
+Content moderation is done when users report content that does not adhere to
+Eclipse Foundation’s moderation guidelines. A foundation staff member will
+review and remove it if necessary.
+
+Additionally, an automated spam detection system analyzes content and when
+triggered it automatically deletes the content and associated user account.
+
+## Eclipse Marketplace
+
+*URL: https://marketplace.eclipse.org*
+
+The Eclipse Marketplace is a community-powered marketplace platform for
+promoting solutions and services related to Eclipse technologies.
+
+Details on our moderation guidelines and content algorithm can be found on our
+[Marketplace Client Content Inclusion Policy](https://marketplace.eclipse.org/content/marketplace-client-content-inclusion-policy)
+page.
+
+## Eclipse Newsroom
+
+*URL: https://newsroom.eclipse.org/*
+
+The Eclipse Newsroom is a platform that enables staff and members of the
+Eclipse community to submit news, events and resources such as, but not limited
+to case studies, white papers and market reports. These submissions are
+featured across various websites operated by the Eclipse Foundation
+
+Each submission is reviewed by staff before publication to ensure it adheres to
+Eclipse Foundation’s moderation guidelines
+
+## Jakarta Blogs
+
+*URL: https://jakartablogs.ee/*
+
+Jakarta Blog is a website that aggregates blog posts from diverse contributors
+in the Jakarta EE community. It serves as a platform where individuals
+interested in cloud native Java innovation can share their insights, updates,
+and thoughts.
+
+Before a new feed is added to Jakarta Blog, our staff will review the current
+content to ensure it follows both the Eclipse Foundation’s moderation
+guidelines and the [Jakarta Blog guidelines](https://github.com/jakartaee/jakartablogs.ee?tab=readme-ov-file#guidelines).
+
+## Open VSX Registry
+
+*URL: https://open-vsx.org/*
+
+The Open VSX Registry is a vendor-neutral, open-source platform managed by the
+Eclipse Foundation for publishing and downloading VS Code extensions.
+
+All publishers must sign the Eclipse Foundation Open VSX Publisher Agreement
+and ensure that their extensions are properly licensed.
+
+Listings on the site are sorted by relevance by default, which is calculated
+based on user ratings, download counts, and the publishing date of the
+extension. Unverified extensions are assigned a lower relevance score, while
+those that are recently updated are given a higher score. This algorithm
+ensures that relevant extensions are prioritized for the end users.
+
+## Eclipse Wiki
+
+*URL: https://wiki.eclipse.org/*
+
+The Eclipse Wiki is a collaborative content editing platform for the Eclipse
+community.
+
+Content moderation is done when users report content that does not adhere to
+Eclipse Foundation’s moderation guidelines. A foundation staff member will
+review and remove it if necessary.
+
+## Planet Eclipse
+
+*URL: https://planeteclipse.org/planet/*
+
+Planet Eclipse is a website that aggregates and displays blog posts from
+various contributors within the Eclipse community. It serves as a platform
+where individuals interested in Eclipse technology can share their insights,
+updates, and thoughts.
+
+Before a new feed is added to Planet Eclipse, our staff will review its
+existing content to ensure it follows both the Eclipse Foundation’s moderation
+guidelines and the [Planet Eclipse guidelines](https://gitlab.eclipse.org/eclipsefdn/it/websites/planeteclipse.org#guidelines).
+

content/legal/copyright/index.md

+---
+title: Copyright Agent
+author: Mike Milinkovich
+keywords:
+  - legal
+  - privacy
+  - policy
+related:
+  links:
+    - text: Legal resources
+      url: /legal
+    - text: Guide to legal documents
+      url: /projects/handbook#legaldoc
+---
+
+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:
+
+- Your address, telephone number, and email address;
+- A description of the copyrighted work that you claim has been infringed;
+- A description of where the alleged infringing material is located;
+- A statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law;
+- An electronic or physical signature of the person authorized to act on behalf of the owner of the copyright interest; and
+- A statement by you, made under penalty of perjury, that the above information in your Notice is accurate and that you are the copyright owner or authorized to act on the copyright owner's behalf.
+
+### Copyright Agent
+
+Eclipse Foundation AISBL  
+Attention: License Department  
+Rond Point Schuman 11  
+Brussels 1040 Belgium  
+
+Phone: [+32 2 808 81 52](tel:+3228088152)  
+Email: [license@eclipse-foundation.org](mailto:license@eclipse-foundation.org)

content/legal/cpl2epl/_index.md

+---
+title: "CPL to EPL Conversion"
+author: "Mike Milinkovich"
+keywords: ["legal", "documents", "about", "cpl", "epl", "conversion", "convert"]
+is_deprecated: true
+layout: "single"
+---
+
+As part of the formation of the Eclipse Foundation, the Eclipse community
+migrated from the Common Public License (CPL) to the Eclipse Public License
+(EPL). This conversion resulted in changes to quite a few legal documents on
+our website. This page maintains the transition plan and the old versions of
+the eclipse.org documents which reference the CPL.
+
+{{< figure src="/images/osi-certified-60x50.gif" caption="The Eclipse Public License is an OSI-approved open source license." >}}
+
+The Eclipse Foundation began the transition from the CPL to the EPL on
+September 9th, 2004. It was substantially completed with the release of Eclipse
+3.1 on June 28, 2005.
+
+## CPL to EPL Transition
+
+- CPL to EPL Transition Plan Frequently Asked Questions.\
+  This FAQ answers some of the commonly asked questions about transition from
+  the Common Public License (CPL) to the Eclipse Public License (EPL).
+- CPL to EPL Transition Plan The detailed plan (.pdf) for transitioning from
+  the Common Public License (CPL) to the Eclipse Public License (EPL).
+
+## Agreements and Licenses
+
+- [Eclipse.org Software User Agreement](/legal/cpl2epl/notice/) By downloading
+  builds or accessing the CVS repository, you acknowledge that you have read,
+  understood, and agree to be bound by the terms and conditions contained in
+  this agreement. This agreement is used for projects that default to the
+  Common Public License (CPL).
+
+## Frequently Asked Questions
+
+- [CPL Frequently Asked Questions](http://www.ibm.com/developerworks/opensource/library/os-cplfaq/index.html)
+  Written by IBM and hosted at IBM’s developerWorks site, this FAQ answers some
+  of the commonly asked questions about the Common Public License (CPL).
+
+## Resources for Committers
+
+- ["About" Template (CPL References)](/legal/cpl2epl/about/) This is a template
+  for an "about.html" ("About") file that describes CPL-licensed content.
+  Abouts contain legal documentation and are maintained in the CVS repository
+  and subsequently included in builds in plug-in and other directories. They
+  usually contain information about licensing and sometimes also information
+  about any use of cryptography. By convention, every plug-in usually has an
+  About. If all the content in a plug-in, directory or module can be
+  correctly licensed under the CPL then this template can be used without
+  modification. Any other About should be approved by the relevant PMC who
+  can also assist committers with drafting an About.
+- [Default Copyright and License](/legal/cpl2epl/copyright-and-license-notice/)
+  Notice The standard copyright and license notice should appear in all source
+  files where possible. Variations on this notice may be required (for example
+  where a license other than the CPL or EPL governs the use of the file).

content/legal/cpl2epl/about/index.md

+---
+title: "About File Template"
+is_deprecated: true
+related:
+  links:
+    - text: CPL About.html in plain HTML
+      url: about.html
+    - text: CPL to EPL conversion
+      url: /legal/cpl2epl/
+    - text: Guide to legal documents
+      url: /projects/handbook#legaldoc
+---
+
+## About This Content
+
+20th June, 2002
+
+### License
+
+Eclipse.org makes available all content in this plug-in ("Content"). Unless
+otherwise indicated below, the Content is provided to you under the terms and
+conditions of the Common Public License Version 1.0 ("CPL"). A copy of the CPL
+is available at [http://www.eclipse.org/legal/cpl/cpl-v10.html](/legal/cpl/cpl-v10.html). For purposes of the
+CPL, "Program" will mean the Content.
+
+### Contributions
+
+If this Content is licensed to you under the terms and conditions of the CPL,
+any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of
+Eclipse.org web site, by you that relate to such Content are provided under the
+terms and conditions of the CPL and can be made available to others under the
+terms of the CPL.
+
+If this Content is licensed to you under license terms and conditions other
+than the CPL ("Other License"), any modifications, enhancements and/or other
+code and/or documentation ("Modifications") uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of
+Eclipse.org, by you that relate to such Content are provided under terms and
+conditions of the Other License and can be made available to others under the
+terms of the Other License. In addition, with regard to Modifications for which
+you are the copyright holder, you are also providing the Modifications under
+the terms and conditions of the CPL and such Modifications can be made
+available to others under the terms of the CPL.

content/legal/cpl2epl/copyright-and-license-notice/index.md

+---
+title: Default Eclipse Foundation Copyright and License Notice
+author: Mike Milinkovich
+is_deprecated: true
+keywords:
+  - legal
+  - documents
+  - cpl
+  - epl
+---
+
+Last updated September 8th, 2004 (see [the Eclipse Project Handbook](/projects/handbook/#ip-copyright-headers) for current information)
+
+With the Eclipse Foundation transitioning from the CPL to the EPL (for further information see the [CPL to EPL Transition Plan](/legal/cpl2epl/cpl2epl-transition-plan.pdf) (.pdf) and matching [FAQ](/legal/cpl2epl/faq/)), the default license for a project will either be the CPL or the EPL. For CPL projects, the notice template is:
+
+/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
+ \* Copyright (c) {DATE} {INITIAL COPYRIGHT OWNER} {OTHER COPYRIGHT OWNERS}.  
+ \* All rights reserved. This program and the accompanying materials  
+ \* are made available under the terms of the Common Public License v1.0  
+ \* which accompanies this distribution, and is available at  
+ \* http://www.eclipse.org/legal/cpl-v10.html  
+ \*  
+ \* Contributors:  
+ \*    {INITIAL AUTHOR} - initial API and implementation  
+ \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*/
+
+For EPL projects, the notice template is:
+
+/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
+ \* Copyright (c) {DATE} {INITIAL COPYRIGHT OWNER} {OTHER COPYRIGHT OWNERS}.  
+ \* All rights reserved. This program and the accompanying materials  
+ \* are made available under the terms of the Eclipse Public License v1.0  
+ \* which accompanies this distribution, and is available at  
+ \* http://www.eclipse.org/legal/epl-v10.html  
+ \*  
+ \* Contributors:  
+ \*    {INITIAL AUTHOR} - initial API and implementation  
+ \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*/
+
+NOTE: While the CPL to EPL Transition Plan is in effect, do NOT use the EPL notice unless you know for certain that your project has transitioned fully to the EPL.
+
+If the contents of the file are to be governed by another license, different text will be required. Contact the relevant PMC for assistance with this.
+
+**{DATE}** is either a year or a range of years with the first and last years of the range separated by a comma. So for example: "2004" or "2000, 2004". The first year is when the contents of the file were first created and the last year is the last year is when the contents were last modified.
+
+**{INITIAL COPYRIGHT OWNER}** is the copyright owner that created the initial content. If the content is subsequently modified and appended to by other copyright owners, the words "and others" are typically appended. So for example: "XYZ Corp." or "XYZ Corp. and others". The words "and others" are used to avoid having to list every copyright owner and because often, most of the content in the file was contributed the by initial copyright owner with subsequent modifications by others being smaller. However especially if the number of copyright owners is small (e.g. two), there is nothing wrong with listing all of them especially if their contributions are more proportionately equal. For example: "XYZ Corp., John Smith, and ABC Enterprises."
+
+NOTE: Do not confuse copyright owners with authors (which is explained below). A copyright owner may be either an individual or an entity. If a person is making their contributions on behalf of their employer, then the copyright owner is usually the employer (i.e. "XYZ Corp." and not "John Smith").
+
+**{INITIAL AUTHOR}** is the name of the person that wrote the initial content. Subsequent authors are listed on proceding lines with a short description of the contribution. If there is an associated Bugzilla report number, then it is good practice to include it here. Over time, this section actually becomes a log of the contributions. Although it could become quite lengthy in some cases, it should be maintained for two important reasons - to acknowledge the contributions of individuals (especially when their contribution is owned by their employer), and to assist with tracking the pedigree of the code (who wrote what). It is good practice to list the name of the author with their employer if the latter owns the copyright. For example: "John Smith (XYZ Corp.)".