#metabrainz

/

      • monkey
        Good question. I believe the plan was to re-run the YIM stats tomorrow, so it's probably still good to keep it there
      • akshaaatt
        lucifer it is also present in the explore section rn
      • Right monkey
      • lucifer
        ah! i didn't know about that. sounds good.
      • i wonder if a tab could be added to user homepage as well.
      • akshaaatt
        We're working on that lucifer
      • lucifer
        👍
      • akshaaatt
        We had even decided for an actual profile page on LB
      • reosarevok
        bitmap: wait, it actually managed to return all million + editors in a single page?
      • Without timing out? :D
      • bitmap
        it started to, I hit the stop button before my computer crashed :P
      • (was using the sample DB so it only returned about 16k)
      • texke joined the channel
      • oh selenium tests are failing for PRs based on master 'cause it's missing https://github.com/metabrainz/musicbrainz-serve...
      • i merged beta into master just now
      • reosarevok
        Ok :)
      • bitmap: would you suggest to just do load_paged there or?
      • bitmap
        yeah. we should require selecting at least one option I guess, but load_paged could be useful for e.g. the spammer flag or other common ones
      • yvanzo
        reosarevok: The placeholder icon for editor looks good, feel free to merge it, thanks!
      • BrainzGit
        [musicbrainz-server] 14reosarevok merged pull request #2398 (03beta…readd-default-avatars): Add a default editor avatar for display https://github.com/metabrainz/musicbrainz-serve...
      • [musicbrainz-server] 14reosarevok merged pull request #2293 (03master…MBS-11986): MBS-11986 / MBS-12128: New account flag: Spammer https://github.com/metabrainz/musicbrainz-serve...
      • reosarevok
        Thanks for the reviews!
      • I'll release as soon as I fix the bug I'm fighting
      • yvanzo
        Great, it can be tomorrow if needed.
      • Freso
        <BANG>
      • It’s Street Children’s Monday!
      • I haven’t received any mailed in reviews. Which means the usual suspects are up: lucifer, mayhem, reosarevok, bitmap, alastairp, yvanzo, akshaaatt, monkey, zas, CatQuest, Freso – anyone else who want to give review, let me know ASAP!
      • lucifer: Go!
      • lucifer
        hi all!
      • i mostly worked on migrating various parts of LB to use user ids instead of user names. we'll hopefully deploy it all this week.
      • also discussed some stuff about listen counts and timestamps with mayhem and worked on that.
      • other than that follow up on existing PRs. that's it for me.
      • alastairp: next?
      • alastairp
        hello there
      • lucifer
        CatQuest: BB is in node.js, LB in python so no code reuse possible there
      • CatQuest
        aw
      • alastairp
        last week I reviewed some things for lucifer - documentation stuff from the previous week + the user id stuff, and a bit of the timestamps things too
      • I did some further digging into automatic computation of the "mood" of audio recordings
      • although this turned into a few different discussions with mayhem and others about how we can use our commumity to help us get better annotations for content in MB without resorting to automatic classifiers
      • I also spent some time preparing classes and teaching them at the uni, so was away for a bit in the middle of the week for that
      • that's it for me, yvanzo next?
      • yvanzo
        Thanks, hi all!
      • I mostly finalized scripts to repair indexing MB in Solr when broken.
      • Resent 880K search index requests to the indexer, most from previous failures in 2021.
      • Also reviewed a coupe of MBS PRs, including the spammer flag’s PR.
      • Fin. Go reosarevok?
      • Freso
        🙌
      • reosarevok
        Hi!
      • Freso
        (Still up: mayhem, bitmap, akshaaatt, monkey, zas, CatQuest, Freso – anyone else who want to give review, let me know ASAP!)
      • reosarevok
        I mostly reviewed our Perl tests
      • And wrote docs for them
      • As in, added descriptions of what they actually do
      • Other than that, some code review and some finally fixing some small bugs that I hadn't found time to look into before the holidays
      • CatQuest: you?
      • CatQuest
        meow!
      • I've been working
      • this week I'll be working more!
      • today is both clothmass and chinese new years! 🎊
      • I'm also going to work on instrument documentation (with reosarevok)
      • finally I hope to add some more instruments
      • fin! next can be: monkey! 🐒
      • monkey
        Hi everyone !
      • Last week I spent most of my time reviewing and merging PRs for BookBrainz and ListenBrainz.
      • There was (and still is!) a big backlog of PRs from the holidays that I hadn't got to yet, and a lot of general repo upkeep tasks.
      • Including fixing the automated linting setup for the github repo
      • I helped BenOckmore roll out an update from Boostrap version 3 to v4, now deployed on beta.bookbrainz.org
      • And as a follow-up, I'm currently reading v4 to v5 migration guides. I think we'll soon want to use the design-system package that akshaat is working on which uses Bootstrap v5.
      • I also helped Shubh with a couple of big impact projects for BookBrainz: notifications and import userscripts.
