Eclipse Foundation contributor agreements and trademark rules

Does the Eclipse Foundation still require contributor agreements and trademark rules for open source projects

Yes. Eclipse projects still use contributor agreements, and trademark use still follows Foundation rules. The part people miss is that these are separate controls: one covers intellectual property rights in contributions, the other covers how project names, logos, and related marks are used. If you are working inside an Eclipse project, both matter. The Eclipse Project Handbook says contributors must sign the Eclipse Contributor Agreement, and the trademark pages say project names and logos are Foundation trademarks.

The contributor agreement is not a formality for show. The Eclipse Contributor Agreement states that anyone making intellectual property contributions to Eclipse projects must agree to it, and the handbook says contributors who are not committers are required to sign it electronically. The practical purpose is clear: Eclipse wants a written record that the contributor has the rights to contribute the code or documentation under the project license.

The part people get wrong is assuming committers and contributors are treated the same. They are not. The handbook says committers are already covered by a committer agreement, so they do not need to also sign the ECA. That does not remove the requirement, it changes which agreement covers the person. If you are only contributing a patch, you need the ECA path. If you are a committer, you are covered through the committer agreement path instead.

Trademark rules are still active too. The Eclipse trademarks page says the names and logos of all open source projects, working groups, specifications, and downloadable software products are trademarks of the Eclipse Foundation. The handbook adds that the use of Eclipse Foundation trademarks outside the immediate scope of the open source project, including project names, is subject to the Trademark Usage Guidelines. In practice, that means you do not treat the project name like generic public-domain wording.

That trademark rule shows up early, not only after a project is famous. The handbook says the EMO performs a trademark search and clearance review as part of project creation or renaming, and it says existing project name trademarks must be transferred to the Foundation when a project moves in. That is the inconvenient part for teams that already have a name, a logo, or a long-lived brand: the Foundation checks the mark, clears the mark, and may require transfer before the project proceeds.

The Foundation also expects trademark notices in project materials. The handbook says notices must include copyright statements, assertions of trademarks owned by the Foundation on behalf of the project, and indication of third-party trademarks in use. Its example notices show the pattern: name the Foundation-owned mark, identify outside trademarks like Java when they appear, and avoid implying endorsement or association that has not been approved. That is why project websites, download pages, and about dialogs often carry legal text that feels heavier than the code itself.

A common mistake is thinking trademark rules only apply to marketing pages. They do not. The handbook directs developers to the official project website for contribution information, and the trademark guidance also reaches the project name itself, downloadable software, and community materials. If a team launches a mirrored site, a meetup page, or a package page that uses the project name, it still needs to respect the Foundation’s mark rules and attribution language.

The legal structure is broader than one agreement or one policy. The Foundation’s legal resources page lists the ECA, trademark usage guidelines, trademark assignment agreements, and related legal documents. The governance pages also point to the IP Policy, which describes the processes the Foundation uses to accept and license intellectual property developed by projects. That means contributor paperwork and trademark rules are part of a larger governance system, not optional add-ons a project can ignore when the repository is already public.

The question people usually mean is whether this is still true for open source projects under the Eclipse umbrella today. The answer is yes. The current ECA page is dated March 3, 2026, and the current handbook still says contributors must sign the ECA and that trademark use is governed by the Foundation’s trademark guidelines. If your project is Eclipse-hosted or wants to become Eclipse-hosted, the rules are still live, not historical.

If you are setting up a new project, the clean sequence is simple. First, confirm who is contributing code and documentation, then make sure the contributor path matches the correct agreement coverage. Second, check the project name, logo, and website copy against the trademark guidance before you publish. Third, treat the official handbook as the source of truth for project operations, not the memory of a prior project or the way another foundation handles things.

If you are already inside an Eclipse project and a contributor has not signed the ECA, the issue is not cosmetic. The handbook says systems are in place to detect whether commits and pull requests are covered by an ECA. That means the missing agreement can block contribution acceptance, create cleanup work for the project leads, and slow the IP review process. The fix is to get the right agreement in place before the contribution is merged, not after the fact.

So the short answer is straightforward: yes, the Eclipse Foundation still requires contributor agreements, and yes, trademark rules still apply. The important detail is that these rules are not one-size-fits-all. Contributors, committers, and project owners are handled through different documents, but the Foundation still expects all three groups to follow the current legal framework.

For teams that want the rest of the onboarding and project-management context in one place, the Foundation’s handbook is the right starting point, and it is the page to read before you publish project names, logos, or contribution instructions. If you are comparing this with other ecosystems, the exact rule set is one reason Eclipse projects feel more governed than a loose GitHub repository. That structure is intentional.

If you are also building a tester exchange or launch workflow around an app project, DevConnect keeps that separate from legal governance. Its public platform page can help with testing coordination, while Eclipse rules still control the IP and trademark side of the project if the project sits under Eclipse. See the platform here: https://devconnectplatform.com. That link is for context, not a source for the Eclipse rules.