#metabrainz

/

      • reosarevok
        lucifer: last two already wrote to me :) Sure, I'll add the third too. List for today: mayhem, yvanzo, lucifer, akshaaatt, Pratha-Fish, riksucks, jasje, jivte, shivam_, vscode, pixelpenguin (other GSoC students, if you're here ping me and I'll add you too)
      • 2023-05-29 14935, 2023

      • reosarevok
        zas: back to you, sorry
      • 2023-05-29 14943, 2023

      • arsh
        Hi reosarevok: if you can please add me to the list as well.
      • 2023-05-29 14944, 2023

      • zas
        plus usual Picard PRs reviews, user support, supervision, grafana alerts/dashboards tuning
      • 2023-05-29 14904, 2023

      • zas
        fin. mayhem ?
      • 2023-05-29 14909, 2023

      • reosarevok
        List for today: yvanzo, lucifer, akshaaatt, Pratha-Fish, riksucks, jasje, jivte, shivam_, vscode, pixelpenguin, arsh
      • 2023-05-29 14911, 2023

      • mayhem
        hi!
      • 2023-05-29 14943, 2023

      • mayhem
        last week I worked with atj to book summit lodgings and we booked one place -- we'd been there before. the place with the terrrace overlooking the parc.
      • 2023-05-29 14957, 2023

      • mayhem
        friendly host, he recognizes me from the barrio, so that is good.
      • 2023-05-29 14959, 2023

      • zas
        (nice one!)
      • 2023-05-29 14914, 2023

      • mayhem
        I also worked on background stuff, trying to seal a couple of deals.
      • 2023-05-29 14934, 2023

      • mayhem
        related to that aerozol and I worked on the attribution guidelines for our commercial users.
      • 2023-05-29 14910, 2023

      • mayhem
        I worked with monkey and tag and release group tag radio and we moved the whole lot further along. I'm genuinely excited for this work!
      • 2023-05-29 14924, 2023

      • mayhem
        I also wrote article for the 3 part article series. that was kinda fun!
      • 2023-05-29 14934, 2023

      • mayhem
        fin.
      • 2023-05-29 14936, 2023

      • mayhem
        lucifer: go
      • 2023-05-29 14940, 2023

      • lucifer
        hi all!
      • 2023-05-29 14911, 2023

      • lucifer
        last week i worked on implementing the login system for MeB as a part of the Oauth stuff.
      • 2023-05-29 14938, 2023

      • lucifer
        i also worked on adding popularity datasets by processing MLHD+ data.
      • 2023-05-29 14943, 2023

      • lucifer
        that's it for me.
      • 2023-05-29 14945, 2023

      • lucifer
        yvanzo: next?
      • 2023-05-29 14951, 2023

      • yvanzo
        Hi!
      • 2023-05-29 14905, 2023

      • yvanzo
        Last week I helped zas with getting some servers ready to reboot.
      • 2023-05-29 14916, 2023

      • yvanzo
        Also did some other maintenance tasks for Jira and Solr.
      • 2023-05-29 14926, 2023

      • yvanzo
        Pushed and reviewed a few MBS pull requests too.
      • 2023-05-29 14939, 2023

      • yvanzo
        Mostly getting prepared for switching translations to Weblate otherwise.
      • 2023-05-29 14948, 2023

      • yvanzo
        (It includes wiki landing pages and forum category about internationalization.)
      • 2023-05-29 14955, 2023

      • yvanzo
        Plus usual tickets triage and support.
      • 2023-05-29 14901, 2023

      • yvanzo
        Fin, go akshaaatt!
      • 2023-05-29 14924, 2023

      • yvanzo
        Or riksucks?
      • 2023-05-29 14936, 2023

      • yvanzo
        Or arsh?
      • 2023-05-29 14943, 2023

      • arsh
        Hi everyone
      • 2023-05-29 14951, 2023

      • CatQuest
        yo
      • 2023-05-29 14957, 2023

      • rdswift
        yvanzo, please let me know if you need anything more from me on the Picard / Picard Docs landing page.
      • 2023-05-29 14922, 2023

      • arsh
        So last week I spent time brushing up on some react definitions and learning about d3js
      • 2023-05-29 14938, 2023

      • arsh
        getting everything ready to start my gsoc project
      • 2023-05-29 14911, 2023

      • arsh
        And some time looking around how things work
      • 2023-05-29 14939, 2023

      • arsh
        and excited to start with my project
      • 2023-05-29 14948, 2023

      • arsh
        Thats all from my side
      • 2023-05-29 14948, 2023

      • mayhem
        remember that you can ask questions here.
      • 2023-05-29 14901, 2023

      • monkey has experience with D3
      • 2023-05-29 14908, 2023

      • arsh
        ok sure
      • 2023-05-29 14917, 2023

      • arsh
        after the meeting maybe
      • 2023-05-29 14924, 2023

      • arsh
        or I can ask now
      • 2023-05-29 14929, 2023

      • monkey
        Later please :)
      • 2023-05-29 14932, 2023

      • arsh
        sure thanks
      • 2023-05-29 14958, 2023

      • arsh
        Someone can go next
      • 2023-05-29 14906, 2023

      • reosarevok
        Pick someone
      • 2023-05-29 14914, 2023

      • reosarevok
        List for today: akshaaatt, Pratha-Fish, riksucks, jasje, jivte, shivam_, vscode, pixelpenguin
      • 2023-05-29 14923, 2023

      • arsh
        jasje: go
      • 2023-05-29 14932, 2023

      • jasje
        Hi all
      • 2023-05-29 14907, 2023

      • jasje
        exams over and gsoc project is fully engaged
      • 2023-05-29 14944, 2023

      • jasje
        started with visiting back my proposal, made tickets section wise and have started Phase 1
      • 2023-05-29 14951, 2023

      • jasje
        Meep moop
      • 2023-05-29 14902, 2023

      • akshaaatt is back
      • 2023-05-29 14906, 2023

      • jasje
        went through tickets
      • 2023-05-29 14919, 2023

      • jasje
        more people are using the app now
      • 2023-05-29 14922, 2023

      • jasje
        weehee
      • 2023-05-29 14951, 2023

      • jasje
        took care of the tickets and replied to a query on MeB community as well
      • 2023-05-29 14955, 2023

      • jasje
        apart from that
      • 2023-05-29 14914, 2023

      • jasje
        did some work on Feed Listens endpoint
      • 2023-05-29 14918, 2023

      • jasje
        thats it for me
      • 2023-05-29 14923, 2023

      • jasje
        akshaaatt?
      • 2023-05-29 14928, 2023

      • akshaaatt
        Hi Everyone!
      • 2023-05-29 14948, 2023

      • akshaaatt
        I revamped the entire ui/ux for profile and listens submission. We also got rid of unnecessary screens and stuff and I’ve started to work on our explore screen.
      • 2023-05-29 14914, 2023

      • akshaaatt
        I just made a beta release today. We will focus a lot more on UX of the app from now on.
      • 2023-05-29 14936, 2023

      • akshaaatt
        That’s pretty much it for now. I’ve just been juggling with stuff lately
      • 2023-05-29 14946, 2023

      • akshaaatt
        Go Pratha-Fish !
      • 2023-05-29 14955, 2023

      • jasje 🫸🫷
      • 2023-05-29 14926, 2023

      • reosarevok
        shivam_: go for now? : )
      • 2023-05-29 14931, 2023

      • shivam_
        hi!
      • 2023-05-29 14938, 2023

      • shivam_
        Thanks for adding me to the weekly meetings roster.
      • 2023-05-29 14945, 2023

      • shivam_
        I've nothing worthwhile to report from last week. I was mostly afk, out with friends.
      • 2023-05-29 14954, 2023

      • shivam_
        This week I am finally going to start the work on my GSoC project. Really excited for that.
      • 2023-05-29 14915, 2023

      • shivam_
        Oh, and last week I also got to connect with ansh and we had a nice conversation. He'll also be mentoring me during the project.
      • 2023-05-29 14931, 2023

      • shivam_
        That's it for me!
      • 2023-05-29 14941, 2023

      • shivam_
        go jivte?
      • 2023-05-29 14957, 2023

      • jasje
        no jivte
      • 2023-05-29 14904, 2023

      • shivam_
        vscode then?
      • 2023-05-29 14916, 2023

      • vscode
        Hi All
      • 2023-05-29 14946, 2023

      • vscode
        I wore on another ticket last week to fix minor issue for Api error message
      • 2023-05-29 14953, 2023

      • vscode
        worked*
      • 2023-05-29 14905, 2023

      • vscode
        connected with my mentor
      • 2023-05-29 14943, 2023

      • vscode
        I am working with him to get me the developer key for apple that I will need for my GSoC project
      • 2023-05-29 14918, 2023

      • vscode
        Revisited my proposal and getting ready to start it.
      • 2023-05-29 14953, 2023

      • vscode
        that's it from me, and I think Pratha-Fish is the only one left
      • 2023-05-29 14957, 2023

      • reosarevok
        List for today: Pratha-Fish, riksucks, pixelpenguin
      • 2023-05-29 14902, 2023

      • reosarevok
        Not sure if any are around :)
      • 2023-05-29 14910, 2023

      • reosarevok
        If any of you is around, say so
      • 2023-05-29 14916, 2023

      • reosarevok
        If not, I'll move on in a min or so
      • 2023-05-29 14919, 2023

      • vscode
        pixelpenguin: if no one else?
      • 2023-05-29 14907, 2023

      • reosarevok
        Ok, seems none of the three are here today
      • 2023-05-29 14915, 2023

      • reosarevok
        Let's move on. That finishes the reviews, thanks!
      • 2023-05-29 14932, 2023

      • reosarevok
        Next is... some reosarevok person, with "Indicating blocked editors"
      • 2023-05-29 14935, 2023

      • reosarevok
        go reosarevok
      • 2023-05-29 14939, 2023

      • reosarevok
        Hi!
      • 2023-05-29 14941, 2023

      • CatQuest
        :D
      • 2023-05-29 14905, 2023

      • lucifer
        akshaaatt: do you want to add profile pictures to meeting agenda?
      • 2023-05-29 14916, 2023

      • reosarevok
        So right now, when we mark someone as a spammer in MB, that is visible for everyone (or well, they become non-visible for everyone :) )
      • 2023-05-29 14943, 2023

      • reosarevok
        But when we just block someone's editing or edit note privileges, we do *not* show that to users in any way
      • 2023-05-29 14955, 2023

      • CatQuest
        like a vandal fex?
      • 2023-05-29 14959, 2023

      • reosarevok
        Yeah
      • 2023-05-29 14911, 2023

      • reosarevok
        IIRC the argument for that was that we didn't want to shame-mark users who got banned
      • 2023-05-29 14927, 2023

      • reosarevok
        But a) most sites mark banned users clearly
      • 2023-05-29 14939, 2023

      • reosarevok
        b) we keep getting banned people re-reported because people cannot tell
      • 2023-05-29 14951, 2023

      • reosarevok
        Is there any reason you can see not to have a notice that a user is banned?
      • 2023-05-29 14901, 2023

      • reosarevok
        yvanzo, bitmap ^ your opinion especially welcome
      • 2023-05-29 14906, 2023

      • yvanzo
        Was blocking was supposed to be temporary?
      • 2023-05-29 14921, 2023

      • reosarevok
        Well, it *sometimes* is, if we can talk things through with them
      • 2023-05-29 14922, 2023

      • CatQuest
        I mean if they are banned for vandalism or being jerks or whatever..
      • 2023-05-29 14933, 2023

      • yvanzo
        Would it make sense to have another level such as 'banned'? Or just say after one month without progress, we just delete your account?
      • 2023-05-29 14950, 2023

      • reosarevok
        For example, some times we ban people temporarily because they're not responsive to notes
      • 2023-05-29 14958, 2023

      • rdswift
        Perhaps display them as "under review" or "Under investigation"?
      • 2023-05-29 14916, 2023

      • yvanzo
        (one month or maybe more time)
      • 2023-05-29 14925, 2023

      • CatQuest
        perhaps just italicising and greying out names wouth saying "BANNED" or something
      • 2023-05-29 14925, 2023

      • reosarevok
        That said, I think it's a bit unfair for people to not know if someone has been (even if temporarily) blocked
      • 2023-05-29 14925, 2023

      • rdswift
        Might help prevent the repeated reporting.
      • 2023-05-29 14931, 2023

      • monkey
        If the user managed to get blocked, there were practical reasons. Nothing wrong with a bit of justified public shaming in that case IMO, especially if it's reversible.
      • 2023-05-29 14940, 2023

      • bitmap
        I think we should display something so people don't waste time reporting them again, whether that's under review or otherwise
      • 2023-05-29 14954, 2023

      • reosarevok
        Also for the user in question, because if people ask questions from them and they're blocked, they can't answer :)
      • 2023-05-29 14904, 2023

      • CatQuest
        yea!
      • 2023-05-29 14909, 2023

      • yvanzo
        We're not supposed to keep blocked accounts for too long either.
      • 2023-05-29 14912, 2023

      • CatQuest
        hmm
      • 2023-05-29 14920, 2023

      • reosarevok
        Well, we don't usually delete those accounts right now
      • 2023-05-29 14920, 2023

      • CatQuest
        yea i was wondering about that actually
      • 2023-05-29 14937, 2023

      • reosarevok
        Mostly because it's easier to keep track of new ban-evading and whatnot if we don't delete them, tbh :)
      • 2023-05-29 14950, 2023

      • yvanzo
        Maybe one year can be a hard limit.
      • 2023-05-29 14956, 2023

      • CatQuest
        that is true. it was a few new ones was foudn becasue i asked reo about some other ones
      • 2023-05-29 14916, 2023

      • reosarevok
        Ok, we can have a talk about this a bit later with the team
      • 2023-05-29 14926, 2023

      • yvanzo
        Thanks for raising this up anyway.
      • 2023-05-29 14928, 2023

      • reosarevok
        Nobody seems to disagree with marking them in *some* way at least to discourage further reporting
      • 2023-05-29 14941, 2023

      • reosarevok
        So there's that, we can discuss impl details in a smaller setting
      • 2023-05-29 14943, 2023

      • reosarevok
        Next is...
      • 2023-05-29 14947, 2023

      • CatQuest
        i also agree with the so people cna know they won't respond too
      • 2023-05-29 14949, 2023

      • reosarevok
        oh, it's that annoying reosarevok again
      • 2023-05-29 14959, 2023

      • mayhem
        i didn't say it
      • 2023-05-29 14959, 2023

      • reosarevok
        Blocking beginner voting again (MBS-13100)
      • 2023-05-29 14900, 2023

      • BrainzBot
        MBS-13100: Re-add some sort of vote restriction for new editors https://tickets.metabrainz.org/browse/MBS-13100
      • 2023-05-29 14914, 2023

      • CatQuest
        oh no. :(
      • 2023-05-29 14916, 2023

      • CatQuest
        already
      • 2023-05-29 14918, 2023

      • reosarevok
        So, turns out if you let new accounts vote, people start sockpuppeting, because people suck
      • 2023-05-29 14924, 2023

      • CatQuest
        :((
      • 2023-05-29 14927, 2023

      • reosarevok
        (well, some people)
      • 2023-05-29 14927, 2023

      • akshaaatt
        Yes lucifer
      • 2023-05-29 14900, 2023

      • CatQuest
        sux
      • 2023-05-29 14900, 2023

      • reosarevok
        akshaaatt: "Yes lucifer, burn them all in hell" *is* what I say when I see the sockpuppeting indeed
      • 2023-05-29 14906, 2023

      • CatQuest
        lmao
      • 2023-05-29 14915, 2023

      • CatQuest
        well i say maybe a week
      • 2023-05-29 14921, 2023

      • 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, Indicating blocked editors (reo), Blocking beginner voting again (MBS-13100) (reo), profile pics (akshaaatt)
      • 2023-05-29 14921, 2023

      • CatQuest
        it's hard ot get 10votes voted on