Also worked with akshaaatt on the Listenbrainz redesign, making some headway on a mockup
I reviewed some PRs and cleaned up old tickets
And that's that! lucifer go !
lucifer
hi all!
ruaok
soulcoughing. <3
Freso
(Only alastairp, yvanzo, and akshat left on my list – last call for anyone else who want to give review :))
lucifer
i did some debugging around failing dumps and missing imports in spark. also, worked on various LB year in music stuff - user's most prominent color, new releases of top 50 artist. other than that some misc discussions and follow ups on existing PRs. that's it for me.
alastairp: next?
alastairp
hi
last week I attended the ismir conference online, and saw some interesting projects using MB and AB data
I also saw a few interesting things that we could use in LB for recommendations, I shared some things in chat throughout the week
I reviewed a huge number of LB prs, !m lucifer for continuing to work on those
I did some work on dumping timescale tables as a part of the full dump
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Agenda: Reviews, Follow up on Summit Notes -> Tickets
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Agenda: Reviews, Follow up on Summit Notes -> Tickets
monkey
Thanks Freso! Saddened to see the personal attacks against you out there
yvanzo
Thanks!
monkey
ruaok: Mayhaps?
ruaok
I'd love for you to give it a try...
CatQuest
do you need technical knowhow to write those tickets?
if not, i cna work on it
monkey
If we improve resolution of cover art (with an LB endpoint we can query), it might be less of an issue, and missing data would more clearly stand out
CatQuest: Help appreciated :) I'm guessing probably not for the most part, and you can always tag people to look at and add more details to the tickets
Or ignore the ones you're not sure about
ruaok
monkey: looks good to me. I'd love to see something like that.
monkey
Maybe a sort of "add me to MusicBrainz" thumbnail ?
monky zas/ othes. got a question on the dummit notes
reosarevok
Is the dummit notes the version of the summit notes with very simple English?
ruaok
ruaok: alternating fornights, I think.
fortnights, even.
more seriously, that I was I am working on. to have the mapping redo unmatched items and then I need to rerun the bono data. I'll do that before we push the reports final data.
[bookbrainz-site] 14dependabot[bot] opened pull request #716 (03master…dependabot/npm_and_yarn/webpack-5.64.1): chore(deps-dev): bump webpack from 5.12.3 to 5.64.1 https://github.com/bookbrainz/bookbrainz-site/p...
[bookbrainz-site] 14dependabot[bot] closed pull request #713 (03master…dependabot/npm_and_yarn/webpack-5.61.0): chore(deps-dev): bump webpack from 5.12.3 to 5.61.0 https://github.com/bookbrainz/bookbrainz-site/p...
alastairp
thanks reosarevok and bitmap for humouring me and my MB review :)
reosarevok
I mean, it includes good points, so :)
Feel free to do more of those :D
alastairp
ah - is that the trick? make good points and people listen to you? :)
lucifer
ruaok: alastairp: which schema should year_in_music table go into?
alastairp
stats, no?
lucifer
some things are stats but not all.
ruaok
stats seems fine to me
lucifer
ok, i don't have a better suggestion anyways. going with stats.
spark side looks ready, once the data is in db. i'll start the api endpoint work.
ruaok
how will you add more stats to this table?
add more columns?
lucifer
yes
ruaok
seems a bit cumbersome.
lucifer
as more stuff becomes ready, add more update scripts to add more columns.
oh
ruaok
needing a schema change for each feature added to the year end report
lucifer
yeah right. i think its the most flexible currently though.
ruaok
I think a single JSONB column could be sufficient. we just add more top level keys. and we'll need to provide a method to add more keys to the json blob though.
a single JSONB column is more flexible, but has less structure. and I think it would not be acceptable in most cases, but this is not data we intend to query, except all at once. so I thin its permissable here.
lucifer
yeah that's possible
we had something like that in old stats format. i'll modify this on those lines then.