When Research Project teams learn Open Collaboration
summary
Shows how research consortia (often 3–4 year projects, sometimes ~40 partner orgs) move from scattered tools to a reproducible workspace using tuleap.eclipse.org, with Git integration, Jenkins hooks, Kanban boards, test management and linked traceability from requirement → commit → test. Describes PDP4E (GDPR tools) bootstrapped on Tuleap, initial contributions arriving after ~12–18 months, templates and an Eclipse Research Labs repo that let teams publish code and pass IP checks, and reports that the approach speeds onboarding and sustains collaboration.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:35Software Development Is Not Really Rocket Science
- 2:26Tips Not To Be Efficient
- 2:59To Share Only Code
- 5:02The Secret Recipe to for an Effective Team Collaboration
- 6:56Kanban Board
- 9:47The Traceability Notion
- 10:25Traceability
- 12:05Garrett Code Review
- 15:39What Is the Research Project
- 24:33Document Management
related talks
32mSuccess stories of open source collaboration in the Eclipse Cloud Dev Tools ecosystem
12mBuilding Bridges Between Academia, Industry and Open Source
31mDevelopment Process 101
01h 21mOpen Source Best Practices at Eclipse Foundation
28mEMO & YOU
47mPolicing Open-Source Projects at Scale
50mEclipse Apoapsis - Open Source based Software Composition Analysis at scale- 47mPolicing Open-Source Projects at Scale