Wayne Beaton

Eclipse Collections is a wonderful library for Java developers that provides a rich… uh… collection (set?

Originally posted in the the February 2019 Eclipse Foundation Newsletter.

Originally posted on January 27, 2020 The Eclipse Foundation Development Process (EDP) says nothing about how teams should organise.

The 2022 update to the Eclipse Foundation’s IP Policy, approved by the Board of Directors in June 2022, resulted in the following changes: The Eclipse Public License is no longer special.

All Eclipse open source projects are required to operate in an open and transparent manner.

If an Eclipse open source project team wants to include the community in a vote to, say, decide what functionality to include in the code base or decide whether or not they’re ready to do a release, that’s entirely up to the project team.

The Eclipse Foundation community awards are returning once again!

The Eclipse Dash License Tool identifies the licenses of content.

As a member of the Eclipse Foundation, you already know the value of making a project open source.

Here’s a scenario: you work for an organization that contributes to open source and you’ve hired a developer to work on your favourite open source project.

Originally posted on October 26/2017.

The Eclipse Foundation Development Process (EDP) describes a release as anything that is distributed for adoption outside of the committers of a project (effectively, if you stamp something with a version number and tell the general audience to download i…

Scientific progress goes “boink”?

The Eclipse Foundation community awards are back for 2021!

Intellectual property management is important for Eclipse projects.

Dropping barriers to open up opportunities for contribution is a critical activity for Eclipse open source projects.

The Eclipse Foundation has a policy regarding the resolution and responsible disclosure of identified vulnerabilities.

The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority.

Good news!

Originally posted on August 2, 2017 For many open source organisations, open means the same thing as transparent: open as in open book.

The hard parts of contributing to an Eclipse open source project are the same hard parts that you’ll have with any open source project.

Originally posted on January 13, 2012 The Eclipse Foundation Development Process (EDP) defines–in its section on principles–three open source rules of engagement: Openness, Transparency, and Meritocracy: Open – Eclipse is open to all; Eclipse provides the…

Eclipse open source project teams are required to maintain a record of intellectual property contributions.

One of the benefits of hosting your open source project at the Eclipse Foundation is the Eclipse Foundation’s Intellectual Property (IP) Policy and the IP Due Diligence Process that supports it.

Revised on September 22/2020 There’s background information about this post in my previous post.

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.

Revised on September 22/2020 The Eclipse Foundation’s board of directors approved an update to the Eclipse Foundation’s Intellectual Property (IP) Policy in October 2019.