Progress Reviews

Progress reviews are a fundamental bit of governance that Eclipse open source project teams engage in periodically (generally annually). By engaging in a progress review, an open source project team can push out official releases for a full year. For long-time Eclipse Committers… progress reviews are fundamentally the same as release reviews (the primary difference being that release reviews tend to be aligned with a specific release). Note that specification projects are required to engage in release reviews for every release. The EMO doesn’t tend to think of reviews as pass/fail events. Rather, these reviews are an opportunity for the EMO and PMC to make sure that Eclipse project teams understand their responsibilities under the Eclipse Foundation Development Process and the Eclipse IP Due Diligence Process, and are generally engaging in vendor neutral open, transparent, and meritocratic practices to attract contribution and participation.

Notes

One thing that we forgot to mention in the talk is how to actually initiate a progress review. To initiate a progress review, send a note to EMO and the team will lead you through the process. Note that the EMO does periodically initiate progress reviews on behalf of a project.

• Progress Reviews in the Eclipse Foundation Project Handbook
• Documentation Generator (accessible by committers only);
• The Eclipse Dash License Tool
• Generating SBOM for Eclipse Projects