Notes from #MetaBrainz Meeting 2018-06-18

[Freso]

MetaBrainz Meeting 2018-06-18

Meeting start: Making sure you're not a bot!

Agenda

• Reviews
• Amazon cover art
• Quick question about instrument ticket decisions

Reviews

@dragonzeron

Making sure you're not a bot!

@dragonzeron

I have been working on some new albums as well as removing wikipedia links and with that I was going to ask is it possible to look up removal of wikipedia links on types of edits cause I looked them up but I cant seem to find it directly unless its removing relationship in general so if its not a thing could we look into this

@little_rsh

Making sure you're not a bot!

@little_rsh

Last week I completed the work of importing the MusicBrainz metadata in acousticbrainz and worked on param’s review and opened the PR’s related to improvements in the code and would send the PR for the next work of updating the MB metadata in AB probably by tomorrow!

@Rob

Making sure you're not a bot!

@Rob

last week’s overhead nonsense: chasing payments, finding new insurance, wrangling documents from california to spain and other assorted BS.
and I spent a fair amount of time thinking about and working on the new conflict resolution policy.
we’re a tricky bunch that requires some tricky thinking.
also, lots of backup sketching on the SOLR stuff as well as PR review for MSB and LB.
and I spent tuesday installing a new door lock in the office. this one doesn’t suck, is all scifi and will let us manage the summit easier.

@ApeKattQuest_MonkeyPython

Making sure you're not a bot!

@ApeKattQuest_MonkeyPython

