#metabrainz

LB-598

LB-598: Add "Export user's loved/hated recordings" feature https://tickets.metabrainz.org/browse/LB-598

ok.

so, if we're on the same page. shivam-kapila will focus on finishing up getting the listen card merged.

then finish up feedback and delete listens.

then work on the huge number of tickets i always have on my backlog ;)

where is the cutline with the huge number of tickets?

yeah. let's do that right now too.

[musicbrainz-server] yvanzo merged pull request #1634 (master…search-plugins_obsolete-handlearguments): Update search plugin settings https://github.com/metabrainz/musicbrainz-serve...

let's estimate that the delete and feedback things get done by next monday.

when is the deadline? 27th?

24-31

24th

For mentors to evaluate 1-7

coding is done on the 24th.

ruaok: thank you but I don't have access to it :)

yvanzo: that can be fixed.

there is also one on paco, yvanzo

but that is effectively a production DB, so careful.

logged in

shivam-kapila, iliekcomputers: I know that this point is moot now that we have cancelled the redesign, but I just wanted to say that I wont be able to work on the Listening Activity card on listens page anytime soon.

but this is for test :/

actually I want to test if the current PR doesn't break replication

ishaanshah: yep, that's reasonable. but it does teach you something about volunteering about stuff too eagerly ;)

yvanzo: yeah, bono or a vm for that. lets chat in a bit.

ok, thanks

I agreed to do it last month because I did not have college, but my work time has severely reduced rn and I need to focus on getting at least sitewide top artists out before gsoc ends

ok, so effectively we have 3 weeks then.

right.

umm, 2 weeks?

wait let's get in sync first.

heh.

coding officially ends 24th

then there's a week for students to essentially "clean up" and fill their evaluations

then there's a week for mentors to fill final evaluations

man, this whole covid thing has made me forget how to use calendars, lol.

ok, 2 weeks then.

yep.

what if we do this: 1 week to finish delete/feedback.

then on the first day after you task shivam-kapila with a task and a deadline of 24, max 48 hours.

yeah. most of these tasks are in that ballpark.

i think that sounds reasonable.

and if shivam-kapila keeps on the ball and keeps submitting work until the 30th, he gets a pass.

but if he starts slacking off again, fail.

shivam-kapila: what do you think?

1 question? I need to do all the above mentioned tickets?

no.

you need to do what iliekcomputers puts in front of you.

Okay

he gives you a ticket and deadline. and if he things you're doing a good enough job, you pass.

we'll get to some of those next week, i don't think all of them will get done.

this isn't really how I (or anyone here tbh) likes to work, but desperate times, desperate measures.

indeed.

Thats necessary for what I did

cool.

iliekcomputers: can we plan the next week tickets on friday/ saturday so I have an idea about them beforehand

shivam-kapila: so first order of business would be to get the listens card on the listens page and get that released.

let's first focus on the deletion etc.

but yeah, we can do that.

For deletion 3 dot dropdown having that list option. Sounds good?

yeah.

Ok

cool.

i don't have anything else for this topic.

happy to close it unless anyone has anything to say?

close it!

cool cool cool

ishaanshah: hey :D

heyo

sorry, maybe i should have just postponed our meeting instead of asking you to join

i figured you might have some ideas / opinions as well. but no worries.

how goes it?

Going well

Completed the API endpoint doay

today

yay!

exciting!

I figure tests will take the whole day tomorrow 😞

mhmm, sounds reasonable. np.

Then I will start with the frontend

do you think we can finish the entire graph off next planning session?

not tomorrow, next Tuesday

or would it take more time?

I think we should be able to

entire graph meaning artists only

yeah.

or release and recording too?

nah, that would be too much

artists only we should be able to

if both bump and stream dont work

We have a component to show them as bar anyways

yeah!

cool, that's awesome. i think we'll take on the incremental dumps task first after this.

yeah makes sense

adding release and recording support should be easy

the release graph and recording seem like a stretch goal at this point, i'm not massively concerned.

I will also need to write a work product right

we should focus on finishing up this graph and the incremental dumps.

oh yeah.

generally we do a blog post on blog.metabrainz.org

the deadline for that is 31s AAug

31st August

hmm. ok. add a ticket for it, and we can see if we need to start on that this week.

So I will start working on it a bit everyday, I am not very good at writing blogs so progress will be a bit slow for that

sure, np.

general advice: get a first draft out for review as early as possible

yep, I will try to get the first draft by this Sunday

nice. sounds good.

thanks for being on top of that.

i don't really have anything else.

anything blocking you? any concerns?

No, nothing else

I will get the PR ready for review tomorrow

cool. no rush.

have a nice evening!

you too!

shivam-kapila: let's try to get #1037 and #1038 merged quickly, ok?

the listen card one, we can start showing the cards on the current listen page.

Okay

But that will have a hollow in fewdback controls

Shall I span the div with track details for entire width

i don't think it really matters, given that you're gonna work on feedback this week.

Okay okay

whatever looks better to you works

Will just hide the buttons

sounds good.

feedback will really help in improving recs. Eager to see it work :)

Will work on tests tomorrow. Rest is almost done

never done until merged and released ;)

Right

Since you are around 1 more thing

The get- feedback api works for searching via a user/rec_msid

Shall we modify it to search for multiple rec_msid so that we search for all 25 recs on a page in one call

yeah, i think that makes sense.

the listens page is slow enough as is

It’s Black Cat Appreciation Monday!

I’ve received one mailed-in review, so Mr_Monkey, go:

Mr_Monkey says…

"""

:O

Hi everyone !

Last week I finished the React side of this PR for ListenBrainz: https://github.com/metabrainz/listenbrainz-serv...

I had more fruitful discussions about how the BookBrainz schema should evolve and what elements are currently missing, and ways to deal with certain complex cases of entries.

I also looked a bit at what’s needed to import the Bookogs database, both on schema and technical sides.

I continued to review prabal’s GSoC project, I feel the testing is a lot more robust now and things and the last few missing features are being implemented. I’m excited ! :)