The latter requires creating POST endpoints to pre-fill entities, as those don't exist in BB yet.
      • And that's most of it ! bitmap go !
      • bitmap
        hey
      • CatQuest
        :O
      • bitmap
        last week I mostly worked on code review, plus fixing test failures and merge conflicts in open PRs
      • was trying to fix more test flakiness since circleci often fails for no reason, so pushed a couple changes for that that seem to help
      • other than that I was working on finishing some pgtap tests for the area_containment schema change I mentioned a couple weeks ago (that would improve perf of the area-related pages)
      • fin. mayhem go!
      • mayhem
        hey!
      • last week was finishing off more documentation and emails and some more peer learning network calls.
      • but then thursday evening inspiration struck and I realized we can use listens to calculate something akin to recording similarity. this factors into alastairp's update about using LB to generate some of the data we were hoping to product from AB.
      • and this realization, after doing about 5 hours of work and getting promising results, changes many things about how we should be moving forward with AB.
      • Freso
        (Sorry, Ffx crashed. On mobile while I reboot.)
      • mayhem
        I hope that alastairp and I can chat about it more and that I can finish the proof of concept and tune the results a bit.
      • fin. zas?
      • monkey
        There's already a patch for that and deployed on beta now CatQuest :)
      • alastairp
        mayhem: let's do that chat tomorrow!
      • zas
        Hey
      • last week I worked on Picard patches & reviews, many good and big patches from phw (like support for long due eac logs)
      • mayhem
        great!
      • zas
        I also upgraded discourse in multiple steps (I started on friday, but I delayed to today the rest, and I did well, it failed)
      • so we are now running discourse 2.8
      • Freso
        🙌
      • CatQuest
        monkey: whooo
      • zas
        plus usual tasks, edits, etc.. fin. akshaaatt ?
      • akshaaatt
        Hi everyone!
      • I enjoyed working last week since I got the design system up and sailing!
      • I think we have some discussions and work incoming for the design system.
      • I fixed open PRs in MB and LB, and removed the boilerplate code that my past self had added.
      • Some Android app work is always happening in the background as well.
      • I'm happy with the way February is looking!
      • That's it for me. fin!
      • Go Fresh!
      • Freso
        👋
      • akshaaatt
        Freso*
      • alastairp
        fresh-o
      • Freso
        Last week I started working on some community management docs, still a way to go on that.
      • There were a couple of other things too, but I can't access my time tracker rn. :/
      • I'll be getting my booster shot tomorrow (finally), so I'll take most of tomorrow and Wednesday off.
      • I haven't reacted too poorly to prior vaccines (covid or otherwise), so I don't expect to be out for long... But we'll see how I feel Wed/Thu/Fri.
      • CatQuest: yes.
      • CatQuest
        aahh. highfive
      • Freso
        Fin.
      • I think that's all for reviews, right?
      • yvanzo
        Yes
      • Freso
        Thank you :)
      • CatQuest
        yes
      • Freso
        And thank you all for your reviews!
      • akshaaatt
        Thank you!
      • CatQuest
        nothing more for today, i think
      • Freso
        No more items on tonight's agenda, so this also concluded tonight's meeting.
      • Thank you all for your time! Stay safe out there! 🙏
      • </BANG>
      • BrainzGit
        [listenbrainz-server] 14amCap1712 opened pull request #1836 (03master…amCap1712-patch-2): cron: fix feedback dump command https://github.com/metabrainz/listenbrainz-serv...
      • Freso goes to try and fix his desktop now 😅
      • alastairp
        mayhem: after your work last week I've also been mulling over a bunch of things, especially around content-based computation vs user data-based and when each of them is useful
      • mayhem
        have you found useful cases for the content based approach is the not BPM?
      • alastairp
        and I was reading a bit about differences between "recommendation" vs "playlisting" (Ben F and Paul L did a well-known tutorial about this >10 years ago now - https://www.slideshare.net/BenFields/finding-a-...), I'm interested to see how this fits in with some of your ideas
      • I had a really quick look through some papers and other documents
      • one of the biggest drivers for content-based computation is "what do we do about the long tail?"
      • so, stuff that doesn't have a lot of people listening to it (because it's not popular, or because it was released yesterday)
      • mayhem
        ok, I can see that. deffno not low hanging fruit though
      • alastairp
        so a lot of the work on "content-based recommendation" was trying to take user-based data, which was known to be pretty good, and see if they could get similar results using only the audio content compared to the user-centric methods
      • which I think ties into a lot of this discussion about what we're collecting the data for, and what we want to do with it
      • I think it's correct to say that if we have a lot of user interaction data, for popular tracks, then that's definitely the way to go
      • mayhem
        agreed, that has become more than evident now.
      • reosarevok
        I'd really like to be recommended less popular stuff too though :)
      • alastairp
        and if we want to try and work out how to do recommendation in the long tail then we have to look at a combination of things (there's been a lot of work in this area for years, since Oscar Celma's PhD), but I'm not sure what the current state of the art on that is
      • reosarevok
        (eventually)
      • mayhem
        I think this popular vs long tail distinction is a good one for us to keep in mind.
      • alastairp
      • that's a pretty good overview in only 130 slides, for the most part you can skip the mathy slides
      • reosarevok: there's a bit of stuff in there about methods to get recommendations for less popular stuff if you don't have play data
      • which doesn't go all the way to automatically extracted features
      • mayhem adds both of those to his reading list
      • which we might have a lot of low hanging fruit on (relationships in MB, wikipedia, reviews, etc)
      • mayhem: https://link.springer.com/book/10.1007/978-3-66... appears to be Peter Knees' book on this - I suspect's mostly covering research he's done over the last 5-10 years (same person who did that tutorial)
      • mayhem
        I'm going to start thinking about how OSS methods could help in address the long tail issues.
      • alastairp
        the univeristy doesn't have it, but I made an inter-library loan
      • mayhem
        oh cool.
      • alastairp
      • anyway, see you in the office tomororw