#metabrainz

In GitHub you need permission to change the assignee, and it's inconvenient to link issues

agree with reosarevok, I've gone and implemented many good-beginner tickets because I realised that we really needed them

it is more flexible. it's a Eissue manager" and github isn't that it's something else

but I didn't want to leave it any longer

alastairp: 👍

I love doing "Good Beginner" tickets. 😉

this is one issue i have with bookbrainz tbh. monkey

And you can log into Jira using musicbrainz and you need a GitHub account to open an issue

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

s/and/but

on moving docs to rtd and pointing it from readme.

regarding HACKING.md, we have the devel doc page in rtd, we should do the same for LB. CB has some of this too

Same for BB

are we going to make a "documentation" epic /miniproject or what

for these tickets

a jira-howto

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

if someoen already knows github but doesnt know jira

i agree

akshat: There is this for now: https://github.com/metabrainz/.github/blob/mast...

alastairp: Probably the year before last? That was the last year of GCI, where I specifically poked people to tag/label tickets. :x

can someone help with adding bullet points about this discussion to the minutes

I'm falling behind

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.

reosarevok: I’m not fully sure what the current topic is 🙈

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".

Freso: me either :D

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"

oh this.

Although it seems we're mostly still on "Making contribution easier for new contributors"

Okay. Using "Topic: Triaging tickets" for the stream for now.

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...

CatQuest: theres an ordered list of topics in https://docs.google.com/document/d/1MdK9y1fSa5A...

yes.

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.

what I wish someone would do is put those that are done in the rigt time bracket

rdswift: I tried to address that with comments at https://wiki.musicbrainz.org/Development/Summer...

Remember that new users don't have the same long-erm, big picture view of the projects.

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 :)

s/new users/new contributors/

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

alastairp: EXACTLY! Need to develop that into the process somehow.

guilty

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

he tells me to create a ticket if i report a thing :D

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

our jira has a "sign in with github" button too

!m yvanzo

You're doing good work, yvanzo!

+1 Thanks outsidecontext

BUT!

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

does the pull request merge button on LB still squash commits?

need to check the default but i enabled other options some time ago.

https://chris.beams.io/posts/git-commit/ is a great primer for good commit message writing :)

yes, the default is squash but we can change it if we want.

props for yvanzo to be just a floating head in the dark. good effect!

looks like default now appears to be merge, which I'm in favour of

Works esp. well combined with https://www.freshconsulting.com/atomic-commits/ (which indiscriminate commit squashing is counter to) :)

it seems to be user specific? its squash for me

tests are another can of worms...

I find it harder to write tests than the actual code changes.

But the tests are very valuable during the development.

indeed +1

imo, twitter isn't a very good medium for that due to how ephemeral it is

And some of us "old farts" do do social media in general. 😉

*don't do*

Can you capture the brainzbot notices about merged PRs and the just delete the minor / non-newsworthy items?

Or capture the closed tickets?

re this, i think doing zoom meetings for otherthings than just summits might be ok?

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

+1

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

just one carn of worms more...

:(

https://skribbl.io/?b4xrXuhgeWSQ <--

or wait

I made freso host now. everything ok?

Yes

i'll need to make a room and stuff

!m team

You're doing good work, team!

I'll paste the right one once i fix it

ruaok: it's a good indicator that it's time to stop for today ;)

suggestion for custom words?

heyy

[listenbrainz-server] 14MonkeyDo opened pull request #1661 (03master…monkey-catch-getUserListenCount-errors): Catch potential errors when calling getUserListenCount https://github.com/metabrainz/listenbrainz-serv...

That's the issue you reported CatQuest ^

monkey: wich one :D

oh oh that

cool

Freso: think we're done if you want to close for the day, thanks! :)

\o

Freso: nice flag :)

Oh are we playing scribble?

reosarevok: Done. Thanks. :)

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!)

sure would like to join tomorrow

cool!

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

I agree. I'll note that on the repository README.