Notes from #MetaBrainz Meeting 2018-06-25

[Freso]

MetaBrainz Meeting 2018-06-25

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• DR: INST-24

Reviews

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

I finally put Solr to a close this weekend, releasing it to beta, fixing the initial bugs reported. The punctuation search proved to be a pretty difficult problem to fix, but after 10 files, and 3 Java factories later, I finally managed to solve it. It basically involved modifying some of Solr’s tokenizers and filters.
Apart from this worked on some documentation and another blog and some MBS fixes to accommodate solr along with ws1.
You can find the new blog here
Releasing our new Solr search infrastructure – MetaBrainz Blog
Apart from that, as you can tell from @Freso posting this, I am on a vacation to nowhere enjoying some time away from technology.

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

not much this week, i was travelling, so just usual supervision and security upgrades

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I fixed some encoding issues in hte oauth and digest auth endpoints, MBS-9744 and MBS-8334. I guess the former was causing peoples usernames to get messed up in external projects
and finally got back to my other prs, reviewed/tested @chhavi’s design work more
worked on getting @reosarevok’s genre’s patch merged
I also contacted these riskanalytics people and got them to remove some IA domain from their malware list, which was blocking cover art for people using uBlock Origin

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

I mainly worked on React rewrite (user account) and reworked some pending PRs (about i18n).
I also fixed a few small issues and helped a tiny bit with SOLR.

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

last week was an odd one for me – in a few ways. the weather during the day got warmer and that impacted my sleep so there was a day I was in full on zombie mode. not fun,
on the bright side, that finally convinced me to get a portable AC unit for my bedroom.
the rest of the week was spent on the usual sorts of non-sense like foundation admin, procuring new insurance and emails.
I reviewed a pile of PRs and mostly caught up on those as well.
the most troubling bit was that we received a complaint from Google that one of our mentors had helped an applicant with their application – unfairly.
I did some snooping around and with the help of a couple of people pretty quickly figured out that this person held a grudge and was making shit up.
none of our volunteers/staff did anything wrong and we’ve settled the issue with google.
still, it took far more of my week than I cared for.
and the redux: there is nothing for us to learn from this. some people are sore freaking losers.
given that, this is as far as I will disclose any details as to what happened.
onward, upward, but with gelato this time.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

I spent the last week finalizing my work on importing musicbrainz row IDs into LB. That is done now, involved a new release to LB.
This means that it should be easy for us to delete user accounts on LB if they delete their MB accounts.
I’m gonna soon try to port this over to other Brainzes.
Other than that, I spent the weekend setting up a Spotify account (via a tunnel) and then working extensively on the spotify listen importer that @alastairp was working on.
there were a few chinks that needed to be fixed.
Mostly done now, excited to deploy that to beta
Also, merged a few small PRs from @little_rsh, we’ve gotten back to schedule, I think. I’m hoping replication packets don’t take more than around a week and a day or two.

@kartikeyaSh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@kartikeyaSh

Last week I created PR for LB-373, LB-374, and BU-15. And started reading How docker works as I will need it for the 3rd part of project. That’s it.

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

Discussing and looking up some spam stuff with/for @yvanzo, and generally being around and about.

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

This week is was midsummer! Happy Samradh!
I did some “spring cleaning” and removed a lot of cruft and old tickets.
As expected, the previous week’s “membranophone” change caused havoc - trying to reply to and making sure everyone understands what is the options for change and such.
I’m not sold on the membranophone idea but it received no contests for the week the edit was open (I should have had someone vote no on purpose to keep it longer even further, but alas)
in other, more positive news, I finally got a NEW PHONE​:fireworks:
With this I maybe able to edit mb on-the-go, which will (hopefully) increase my productivity on really sunny days (typical that the weather has been bum since a week now :​​D)
of course this new phone has a /nano/sim so I will need to mess around getting a new sim
Still trying to concentrate on @chhavi‐feedback, it’s slowly getting there

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

I bought The Witcher 3, then I played The Witcher 3
I also posted a bit about the aforementioned drums issue
We might need to change the name, but we’ll see
I pestered bitmap to look at the genres PR again
And I opened Project Composer Diversity - MusicBrainz Wiki
Which for now needs an annoying thing with people pasting composer urls in the wiki, so I talked to @bitmap a bit about possible collaborative collections
If I get bored enough I might try to write that, but no promises

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

Well, my week was kind of a mess, spent way too much time travelling between the city I come from and the one I study in but at least I got to see a concert in the large hall of Elbphilharmonie - MusicBrainz
On the SpamBrainz side of things, I’ve gotten most of the API so far done but I’m struggling a bit with how to use Flask Blueprints (just takes a while to figure stuff out).
I also forgot to commit my WIP work so I couldn’t work on the train which had a lovely 50 minute delay at 1 in the night, yay!

@little_rsh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@little_rsh

Last week I completed the work of importing the MB metadata in AB database. Then worked on the script to update the musicbrainz schema by importing the new data corresponding to a recording whenever there is any new recording insertion in acousticbrainz db.
And read about replication packets and figured out a little on how would i write a script to apply the packets to keep the musicbrainz data in AB db updated with the actual MB database

@shivamt

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@shivamt

This week on mostly code refactoring and improving mapping.
I set up test environment, wrote some tests.
I am wrapping up last (as in previous, ed.) phase objectives.
Documentation and improvement of mapping of some dumps is on radar for this week.

DR: INST-24

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

please read the ticet and the comments
So as asked last week, I would like consensus about https://tickets.metabrainz.org/browse/INST-24
it seems to be an “art instalment thing” to me which could be served fine with Instrument credits (see my comments on the ticket)
However, I am not certain certain, so incase someone has any counteropinions, now is the time to speak up!
i fear is that it will basically become a dumping ground for any “guitar played some other way” credits
“altered guitar” i belive we eiher already have or there is a ticket for it

@Freso and @reosarevok both spoke in favour of simply using intrument credits for the time being. @ApeKattQuest_MonkeyPython noted that there had been no activity on the ticket since 2014, so if it “suddenly becomes popular” a new ticket can be made.