In continuing my work with INST-647 et al. idiophones, This week I’ve done quite a lot more reordering.
I’ve deleted unnecessary links and added plucked idiophones and thus reordered stuff with the other idiophones.
Then there was Drums vs. drumset - #19 by reosarevok (which @reosarevok might talk more about)
so with that I also added A FEW choice aliases to “Drumset” :​​D :
Percussion instrument “drums (drum set)” - Aliases - MusicBrainz
Then there was INST-371 which was a fustercluck of epic proportions..
Ghaychak - Wikipedia was two instruments in one, and unrelated. So I proceeded to edit both
Wikidata, ghaychak - Wikidata creating ghijak - Wikidata
Wikipedia creating Ghijak - Wikipedia AND commons to organise links, “MusicBrainz var bare toppen av kransekaka!” as the norwegian saying (ifr, "top of the iceberg)
In that vein, I would really, really really appreciate if anyone speaking german could fix the german WP pages too: since While I could guess based on what I know in Norwegian, I really don’t speak this language and I don’t feel comfortable moving parts to a new page based on Google Translate and my “torsk” (tysk + norsk).
(The other page I’m certain is mixed is Qişek — Vikipediya is in Azerbaijani, if anyone knows it to feel comfortable in it :'D)
Finally any other of the linked wiki’s in ghaychak - Wikidata anyone who speaks languages can confirm or deny they talk of both instruments or no, would be so much appreciated <3

@reosarevok

Making sure you're not a bot!

@reosarevok

This week I mostly edited and did support and helped @ApeKattQuest_MonkeyPython with drums
And @samj1912 with search I guess

@samj1912

Making sure you're not a bot!

@samj1912

this week finally announced solr beta
the blog if anyone wants to read
Making sure you're not a bot!
week was mostly spent on getting solr prod ready
making it keep up with reqs/s other optimizations etc etc
fixed a LOT of things this week
opening up solr to beta also allowed our SOLR ticket tracker to get a bit more active
and I have been chasing inconsistencies in old search server for the past 2 days
they are mostly fixed and I will be announcing a consistent search syntax soon
apart from that, currently working on making the index more efficient, removing un-needed parts
and adding other things that were requested - aliases for rg,releases, recs. and being able to search for accented chars and punctuation
oh, also made some patches upstream to telegraf to fix our solr metrics

@chhavi

Making sure you're not a bot!

@chhavi

I added a few more components to the system. Will do the same the coming week

@bitmap

Making sure you're not a bot!

@bitmap

was ill last week so I didn’t make huge progress on any PRs, but I helped migrate containers off (and then back onto) serge, tried setting up a rabbitmq cluster (but ran into a snag), and code-reviewed @chhavi’s work and the LB user ID stuff (and probably not helping :))

@Freso

Making sure you're not a bot!

@Freso

I reviewed @samj1912’s blog post about the search beta and handled some reported editors and was otherwise around and about.
@FresoBot keeps chugging along.

@Leo_Verto

Making sure you're not a bot!

@Leo_Verto

I updated my GSoC timeline, did my review, started work on building SpamBrainz’ API and started working on comparing the spam data to the live one.

@yvanzo

Making sure you're not a bot!

@yvanzo

Last week, I submitted the first evaluation of @Leo_Verto’s project SpamBrainz to GSoC.
I finished reviewing bitmap’s PR and worked on React rewrite of editor account forms and small recent issues.

@Zas

Making sure you're not a bot!

@Zas

most of the week working setting up haproxy/solr cloud/metrics/grafana etc..
plus a lot load tests on solr
which should be ok for prod
also dig reason of performance differences betwen identical VMs…
found out it comes from IBRS cpus, asked hetzner about this shit
no answer yet
plus usual upgrades, and fixed disk space issue on discourse server

@iliekcomputers

Making sure you're not a bot!

@iliekcomputers

I did work on all three projects this week.
Did some work on LB restreaming our data to BigQuery, also kinda sorta started writing code for stats with the new schema on BQ, but need to discuss it more. Also, trying to import musicbrainz row ids into LB.
Finally merged a bunch of Pull Requests on CB and deployed them to beta. These included some schema changes that I had been putting off for long. Also, made a post about it on discourse. (go take a look). Also, been working on allowing users to delete comments.
New features on beta.critiquebrainz.org!
Reviewed and merged @little_rsh’s PR on AcousticBrainz, we’re making progress on her project, i think. Still need to find a way to test this with prod data. I think import will probably be slow, but I’d like to see how slow. I think it’ll be best to do after AB moves to hetzner?
Also, MessyBrainz code review: I read the clustering artists PR, it is a bit to take in. Will post comments today.

@kartikeyaSh

Making sure you're not a bot!

@kartikeyaSh

Last week I created a PR for LB-372 and wrote tests for the same. I did start working on creating release clusters, I’ll create PR for it in a day or 2. This will conclude part-1 of the project. Now things seem clear to me and I believe I can speed up the work and get part-2 done at a faster pace.

@shivamt

Making sure you're not a bot!

@shivamt

Last week I completed import process.
Presently cleaning up and working on commits.
Out of three classes, two dumps can be handled now.
There needs some work on the mapping and extraction of as much data as possible, which requires some manual working.
I have started work on tests and improving dumps mapping.
I have also started looking into second phase work onwards.

Amazon cover art

Making sure you're not a bot!

@Freso

Last week dragonzeron asked about getting our Amazon cover art fixed for some releases, which reminded me of a discussion we had at a meeting ages ago, about dropping Amazon cover art support entirely in favour of only displaying CAA images on MusicBrainz.
Sadly, I couldn’t find this meeting in our chatlogs. :()
This was discussed at some length in the forums since last meeting though, and it seems like there is a fair amount of our editors who wants to keep it for now:
[WARNING: Old out of date 2018 post. Skip to bottom] Keeping or dropping Amazon as a CAA fallback on MusicBrainz.org
So unless anyone else has something to add, I move for not doing anything for now.

No one had anything to add, so we’re not doing anything for now (in this regard).

Quick question about instrument ticket decisions

Making sure you're not a bot!

@ApeKattQuest_MonkeyPython

In addition to the things I stated in my review, I also closed some tickets as invalid/nofix as they weren’t possible to find any information about, and noone seemed to care/be interested.
I was wondering if I could, in the vein of the “decision required” for certain tickets we did some time back, occasionally, that is //occasionally// ask in the meeting about some instrument tickets I feel I need more consensus/feedback about before deciding?
How does people feel about that? yay or nay?
this would not be an often thing (I have one for next meeting perhaps but)

@Rob and @Freso were in favour and no one else voiced an opinion, so motion was carried.

@ApeKattQuest_MonkeyPython noted they would bring up INST-24 for next meeting.