Intellectual Property

Dogfooding the Eclipse Dash License Tool

Wednesday, July 22, 2020 - 11:43 by Wayne Beaton

There’s background information about this post in my previous post. I’ve been using the Eclipse Dash License Tool on itself.

Updates to the Eclipse IP Due Diligence Process

Thursday, June 25, 2020 - 15:23 by Wayne Beaton

In October 2019, The Eclipse Foundation’s Board of Directors approved an update to the IP Policy that introduces several significant changes in our IP due diligence process. I’ve just pushed out an update to the Intellectual Property section in the Eclipse Foundation Project Handbook.

I’ll apologize in advance that the updates are still a little rough and require some refinements. Like the rest of the handbook, we continually revise and rework the content based on your feedback.

Revising the Eclipse IP Due Diligence Process for Third Party Content

Thursday, May 7, 2020 - 16:21 by Wayne Beaton

The Eclipse Foundation’s board of directors approved an update to the Eclipse Foundation’s Intellectual Property (IP) Policy in October 2019. With help from some of our open source project teams and the Eclipse Architecture Council, we’ve been defining, refining, and rolling out updates to our corresponding IP due diligence process and supporting services. A big part of this update is a change in the way that we will manage third party content.

Specification Project Committer Agreements

Wednesday, February 12, 2020 - 13:36 by Wayne Beaton

We identified a hole in our committer agreement process that excluded individuals with a certain employment status from participating in Eclipse Foundation open source specification projects operating under the Eclipse Foundation Specification Process (EFSP).

Eclipse Committer and Contributor Paperwork

Wednesday, November 27, 2019 - 19:03 by Wayne Beaton

The Eclipse Foundation has several agreements that we use to ensure that contributors understand the terms by which they make their contributions and, especially, to give them an opportunity to assert that they have the necessary rights to make those contributions under the terms of the corresponding project license.

Eclipse IP Policy: Reviewing Third Party Content

Wednesday, November 13, 2019 - 16:33 by Wayne Beaton

I’ll start this discussion with some background…

Under the original Eclipse Foundation Intellectual Property (IP) Policy, every bit of third party content needed to be thoroughly reviewed before it could be used by an Eclipse project. And the reviews were thorough: license scan, provenance check, scan for anomalies, … Reviews of third party content literally took days, weeks, and months. All of that review needed to be complete before the project team could commit any code that made any reference to that third party content.

Update to the Eclipse IP Policy

Tuesday, November 12, 2019 - 11:39 by Wayne Beaton

Sharon Corbett drafted this message that the IP Team has been posting on some of our CQs. I’d like to share it more broadly.

The Eclipse Board of Directors approved changes to the Eclipse Intellectual Property Policy on October 21, 2019. The most significant change relates to how we will perform due diligence of leveraged Third Party Content (Section IV B).

Eclipse Project Licenses

Wednesday, October 23, 2019 - 04:39 by Wayne Beaton

While it’s true that most Eclipse projects use the Eclipse Public License, many Eclipse open source projects use alternative licenses either alone or in combination.

The chart below shows the relative use of various license schemes by Eclipse open source projects:

Revising the Eclipse IP Policy: Third Party Content

Wednesday, October 9, 2019 - 23:07 by Wayne Beaton

The Eclipse Foundation is in the process of making a major update to our Intellectual Property Policy. A big part of this update is a change in the way that we will manage third party content.

Eclipse IP Process: Service Releases of Third Party Content

Tuesday, October 23, 2018 - 03:49 by Wayne Beaton

The primary role of the Eclipse IP Team is to reduce the risks associated with adopting open source software. In broad terms, they ensure that the licenses on content are compatible, that provenance is clear, and that content otherwise unencumbered from a legal point-of-view (strictly speaking, the team does all of this only for Type B requests).

1
2
3
next
last

Eclipse Foundation Blogs

Ian Skerrett (857 posts)
Wayne Beaton (796 posts)
Mike Milinkovich (290 posts)
Benjamin Cabé (131 posts)
Ivar Grimstad (103 posts)
Tanja Obradovic (39 posts)
Thabang Mashologu (32 posts)
Christopher Guindon (15 posts)
Roxanne Joncas (14 posts)
Paul Buck (11 posts)
Frédéric Desbiens (11 posts)
Mikaël Barbero (9 posts)
Jameka Woodberry (9 posts)
Brian King (8 posts)
Hudson Kelly (8 posts)
Denis Roy (5 posts)
Gabriela Motroc (4 posts)
Gael Blondelle (3 posts)
Shabnam Mayel (3 posts)
Jacob Harris (1 posts)
Stephanie Swart (1 posts)
Michael Plagge (1 posts)
Sharon Corbett (1 posts)
Shanda Giacomoni (1 posts)
Paul White (1 posts)

Recent blog posts

Three Good Reasons to Complete the Jakarta EE Developer Survey
Hashtag Jakarta EE #66
Why Java Developers Continue to Rely on Jakarta EE
Open VSX: A Vendor-Neutral Home for VS Code Extensions
Hashtag Jakarta EE #65
Introducing New Che Workspaces on OpenShift
Eclipse Jetty 11 Supports the Big Bang
Meet Adoptium: Open Source Java Runtimes for Enterprises
Support for Asian Communities from the Eclipse Foundation
Hashtag Jakarta EE #64