Development IRC meeting 16 November 2022

The #koha IRC channel (IRC server irc.oftc.net).

If you don't have an IRC client you can join the meeting using your web browser.

Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
Announcements
Elections: Roles for 23.05
- Voting on Roles for 23.05
Update from the Release manager (22.11)
Updates from the Release Maintainers
Updates from the QA team
Status of roadmap projects
Actions from last meeting
- davidnind to send an email to the mailing lists on roles for 23.05: sent on 2 November 2022
- davdnind to send a request to the mailing list for someone to update LTS wiki page: apologies - still to do, please allocate action to davidnind
- Deferred until after the 22.11 release:
  - tcohen to schedule/call a "CSRF day" to work on related patches together - deferred until after the 22.11 release
  - tcohen [WAIT until after 21.11 release] to draft proposal for master→main change and draft of action list
  - oleonard ashimema draft in the developer handbook how to form our modals. With template of a simple case and a case with form inside.: focus is currently on staff interface redesign changes, see the draft style guide (WIP)
- Can we claim ES7 support now?

General development discussion (trends, ideas, ...)
- git-bz is stuck on Python 2 which went end of life on January 1st 2020… should we start to consider alternatives? (Deferred from previous meeting(s).)
  - Helsinki university had a Python 3 fork, any news?
- git bz attach -e BUGNUMBER HEAD~X.. (where X = number of patches (davidnind):
  - I've always done it this way when signing off patches as it is what I was told to do
  - There was some discussion on IRC on using -e or not, and obsoleting patches
  - Just seeking guidance on best practice, including whether old patches should be obsoleted (by adding the obsolete tag) to make the bug "cleaner"
  - There maybe a number of scenarios where different options are preferred (for example, sign off vs. passed QA)

Review of coding guidelines
- SQL8 of our coding guidelines state that SQL should not be in .pl, but should be in the module in C4 or Koha. This would mean that SQL in the Koha namespace is allowed and there is no mention of DBIC in the coding guidelines right now. (Deferred from previous meeting(s).)

Please list your name here if you would like to attend but cannot make this meeting:

Contents