You may have noticed that there hasn’t been much development activity on CritiqueBrainz lately. Unfortunately, the focus of the MetaBrainz team has been on other projects recently, and for a few years now we haven’t had a developer who has been working on CritiqueBrainz. In addition, we see that there hasn’t been much activity on CritiqueBrainz recently. We’re unsure if this is a chicken and egg situation and that we need to invest into it to get people to use it, or if CritiqueBrainz simply doesn’t fit into the mould of MetaBrainz projects as well as we hoped it would.
Even a small project like CritiqueBrainz requires a significant amount of development effort, inculding applying security updates in software that we use, fixing small bugs that appear, and moderating reviews that are added.
Therefore, we’re asking the community to see if there is anyone who would like to help us with the general maintenance and upkeep of CritiqueBrainz.
Call for volunteer community manager
We’ve had a number of great ideas about ways to increase the number of reviews in CritiqueBrainz. Would you like to help to encourage people to write reviews? This could include things like posting on the forums, organising weeks/months of reviews around a particular theme, or promoting CritiqueBrainz in other community forums.
Call for volunteer moderators
We need volunteers to verify bad reviews that have been reported by members of the community. At the moment this task doesn’t require a lot of work, we get reports very infrequently.
Call for volunteer developers
Are you a developer who would like to work on CritiqueBrainz? We’re interested in finding a developer who knows Flask, postgresql and React to work on bug fixes and new features. We’re happy to support new volunteers on development tasks and helping get you up to speed with the project
Call for compelling features
If you have good reasons why you think that CritiqueBrainz is useful, we’d like to know it. If there is a particular reason why you currently don’t like using CritiqueBrainz, let us know. It’s possible that a small amount of development work could incentivise more people to contribute to the site. We have previously discussed some ideas for improving CritiqueBrainz, but as mentioned before, we haven’t had much developer time available to make these changes.
What happens if we don’t find anyone?
Unfortunately, if we don’t find anyone to help with the ongoing maintenance of CritiqueBrainz, we may have to shut it down temporarily, or disable new reviews until we have the resources to put towards the project.