The Path to Code Contributions in MariaDB Server

I have been working for the MariaDB Foundation as the Chief Contributions Officer for a couple of weeks and it is fantastic being part of the MariaDB family again. Part of my job is to help the community massage pull requests into something that we can merge. I am, however, finding that one of the worst parts of my job is having to say “no” to contributions that clearly took a lot of time and effort on the part of the developer.

Contributions could be turned down or at least will require changes for a number of reasons.

Progress on Pull Request Processing

In his blog post “On Contributions, Pride and Cockiness ” in May, MariaDB Foundation CEO Kaj Arnö spoke of a renewed focus on MariaDB Server pull requests. Processing community pull requests in good time is a key part of our mission, but we’d been falling behind, and receiving justifiable criticism. At the time of that article, there were 167 open pull requests, with many open for far too long, and contributors were frustrated.

We set out two end goals:

  • Reduce backlog of open pull requests
  • Motivate contributors to make more contributions

There’s been no noticeable uptick in contributions since then, but we’ve made good progress in reducing the number of open pull requests. …

On Contributions, Pride and Cockiness

At MariaDB Foundation, we are proud of MariaDB Server getting plenty of contributions. But we don’t want to get cocky, so here is an update about where we stand, and what we want to make happen.

First, we have shown our contribution pride in several places. On 15 February 2019, I tweeted

Repeating: On code contributions, #MariaDB beats #MySQL 1009 to 247: We have over a thousand (1009) closed pull requests on GitHub (and 179 open), MySQL has 247 closed (1 open).

In our Annual Report 2018, we spent several pages, talking about pull requests and patches, showing code contribution statistics. …