# GSoC 2026 : Interest in Daemon for correcting out-of-sync cover art metadata

**URL:** <https://community.metabrainz.org/t/gsoc-2026-interest-in-daemon-for-correcting-out-of-sync-cover-art-metadata/814337>\
**Category:** MusicBrainz\
**Tags:** gsoc-2026, musicbrainz\
**Created:** [March 5, 2026, 7:01am UTC](https://community.metabrainz.org/t/gsoc-2026-interest-in-daemon-for-correcting-out-of-sync-cover-art-metadata/814337 "2026-03-05T07:01:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZeyadH](https://community.metabrainz.org/letter_avatar_proxy/v4/letter/z/b5e925/32.png) [@ZeyadH](https://community.metabrainz.org/u/ZeyadH)\
**Post date:** [March 5, 2026, 7:01am UTC](https://community.metabrainz.org/t/gsoc-2026-interest-in-daemon-for-correcting-out-of-sync-cover-art-metadata/814337/1 "2026-03-05T07:01:57Z")

</div>

Hi everyone, and @Bitmap

I’m Zeyad. I’ve been diving into the MusicBrainz server codebase recently and just submitted my first PR ( **MBS-9615** ) to fix the subscription filtering logic in reports. It was a great challenge to get familiar with the Perl and SQL setup!

I’m particularly interested in the GSoC 2026 project: **“Implement a daemon that corrects out-of-sync cover art and event art metadata on [archive.org](http://archive.org)”**.

I’ve already started studying the `artwork-indexer` repository and the **IMG-129** ticket to understand the current synchronization architecture and identify where the gaps are.

Since I’ve already tackled one “good first bug,” are there any other specific areas or related issues you’d recommend I look into to get a better handle on the Cover Art Archive logic before the application period opens?

Looking forward to your thoughts!