State of MetaBrainz 2026

I joined MetaBrainz as Executive Director in August this year, 7 months after we lost Rob. This is the written summary of the talk I gave at our October summit in Barcelona: where we stand, what worries me, and what I plan to do in 2027.

A year of loss, and what held

Losing Rob this year touches everything in this report. What I want to recognize is how people responded:

  • The team kept the lights on and the engines running.
  • The community kept editing, even through the outages.
  • The board focused on funding so we could keep going.

I wasn’t here yet for most of that, so the credit belongs to all of you.

Who I am

I started in August, and I’ve spent the months since learning how everything works. My first focus is infrastructure and the funding it requires. My second is raising money more broadly.

I’ve worked in open data, open standards and open source since 2004, mostly in open government. I care a great deal about privacy: I served on the board of EFF-Austin for 12 years and was a legislative liaison for the ACLU on technical issues. I also have a background in AI, which I know is a sore subject here but this means I can help. I have always fought for artists and creators, and I think you’ll find we’re in sync on the realities we face.

The money

At the time of the summit, income for 2026 stood at 300K, which put us 55K behind for this time of year. We normally bring in about 400K a year, and Nicolás (reosarevok) and I think we can still get there by year-end.  But because of increased infrastructure costs we still have a shortfall for this year.

What has been done:

  • The board has spent the year renewing supporter contracts.
  • We are creating new kinds of contracts, because ListenBrainz is used very differently from MusicBrainz and our existing tiers don’t fit.
  • I’ve been researching what comparable data sells for. The finding: our top tier is the industry standard price. Every tier below it is priced well under that, on purpose, to support small businesses and independent creators.

What is pushing costs up:

  • Infrastructure. AI agent traffic means we need more capacity, and AI demand has raised hardware and networking prices.
  • The summit. Flights cost about three times what they did, especially from the United States.

We are also building a CRM using Twenty, which is open source and self-hosted. It brings together what lives on our website and in our accounting, helps us track privacy requests, and lets us send fewer routine emails and more useful ones, such as yearly tax letters to donors.

The CRM matters for a reason specific to US nonprofits: we have to show the IRS that our support comes from a broad public, and individual donations count toward that. It is also what lets us write to our users to ask for support, which we are planning on doing for the first time soon.

The team

This is my view as the new person, not a measurement.

What I see is an extraordinarily dedicated group. It’s why I took this job: I wanted to work with data nerds. The volunteer engagement is remarkable, from the userscripts and apps people have built to the number of edits made through thick and thin. The team is self-motivated and self-organizing. Everyone wants to carry Rob’s legacy forward, and I am in awe of that.

I also see that people are tired, and I’m worried about burnout.

  • Too many roles are unfilled. Teams of one or two people are not enough.
  • Coordination could be better, which is why we worked on leads and roles at the summit.
  • Our infrastructure needs serious attention. With it in better shape, we’d be more comfortable opening up to outside contributions.

Fixing this takes money, which is why so much of this post is about funding.

2027

I’m preparing two budgets for the board.

The conservative budget covers:

  • Following up with supporters and past donors through the CRM.
  • Two summits: one in person, and a Virtual Summit in spring with rooms and topics the whole community can join.

The aspirational budget adds:

  • Edit-a-thons, code-a-thons and voting-a-thons attached to existing events, starting with an edit-a-thon in the fall. Picture a session the day before a metal festival or a classical music festival, where our editors go and find their people. Sponsorship for events comes out of companies’ marketing budgets, which are far larger than their donation budgets.
  • A UX summit to review our interfaces together.
  • Grants. I’ve found more than 30 to apply for, ranging from 250,000 to 5 million. Many EU heritage preservation grants fit us, because archiving is what we do. AI companies also fund nonprofits affected by AI traffic, and I intend to ask.

Two more things are on my list:

  • Getting our name out to the right people. When I took this role, I kept hearing “Oh, that’s still around?” from people who used to edit. I don’t want mass publicity. I want to reach the people who are passionate about music and data.
  • The website. It needs to explain who the team is, what a nonprofit open data project means, why human-verified data matters and why our editors are the reason it’s good. We also need better onboarding: tutorials, videos and a sandbox.

Thank you

Rob and I are very different people, though I think we shared the same fundamental views. One difference is that I do the money thing. Another is that I will resist getting involved in the code and we manage differently, which means we’ll need some new ways of communicating.

