Open Source Best Practices at Eclipse Foundation
summary
Clear definition of success: real users, external contributors, and a growing, vendor‑neutral community. Practical moves include public daily commits, SPDX identifiers and reuse.software for unambiguous licenses, and SBoMs plus dependency tracking to detect license or vulnerability impacts. Automation with Jenkins and GitHub Actions gives quick previews and nightly full tests. Governance uses earned commit rights, DCO/CLA options, and open meetings; metrics show a 12‑day median review time and 32‑day median issue age, with median four contributing organizations per project.
AI-written summary · about
chapters (5)
- 0:00Introduction and OCX Overview
- 2:00Sponsorship Opportunities
- 3:30Wayne Beaton – Running a Successful Open Source Project
- 36:50Boris Baldassari – Open Source Best Practices in Practice
- 1:17:45Q&A and Raffle Giveaway
related talks
27mOpen Source Health - A Crisis of Expectations
16mA Journey of Contribution and Collaboration in Open Source
32mOpen Source - A Journey of Contribution and Collaboration
50mRunning a Successful Open Source Project
38mHow To Be a Responsible Open Source Citizen
23mManaging the unmanageable: community driven projects at Eclipse Foundation
37mThe Eclipse Development Process for Committers
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance