Have there been any recent efforts to collect high-level statistics about why
and how people use MusicBrainz? For example:
- Why do editors add to or edit MB?
- What do people do with data from MB?
- Do most editors add missing releases from their own personal music collections, or add data about their favorite artists, or …?
As I become a more-active MB contributor, I’m interested in knowing more about how other people use the site to know how common my use cases are, in order to know how useful it is for me to enter data or suggest (or contribute?) changes on the server side.
Work in progress MB User Survey discusses a 2017 survey (announced at MusicBrainz User Survey – MetaBrainz Blog) in which 1,200 responses were collected. The survey closed long ago, but I think there’s a draft of the questions at MusicBrainz User Survey - Google Docs.
I haven’t been able to find a summary of the survey’s results, though. The latest reference I’ve seen was [<entity>:<mbid>|<name>] links - #9 by yvanzo, a comment from July 2018 saying that the results were being used to set priorities for development.
It’s not clear to me whether the 2017 MB survey was trying to collect answers from a representative sample of users (I wasn’t following the discussion forums or the blog at the time, so I didn’t hear about it then). Was it also advertised on the main MB landing page?
I’ve found the annual user survey results published by the Go (programming language) team to be quite interesting:
- Go Developer Survey 2021 Results - The Go Programming Language
- Go Developer Survey 2022 Q2 Results - The Go Programming Language
In addition to advertising the survey via things like blog posts, I think that the Go team randomly prompts a subset of users of a popular IDE plugin to try to collect responses from a (somewhat) representative sample.