#metabrainz

/

      • yyoung[m]
        In GitHub you need permission to change the assignee, and it's inconvenient to link issues
      • alastairp
        agree with reosarevok, I've gone and implemented many good-beginner tickets because I realised that we really needed them
      • CatQuest
        it is more flexible. it's a Eissue manager" and github isn't that it's something else
      • alastairp
        but I didn't want to leave it any longer
      • lucifer
        alastairp: 👍
      • rdswift
        I love doing "Good Beginner" tickets. 😉
      • CatQuest
        this is one issue i have with bookbrainz tbh. monkey
      • yyoung[m]
        And you can log into Jira using musicbrainz and you need a GitHub account to open an issue
      • alastairp
        rdswift: if you're having a bad day and you want to bash out something to make it feel like you're useful for something
      • yyoung[m]
        s/and/but
      • lucifer
        on moving docs to rtd and pointing it from readme.
      • alastairp
        regarding HACKING.md, we have the devel doc page in rtd, we should do the same for LB. CB has some of this too
      • monkey
        Same for BB
      • CatQuest
        are we going to make a "documentation" epic /miniproject or what
      • for these tickets
      • a jira-howto
      • just1602 has left the channel
      • alastairp
        akshat: it's true that the link in LB's README file isn't very helpful with links to open tickets. we can add this
      • CatQuest
        if someoen already knows github but doesnt know jira
      • i agree
      • yvanzo
      • Freso
        alastairp: Probably the year before last? That was the last year of GCI, where I specifically poked people to tag/label tickets. :x
      • alastairp
        can someone help with adding bullet points about this discussion to the minutes
      • I'm falling behind
      • Mineo has quit
      • rdswift
        reosarevok: That is a very important aspect. I have run into that before when I have developed a solution based on a Jira request, only to have it denied because it wasn't what the team had in mind.
      • Freso
        reosarevok: I’m not fully sure what the current topic is 🙈
      • rdswift
        Maybe all new requests should be reviewed / approved by the team and then have some development specifications added before marking them as "Available to be assigned".
      • CatQuest
        Freso: me either :D
      • reosarevok
        The current topic is kinda-sorta still "Making contribution easier for new contributors" but it developed also on "How to make sure users don't assume all tickets are open for work"
      • CatQuest
        oh this.
      • reosarevok
        Although it seems we're mostly still on "Making contribution easier for new contributors"
      • Freso
        Okay. Using "Topic: Triaging tickets" for the stream for now.
      • CatQuest
        it was the last ticket i linked to you. something related to instrument images
      • can anyone who have oversikt over what the topics have been the last hours update the timetable on https://docs.google.com/spreadsheets/d/15GKraub...
      • alastairp
        CatQuest: theres an ordered list of topics in https://docs.google.com/document/d/1MdK9y1fSa5A...
      • CatQuest
        yes.
      • rdswift
        We need to find a way for team members to get more involved on requests earlier in the process to make sure that the specs are clear.
      • CatQuest
        what I wish someone would do is put those that are done in the rigt time bracket
      • Mineo joined the channel
      • alastairp
        rdswift: I tried to address that with comments at https://wiki.musicbrainz.org/Development/Summer...
      • rdswift
        Remember that new users don't have the same long-erm, big picture view of the projects.
      • alastairp
        other people on the internet have complained about the "pr method" of contributions for the same reasons, you don't get to know what people have been working on until they dump a huge change in a PR :)
      • rdswift
        s/new users/new contributors/
      • alastairp
        it turns out that this is a people problem
      • that is, we need to ask people to interact with us before they start coding, and we need to make sure that we interact with those people
      • rdswift
        alastairp: EXACTLY! Need to develop that into the process somehow.
      • ruaok
        guilty
      • alastairp
        we use jira as a task dump, not a project management software
      • and we work quite independently (that is to say, no "manager" making sure that people are working on what they say they're working on)
      • and we very often work on things that don't have tickets
      • CatQuest
        he tells me to create a ticket if i report a thing :D
      • outsidecontext
        rdswift: you can disable issues on GitHub and e.g. point people to Jira. For picard documentation that would make sense. Either we should have it as separate project on JIRA, or we just add a Documentation component to the existing Picard project, which also would be fine IMHO
      • alastairp
        our jira has a "sign in with github" button too
      • !m yvanzo
      • BrainzBot
        You're doing good work, yvanzo!
      • rdswift
        +1 Thanks outsidecontext
      • Freso
        BUT!
      • outsidecontext
        For plugins I want to note that the GitHub issues where intentionally setup separate and we had been pointing users actively there. But that doesn't really work and not really solve the issues we have with plugin maintenance, so recently I have stopped redirecting user there when they open plugin tickets in JIRA
      • alastairp
        does the pull request merge button on LB still squash commits?
      • lucifer
        need to check the default but i enabled other options some time ago.
      • Freso
        https://chris.beams.io/posts/git-commit/ is a great primer for good commit message writing :)
      • lucifer
        yes, the default is squash but we can change it if we want.
      • ruaok
        props for yvanzo to be just a floating head in the dark. good effect!
      • alastairp
        looks like default now appears to be merge, which I'm in favour of
      • Freso
        Works esp. well combined with https://www.freshconsulting.com/atomic-commits/ (which indiscriminate commit squashing is counter to) :)
      • lucifer
        it seems to be user specific? its squash for me
      • tests are another can of worms...
      • rdswift
        I find it harder to write tests than the actual code changes.
      • But the tests are very valuable during the development.
      • lucifer
        indeed +1
      • kepstin
        imo, twitter isn't a very good medium for that due to how ephemeral it is
      • rdswift
        And some of us "old farts" do do social media in general. 😉
      • *don't do*
      • peterhil has quit
      • Can you capture the brainzbot notices about merged PRs and the just delete the minor / non-newsworthy items?
      • Or capture the closed tickets?
      • CatQuest
        re this, i think doing zoom meetings for otherthings than just summits might be ok?
      • alastairp
        rdswift: github captures merged PRs for our releases: https://github.com/metabrainz/listenbrainz-serv...
      • and PRs that are merged before a releaes is made goes into a "draft" release
      • rdswift
        +1
      • alastairp
        so this is what we use to make our releases, and we make tweets and link to this page. I agree with reosarevok's comment about adding a "user-accessible summary", and this is a good place to use for monthly roundups
      • ruaok
        just one carn of worms more...
      • alastairp
        :(
      • CatQuest
      • or wait
      • ruaok
        I made freso host now. everything ok?
      • monkey
        Yes
      • CatQuest
        i'll need to make a room and stuff
      • lucifer
        !m team
      • BrainzBot
        You're doing good work, team!
      • CatQuest
        I'll paste the right one once i fix it
      • yvanzo
        ruaok: it's a good indicator that it's time to stop for today ;)
      • CatQuest
        suggestion for custom words?
      • heyy
      • BrainzGit
        [listenbrainz-server] 14MonkeyDo opened pull request #1661 (03master…monkey-catch-getUserListenCount-errors): Catch potential errors when calling getUserListenCount https://github.com/metabrainz/listenbrainz-serv...
      • monkey
        That's the issue you reported CatQuest ^
      • CatQuest
        monkey: wich one :D
      • oh oh that
      • cool
      • MrClon has quit
      • reosarevok
        Freso: think we're done if you want to close for the day, thanks! :)
      • CatQuest
        \o
      • MrClon joined the channel
      • tandy
        Freso: nice flag :)
      • shivam-kapila
        Oh are we playing scribble?
      • Freso
        tandy: Thanks ✊
      • reosarevok: Done. Thanks. :)
      • CatQuest
        shivam-kapila: oh we wher but we all left now. we cna do that tommorrow. I'll create a room and add some custom words as well (suggestinos welcome!)
      • shivam-kapila
        sure would like to join tomorrow
      • CatQuest
        cool!
      • humhumxx joined the channel
      • outsidecontext
        rdswift: we already have a documentation component on JIRA for Picard. As far as I'm concerned that would be a good place for issues with picard-docs
      • rdswift
        I agree. I'll note that on the repository README.
      • Lotheric has quit
      • Lotheric joined the channel
      • Pokey has quit
      • Pokey joined the channel
      • MrClon has quit
      • MrClon joined the channel
      • antlarr has quit
      • peterhil joined the channel
      • peterhil has quit