#metabrainz

ok, let me re-read it one more time and make edits.

Cool

ok, I think that text is good enough for now. can you please update your PR with that text?

Hmm. Also, we will have to post to the community first to include that link in the PR.

yeah, a bit catch-22.

but right before merging the PR we should put a placeholder post, get the URL and then do there release and add the text after the release.

why not just put the text on the site?

does it need to be a community post?

the site doesn't have a way to comment/discuss....

hmm.

true

I am prompted to have something like a release notification modal

for nex ttime

ah ok. i see we're linking to a community post for comments

and more verbiage.

pristine___: are you releasing with feedback controls

No.

pristine___: in the doc we say that we process the data each week. are we actually doing that now?

That's the plan. We will have to write a cron job for that

It should be updates weekly, at least

Updated*

k.

the text in the doc suggests that we are in fact already doing that.

is the "last updated" timestamp shown in the tab with the recommended tracks?

No.

Can you please add that? people will want to know that.

I was thinking to first write the cron job,

And then release the PR to sync it.

> Can you please add that? people will want to know that.

Okay

> adds "will soon" to the doc

I am not really sure adding this.

About*

why not? this whole post is about managing expectations and we need to state things clearly and correctly.

stuff like that has a bad habit of staying in 2 years after it's been done and dusted :)

I'm open for suggestings on how to do it better.

I mean shouldn't we first write the cron job

For weekly updates

And then release this thing

what pristine___ says makes sense to me

I am really comfortable with the idea of saying we will do it weekly soonish

Not*

ok, then we'll delay the release of this until we have them generating on a weekly basis.

the cron job is easy. the fallout from the cron job may not be.

what's blocking the generation weekly, pristine___ ?

it may just tie up the spark cluster for a day or two, for each run.

Nothing. I just didn't write the cron job. I will do it.

how does that play with the stats jobs?

they'll be in the queue

but they'll be blocked until after recommendations are done.

Right. That's why I said about releasing the recent prs. We will get to know the total time in generating recs

Then we can sync recs and stas accordingly

i think we should just add them in, we've done them a few times already, seemed safe enough, but also add a ticket about making request consumer support timeouts somehow.

so then doing a release is actually more important than reviewing this doc?

iliekcomputers: I still want to knon the approx time before final release of showing recs on site

> so then doing a release is actually more important than reviewing this doc?

iliekcomputers: what are the steps to release then? merge PRs, build & push with today's tag, then restart running services?

1. Release the merged PRs

2. Write the cron job

3 Publish the community post

4 release the PR to show recs on site

Is what I think should be done.

merge PRs to master, deploy beta to check that things look sane, merge master to production, build and push images, restart running services

ok, which PRs need merging?

they are merged already.

would get this one in too, while you're at it

[listenbrainz-server] mayhem merged pull request #1059 (master…dont-send-last-week-listens-in-rec): Recommended recordings should not include recordings the user listened to recently. https://github.com/metabrainz/listenbrainz-serv...

also, don't need to restart all services, just related ones. i'd do web and spark-reader, not cron because that is running a data dump right now.

:+1

the commands

its gonna take some time before I get there, pristine___

just for reference. cool

ruaok: GSoC evals sent. I’m very proud of _lucifer and SomalRudra and the work they’ve done 🥳👏🏻

_lucifer: ^

SomalRudra: ^

The MB Android app has been totally reworked and now looks great! 📱🎨

I would have to agree on both counts!

!m SomalRudra & _lucifer

You're doing good work, SomalRudra & _lucifer!

I find that the search results still could use some love. are those on the radar for the app?

iliekcomputers: I see that you have assigned *write cron job for recs* to yourself.

iliekcomputers: pristine___ : Beta updated. help sanity check, please.

pristine___: i'm the default assignee :)

ruaok: it loads, so lgtm :)

lolol

ok, I think it looks fine.

ruaok: yes, still some work has to be done. 😊 But the app now has a strong foundation for new features and mantainability.

iliekcomputers: `git checkout production && git merge master && <handle issues> && git push origin production` ?

yep

gr0uch0mars: thank you for your mentorship -- it looks so much more professional now!

handle issues should be a noop

no-op*

confirmed.

pushed

🎉

ruaok: thanks for trusting me. I wish I could have done more! 😊

:)

iliekcomputers: v-2020-09-01.0 tagged and pushed

as for updating the tag for nodes/lemmy do you just push commit the new tag to master directly?

yeah, that's what i've been doing

https://github.com/metabrainz/docker-server-con... ?

lgtm

iliekcomputers: oh! I thought you are on it so I didn't pick it up.

there were some local changes on the docker-server-configs repo for lemmy. should start start_listenbrainz_cron be v-2020-07-26.1 or v-2020-08-28.0? (I'm not going to restart it, I just want the file to be correct)

iliekcomputers: ^

the latest one, 28.0

one docker layer is always suuuuuper slow to push. gonna take another 20 minutes. anyone else get that?

ruaok: BTDT

ruaok: 20 min is a lot

i just push from lemmy and it's always fast

this is not my connection, but a docker server issue, I think.

must be their shiny new TCP-over-carrier-pigeon implementation

i started on a first version of the planning doc here: https://www.dropbox.com/scl/fi/niem4dby5hz7ar9z...

_lucifer: ishaanshah: shivam-kapila: ideas on what you wanna work on would be appreciated ^

ruaok: pristine___ ^

iliekcomputers: Post design stuff I want to jump into recs

wow, paper is annoying.

8 thing to click away just to type some nonsense.

Project bookbrainz-site build #3403: passed in 4 min 48 sec: https://travis-ci.org/bookbrainz/bookbrainz-sit...

can't believe stats is finished, 3 years after my gsoc project lol

had to become a mentor to finish it off

heh

what was the user-user feature called again? user neighborhood?

I was calling it neighbours

do we want percentage or something like snapchat

haven't fleshed it out yet.

right now i'm trying to zoom out and think of stuff that we could build

ah ohkj

then i'll try to list them in order of impact

then take the highest impact thing and flesh it out

ah ohk

I thought it was released

I just updated to 2020-08-24 and now when I run replication it's complaining about noit being able to find JSON.pm

LB release complete.

iliekcomputers: will you do the release announcement later with your nifty tool?

sure

err, that may have sounded wrong....

ruaok: given that i'll have time to write code now that gsoc's over, do you want to chat about priorities soon? i'd like to take one big piece of work and focus on that for a while.

lots of options

can do tomorrow...