Where the open-source database community meets: Secure your spot at PerconaLive.com
Contact Us

Knowledge
Base

Guides, blogs, forums, and learning resources for the open source database community.

Get involved

Percona’s software is open source. That means the code, the documentation, the bug tracker, and the forum are all places where you can contribute — and where contributions actually shape what ships.

Whatever your starting point, there’s a real way in. Pick the one that matches the time and energy you have right now. None of these paths is more valuable than the others.

Answer questions on the forum

The Percona Forum is where DBAs and developers go when something’s gone wrong at 2 a.m. If you’ve solved a problem before, your answer is worth more than any blog post — because someone is searching for it right now.

You don’t need to be an expert across the stack. Pick a topic you actually run in production and watch that category.

Submit a pull request

Code contributions are welcome across every Percona repository — fixes, features, tests, documentation patches. If you want a curated entry point, the Newbie-labeled tasks in Jira are scoped for a first contribution.

Fork, branch, commit, and open a PR against the relevant repo. Keep the diff focused. Reference the issue you’re closing. After the PR is open, drop a note to community-team@percona.com so we can give it visibility.

Open a GitHub issue

If something’s broken, behaves unexpectedly, or the docs don’t match reality, file an issue. A clear bug report with reproduction steps, version numbers, and the actual vs. expected behavior is one of the most useful things you can give a maintainer.

Find the right repository under github.com/percona and open an issue there. If you’re not sure which repo, ask on the forum first.

Start here if you’ve hit a bug or a doc gap and you’ve got 15 minutes.

Write a blog post

If you’ve debugged something hairy, run a benchmark, migrated between versions, or have an opinion about how to operate a database at scale — write it up. The Percona Community blog publishes technical posts from contributors. Follow the publishing guide or send a draft to community-team@percona.com.

Send feedback

Direct feedback on a release, a feature, a workflow, or this community itself goes to community-team@percona.com. Tell us what’s working, what isn’t, and what you wish existed. We read all of it.

Community forums

The Percona Forum is where DBAs and developers land at 2 a.m. when something’s broken. If you’ve solved it before, answer — someone’s searching for it right now.
Go to forum

Code

Fork a repo and open a pull request — fixes, features, tests, or doc patches all count. Questions first? Ask in Slack or email community-team@percona.com.
GitHub

Documentation

Improve a guide, fix an outdated line, or flag a gap so the next person finds answers faster. Not sure where it lives? Ask in the forums.
Percona Docs Contribute docs

Contributors get acknowledged in release notes, in the contributors directory, and occasionally with Percona swag. That’s a side effect, not the point — the point is that the software gets better when the people who use it shape it.

Questions about any of the above? Email community-team@percona.com.

From the wider community

Articles and videos about Percona software published on external blogs and YouTube — shared by users, customers, and database enthusiasts.

Wrote a post or recorded a tutorial? Publish it on your platform and add it to our collection.

Events

Organize a local meetup, or join our conferences and online sessions. Connect with the practitioners running these databases in production and share what you know.
See events