Do our development tools need a refresh?
summary
Ran surveys and interviews across Fedora and Red Hat to map real workflows and pain points, finding big variability and concrete bottlenecks: painful backporting and rebasing, 6-hour kernel builds and multi-day test suites, flaky CI with inconsistent results, and fragile Koji buildroots. Proposals and prototypes include using cached buildroots, containerized build/test, specfile generation/templating, and automation services (packet/source-gate) to prune manual steps and make branching, rebuilds and CI gating repeatable and faster.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:05DO OUR DEVELOPMENT TOOLS NEED A REFRESH?
- 0:37TOMAS TOMECEK
- 27:43WHAT IS FIXING THIS?
- 34:51NOW WE NEED YOUR IDEAS!
- 46:25WHAT'S NEXT?
related talks
14mUsing packit and testing farm for CI/CD and automation in an upstream project
48mIntegrating upstream projects downstream
27mDeveloper Experience: It’s Time to Start Complaining
09mInterview
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
52mConfronting Common Productivity Hurdles in Modern Software Development
47mHow to win in software development with tighter feedback loops
45mFinding problems quickly in a quickly evolving opensource project