#metabrainz

there are some things about actual recommendation algorithms, but also some stuff that includes surveys / experiments with people, seeing what works from a presentation perspective

alastairp: yup. Having them at a single place will really help. Eagerly waiting for it.

yvanzo: if you have some time at some point to look at https://github.com/metabrainz/musicbrainz-serve... I'd appreciate it :) (it's fairly minor but I would like to have it merged by the time the alias form gets done)

alastairp: shall we do a bit of a check in or should we chat in detail when you come to the office?

ruaok: let me take a look at my notes

not as much last week as the week before, as I was off doing stuff for another project

I think we're doing OK with the small improvements in troi - tests, jenkins, logging, debugging, etc

yeah, now we need substance.

do you have any news on the year endpoint?

debugging as we speak.

I was going to take a look at integrating that into the similarity stuff, but held off because of your bug discovery

discoveries?

these are some of the most complex SQL queries I've ever written. but with any luck that endpoint will be live tomorrow and then soon thereafter a troi element.

I was wondering about evaluation/testing

assume that year support is coming mid-week or so.

especially because you asked in passing why I chose these 2 specific similarity metrics

oh good, now I have some capacity for that discussion.

the specific answer to that question was "because it was something to start with"

but it's clear that these metrics give widely different results

oh, interesting. I kept finding bugs before I was able to really look at the results.

hopefully that yak will be fully shaven soon.

mostly I mean because we have things like bpm, or mfcc (instrumentation), or high-level similarity (generally similar sounding stuff? maybe?)

we have the pending playlist hackday, and feedback being integrated into LB, but I'm not sure if we should be using that to solicit feedback for stuff at this level?

> but I'm not sure if we should be using that to solicit feedback for stuff at this level?

not sure I understand comment

mmm, maybe I'm getting ahead of myself though. Perhaps the focus should be on providing the patch, rather than providing a "perfect" acoustic similarity lookup

YES

that is the whole point of troi.

right, so just allow this patch to look up all similarities

slap something together that gives a valid, (if not good/perfect) example that uses our data.

then our tuning of a good similarity can be something on top of that

yes.

yeah, I'm still looking too far in the future to a fully working thing

I think this patch will be a good litmus test for troi -- once we have all the prereqs settled then we can actually collaborate on getting this to work better.

I am doing that for daily jams and if it werent for finding bugs, it would be good fun.

yep. in fact. after that discussion, I think it's actually ready then

let me rebase and add the other metrics in

perfect.

everything else that I want to add can be another layer on top

I like the debug logging now 👍 great to see the class where the message is coming from

I like it less because of the shit formatting

yeah, I guess that's something that needs to be improved

It’s International Monday to End Impunity for Crimes against Journalists!

I got one mailed in review, but they have since retracted that review, so…

People up for reviews tonight: bitmap, ruaok, zas, pristine___, Freso, reosarevok, Mr_Monkey, alastairp, yvanzo, shivam-kapila, jmp_music, CatQuest – anyone else who wish to give review, let me know ASAP. :)

ruaok: Go!

aight.

(Skipping bitmap to go first since I didn’t see them yet, in case he missed the meeting time change for him. :x)

last week was working on troi, PRs, some accounting trying to chase up some people who should pay us before the end of the year.

I am here :) thanks

I'm also working to get people to pay us electronically, since depositing actual checks keeps getting more expensive (and really, checks in 2020?)

Didn't even realize those still existed

then I discovered that my fix for fetching years from MB was seriously flawed and then went down the rabbit hole trying to fix the bug, only to find several other bugs/deficiencies.

I'm hoping to put out an improved Daily Hams (spellin is intentional) before the end of the week.

a really boringly normal week, really.

fin. alastairp!

hi, as I said just 20 minutes ago, I spent some time on troi - improving some code, reviewing patches, setting up jenkins

I also did some CB reviews, and started generating docs for BU with sphinx

yvanzo: next

hi!

Last week was quite similar to but shorter than the previous one…

Reviewing MBS PRs, updating URLs in MB DB, and debugging MB search.

