From Neglected to Community Driven Reviving Percona Toolkit
summary
Percona Toolkit goes from neglected to actively maintained: outdated Perl/Bash/Go tools get modernized, automated vendor libraries (update-modules) are unbundled or handled to prevent overwritten fixes, and a minimal contributor guide plus clearer docs reduces broken PRs. Regression tests run locally and as regression tests on Jenkins across supported Percona Server versions (5.7, 8.x), community PRs are reviewed quickly and credited in release notes, and incremental fixes prove the rebuilt process works for ongoing contributions to Percona Toolkit and Perl/Bash/Go tools.
AI-written summary · about
chapters (13)
- 0:00Percona Toolkit revival intro
- 2:10History and decline
- 5:19Engineering couldn't maintain
- 7:50Taking ownership
- 10:16Challenges of Perl tools
- 13:50Simplifying contributions
- 16:43Reviewing contributions
- 19:56Automating tests with Jenkins
- 21:46Improving code quality
- 24:13Why feedback matters
- 25:18Thanking contributors
- 25:40Engineers supporting project
- 26:25Future plans and discussion
related talks
53mState of Open Source Databases and how Percona Contributes
28mStay ahead of MySQL operational problems with Percona Toolkit and PMP plugins
39mThe Future of Percona Products
12mContribution Over Control Open Source Responsibility in PostgreSQL
39mMaintaining a big open source project: lessons learned
30mHappy Developers, Healthy Modules - Together We Can Do This
37mOpen Source Maintenance
57m"Potential"