Eclipse Foundation
The Belgian international nonprofit association supports an ecosystem of reusable software projects. Eclipse JDT Core is the scoped developer-tool example, not a score for every member company or product.
90% of weighted axes reviewed. A mechanism hypothesis, not proven effectiveness or a donation recommendation.
Who this work enables
Tools & support for charities: Shared development tools, IP administration and contributor infrastructure can reduce duplicated technical and institutional work by public-interest developers.
Open-source evidence · license checked
- Eclipse JDT Core — EPL-2.0 license file. Organization’s role: steward.
Inspected the named core repository’s EPL text and README. The foundation provides an institutional home and services, while contributors develop the tools; other Eclipse projects, specifications, dependencies and support promises are outside this check. License-file snapshot:e23ece2c852415800ac224b74ede6c5849f6f88d.
License checked 2026-10-27. This is not a security audit, proof of current support or effectiveness, or a promise of free hosting. A sponsor or steward is not necessarily the sole developer. Unchecked profiles are not evidence of closed code. No extra score points are added.
Humanity’s Checklist source match
Gatekeepers · Coordination — editorial, partial alignment.
Reusable tools and common project institutions can lower vendor barriers and coordinate development. This partial mapping does not establish neutral outcomes or community control of downstream systems.
Explicit checklist adoption: not verified. A mechanism match is not an affiliation, endorsement, evidence of effectiveness or a scoring bonus. Read the practice.
Focus classification: 2026-10-27. Based on the organization’s dated official sources below; earlier axis-review dates are unchanged.
Compare alternatives for a funder →
The proposed pathway
Provide shared governance, intellectual-property processes and development infrastructure
Six dimensions, with rationale
Structural depth
3 / 4Shared governance, IP processes and infrastructure can lower institutional barriers to collaboration rather than fund one proprietary software purchase.
Institutional reach
4 / 4Reusable development infrastructure can support many public-interest applications and organizations alongside commercial users.
Durability
3 / 4Public source and governance institutions can persist, while dependency, interoperability and maintenance work continues.
Scalability
4 / 4Common developer tools and support processes can be reused across projects; integration and institutional adoption still cost resources.
Funding additionality
UnreviewedNo current marginal foundation funding bottleneck or counterfactual against member and volunteer contributions was audited.
Community agency
UnreviewedMembership and committer processes do not establish binding rights for communities affected by systems built with these tools.
Evidence and selection
Organization reported; current primary mechanism sources inspected; named repository and license file checked
Illustrative inclusion to examine this mechanism. Inclusion is not an external recommendation or a verified comparative ranking.
A testable next question
Do nonprofit teams using supported Eclipse infrastructure sustain interoperable applications and useful exit options at lower lifecycle cost than comparable teams relying on proprietary development environments, including integration and support?
Review confidence: Moderate for documented design; low for systemic attribution. Eclipse Foundation AISBL’s nonprofit stewardship and core-support model, with Eclipse JDT Core as the scoped example; not a combined rating of every related legal entity, member or hosted project.
What remains uncertain
The current legal FAQ identifies Eclipse Foundation AISBL in Belgium and continuing US and German entities; they are not counted separately here or presumed to have identical tax treatment. JDT Core’s EPL-2.0 license check is not a blanket statement about all Eclipse projects, dependencies or specifications. The README emphasizes volunteer development, not sole foundation authorship or a support guarantee. Industry collaboration does not itself establish public-interest outcomes, independence from member priorities or affected-community power.
Sources to inspect
- Eclipse Foundation: current mission and core services ↗
official · checked 2026-10-27 - Eclipse Foundation: Belgian AISBL and related legal-entity boundaries ↗
official · checked 2026-10-27 - Eclipse JDT Core: inspected repository ↗
official · checked 2026-10-27 - Eclipse JDT Core README: tools, volunteers and project links ↗
official · checked 2026-10-27 - Eclipse JDT Core: inspected EPL license text ↗
official · checked 2026-10-27
Propose a sourced correction →
Axis review: 2026-10-27 · weighting method v0.2 (2026-10-26) · Method, conflicts and coverage