That plus investigating MB WS 500s and SIR failures.

Fin, go bitmap!

hey

(People still up: zas, pristine___, Freso, reosarevok, Mr_Monkey, shivam-kapila, jmp_music, CatQuest – anyone else who wish to give review, let me know ASAP. :))

last week I worked more on MBS-11092, mostly moving csrf token handling to the Form layer since we reuse the login form on different endpoints, and making sure POST parameters are preserved in the form

MBS-11092: Some issue with userscripts/plugins and beta site https://tickets.metabrainz.org/browse/MBS-11092

should submit something after the meeting

opened a PR for MBS-1424 which adds a first-release-date "field" for recordings (read-only, calculated from release events)

MBS-1424: Add a 'First release date' field to recordings https://tickets.metabrainz.org/browse/MBS-1424

it's implemented in a backwards-compatible way that we can deploy before the next schema change

:)

also helped a lot with date period validation on https://github.com/metabrainz/musicbrainz-serve... which is good since it'll guide how we do validation on other edit forms

mostly just minor things otherwise, doing code review and looking at disk space issues on paco

fin! go Freso go

o/

^

a vegan is fine too

( ͡° ͜ʖ ͡°)

Not much out of the usual going on for me last week, so nothing much to say from my side.

fin.

zas: Go!

hey

I did usual maintenance tasks, supervision, upgrades, Picard PRs reviews. That's it. pristine___ ?

Hey

Thanks

Hi everyone

Last week I worked with Mr_Monkey on recommendation feedback. We mostly worked on the UI. Then I wrote a design doc to get feedback from the community. Also, I worked out a lil on refactoring recording recommendations code. 

Nothing much though.

Fin! CatQuest ?

I can go first, I'm sure they'll be back soon :)

Go go

I spent most of the week working on MBS-11168

MBS-11168: Convert alias edit form and edit pages to React https://tickets.metabrainz.org/browse/MBS-11168

With a *lot* of help from bitmap

This is our first big React form with a lot of JS validation and special cases and whatnot

So it's important to get it reasonably right so we don't need to rewrite it all later when we realize we did a dumb

I'm now reorganizing the whole thing and splitting it into as many smaller commits as I can, but it'll still be kinda big and clunky to review I suspect

But we'll see

Other than that I fixed a few ISE bugs caused by React caring about our old historic crappy data being broken where TT ignored it

And merged a bunch of stuff to release a beta - which I guess we'll release for real today

This week I'll be hopefully done with the whole alias form (one smaller form missing still)

And then can maybe try to find time to look into the IROM images or something else less

😎

formal

Fin, I think

CatQuest / KassOtsimine: you around now? :)

hit hu

If not, then maybe Mr_Monkey

Oh

hey

If yes, then you :D

Meow! `😺`

For this week I got nu'fink - Celebrated Halloween! :D

This week I'll be working on BookBrainz

Mr_Monkey I hope we can discuss some of the relationship questions put up on community in the oppcoming days <3

♎

fin, go Mr_Monkey !

Hi !

For the first half of last week my sister was visiting, but I reviewed PRs, kept an eye on the forums and helped a new BB contributor get set up.

(Only shivam-kapila and jmp_music__ left on my list. Last call for others who may want to give review!)

The second half, I reviewed PRs some more and helped pristine with recommendation feedback as she mentioned.

I also tracked and fixed some bugs and finished some open PRs for BrainzPlayer.

Finally, I updated some packages in BB following the new Node LTS version (CI tests were broken for the new version).

That's it for me !

shivam-kapila go!

Mr_Monkey: do you have a "newbie to BB" welcome package in the docs somewhere already?

Hi

If not, maybe you can use whatever you used in the forums :)

Thanks

hi!

+1 to that

My laptop is still yet tobe delivered

So no code

I participated in some PR reviews

And discussions

The week was quite equipped with wedding fun

With the tee surprise just in time

Thats

It

:crosses fingers for shivams laptop arriving soon:

jmp_music__: go

Hey everybody o/

CatQuest: haha. its been 15 days since 1st order :p