#bookbrainz

Tarun_0x0 (IRC): 15 file changes really isn't that bad for reviewing, all in all. Fewer is better, but it's only from 30 onward that it becomes really unwieldy.

Hi there

I am Mohamed Ali, interested in open source and love books and their world. So I am trying to contribute to you and I have created an issue my first PR was been yesterday and I have a lot of issues to solve. so I want to know if I can resolve some of these issues and make PRs before the previous reviewed or not.

For posterity,I answered in private but copying it here:

Hello, Yes you can start working on a different issue while waiting for review on another, especially considering how it might take me a bit of time to get to the review

Yeah, I have seen it Thanks again, and apologies for this noise

Hey monkey! The Monday meetings look cool. Can I also take part, or are they exclusively for the official team members?

Tarun_0x0 (IRC): You're absolutely welcome to take part! Drop reosarevok a line on the #metabrainz channel asking to be added to the list for next week

thanks a bunch !!!

hey yvanzo, are there any specific strategies we use for MusicBrainz to enhance the relevance (precision and recall) of search results to the query ? can you point me to some code I can take a look at please.

Hi Tarun_0x0, there are but it is also known that it can/should be further improved: https://github.com/metabrainz/mbsssss

See more particularly the default request parameters such as https://github.com/metabrainz/mbsssss/blob/mast...

And the corresponding documentation: https://solr.apache.org/guide/solr/latest/query...

also i got to know that previously in BookBrainz, there was an attempt to shift to Solr for search functionality, but the search results were not as good as with Elasticsearch. due to the lack of an equivalent for multi-match queries in Solr, even after boosting some fields. Now, I'm curious, is the situation similar for MusicBrainz search, or do

we have better results compared to BookBrainz' Elasticsearch there?

yvanzo .

oh i noticed this was 3 years ago may be not the case now