alastairp: Probably the year before last? That was the last year of GCI, where I specifically poked people to tag/label tickets. :x
2021-10-16 28925, 2021
alastairp
can someone help with adding bullet points about this discussion to the minutes
2021-10-16 28927, 2021
alastairp
I'm falling behind
2021-10-16 28947, 2021
Mineo has quit
2021-10-16 28910, 2021
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.
2021-10-16 28957, 2021
Freso
reosarevok: I’m not fully sure what the current topic is 🙈
2021-10-16 28904, 2021
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".
2021-10-16 28916, 2021
CatQuest
Freso: me either :D
2021-10-16 28939, 2021
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"
2021-10-16 28949, 2021
CatQuest
oh this.
2021-10-16 28952, 2021
reosarevok
Although it seems we're mostly still on "Making contribution easier for new contributors"
2021-10-16 28911, 2021
Freso
Okay. Using "Topic: Triaging tickets" for the stream for now.
2021-10-16 28914, 2021
CatQuest
it was the last ticket i linked to you. something related to instrument images
Remember that new users don't have the same long-erm, big picture view of the projects.
2021-10-16 28904, 2021
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 :)
2021-10-16 28909, 2021
rdswift
s/new users/new contributors/
2021-10-16 28912, 2021
alastairp
it turns out that this is a people problem
2021-10-16 28949, 2021
alastairp
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
2021-10-16 28954, 2021
rdswift
alastairp: EXACTLY! Need to develop that into the process somehow.
2021-10-16 28924, 2021
ruaok
guilty
2021-10-16 28951, 2021
alastairp
we use jira as a task dump, not a project management software
2021-10-16 28920, 2021
alastairp
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)
2021-10-16 28930, 2021
alastairp
and we very often work on things that don't have tickets
2021-10-16 28912, 2021
CatQuest
he tells me to create a ticket if i report a thing :D
2021-10-16 28903, 2021
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
2021-10-16 28936, 2021
alastairp
our jira has a "sign in with github" button too
2021-10-16 28950, 2021
alastairp
!m yvanzo
2021-10-16 28950, 2021
BrainzBot
You're doing good work, yvanzo!
2021-10-16 28951, 2021
rdswift
+1 Thanks outsidecontext
2021-10-16 28933, 2021
Freso
BUT!
2021-10-16 28923, 2021
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
2021-10-16 28904, 2021
alastairp
does the pull request merge button on LB still squash commits?
2021-10-16 28946, 2021
lucifer
need to check the default but i enabled other options some time ago.
and PRs that are merged before a releaes is made goes into a "draft" release
2021-10-16 28904, 2021
rdswift
+1
2021-10-16 28956, 2021
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