Thank you for everything, and for your patience while I fill some brightly colored shoes.

Silona Bonewald

Executive Director, MetaBrainz Foundation

Watch the talk

Picard 3.0.5 released

Picard 3.0.5 is a maintenance release for the recently released Picard 3.0 with fixes for reported issues. This release fixes issues with saving the order of cover art providers, manually set artwork for multiple files not being saved, a potential crash when logging out of your MusicBrainz account and many more.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.13 please see our detailed release announcement for Picard 3.0.

Thanks a lot to everyone who gave feedback and reported issues.

Continue reading “Picard 3.0.5 released”

Picard 3.0.4 released

Picard 3.0.4 is a maintenance release for the recently released Picard 3.0 with fixes for reported issues and updated translations. This release fixes crashes on macOS with some language settings as well as a potential crash when updating the plugin list. It also addresses a regression where the match indicator for files would indicate a low score for newly tagged files and an issue where Picard would detect a WebP file as a WAVE audio file.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.13 please see our detailed release announcement for Picard 3.0.

Thanks a lot to everyone who gave feedback and reported issues.

Continue reading “Picard 3.0.4 released”

Picard 3.0.3 released

Picard 3.0.3 is a maintenance release for Picard 3.0 with fixes for reported issues and updated translations.
This release fixes a crash when switching color themes, a crash when loading a release from an ISRC lookup, metadata issues in the Album Pane when multiple files match a track, and problems saving tags to WAV files with invalid chunk sizes, along with several plugin, cover art, and sorting fixes.
It also brings a few small improvements, including Enter-key navigation in the scripting documentation search, better recording-match scoring to avoid false positives on gross track-length mismatches, and normalization of lowercase or unhyphenated ISRCs.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.13 please see our detailed release announcement for Picard 3.0.

Thanks a lot to everyone who gave feedback and reported issues.

Continue reading “Picard 3.0.3 released”

Picard 3.0.2 released

Picard 3.0.2 is a maintenance release for the recently released Picard 3.0 with fixes for reported issues and updated translations. This releases fixes a crash in the Setup Wizard if Picard was packaged with the automatic update check disabled and several color theme related fixes.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.13 please see our detailed release announcement for Picard 3.0.

Thanks a lot to everyone who gave feedback and reported issues.

Continue reading “Picard 3.0.2 released”

Picard 3.0.1 released

Picard 3.0.1 is a maintenance release for the recently released Picard 3.0 with fixes for reported issues and updated translations. In particular this release fixes issues on newer macOS Tahoe and Golden Gate, a possible crash when updating from Picard 2.x and the picard-cli utility in the Windows package.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.13 please see our detailed release announcement for Picard 3.0.

Thanks a lot to everyone who gave feedback and reported issues.

Continue reading “Picard 3.0.1 released”

Happening NOW: AMA with Silona Bonewald, MetaBrainz Foundation Executive Director

Silona Bonewald, our new Executive Director, is NOW hosting an AMA (Ask Me Anything) in this forum thread.

Please respect the code of conduct, as you always do!

You are welcome to post questions in the thread later, and Silona will do her best to answer them when she has the time. We will close the thread after a couple of days – though of course the door remains open to chat with the MetaBrainz team any time in the future!

You can find more information about Silona on our Executive Director announcement post.

Picard 3.0 released

The Picard team is happy to announce the new major version 3.0 of MusicBrainz Picard, now available to download. MusicBrainz Picard is the official tag editor for the MusicBrainz database and helps you get your music collection sorted and cleaned up with data from MusicBrainz.

An image of a mock software cardboard box, showing "MusicBrainz Picard" as the title. There are two worn-out looking stickers visible on the box, one saying "Complete Tagging Solution", one "Community Support".

Beside the box there is a pink / orange circle with the text "Version 3".

This release brings many changes, including an upgrade to Qt6, a completely new plugin system, several improvements to the user interface, cover art processing, ISRC submission and many more. More details below.

Continue reading “Picard 3.0 released”

Our editors: vzell

This is part of a series where we talk to some of the amazing editors that have cracked one million MusicBrainz edits and qualified for super special (lousy) shirt plan.*

These users have donated substantial amounts of their time to improve open music data, enriching open-source knowledge and culture for billions of people. Let’s find out what makes vzell click. And click and click and click!

Continue reading “Our editors: vzell”