Development IRC Meeting 11 January 2023

Place

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.

Time

11 January 2023, 15:00 UTC Time and Date.com converter for various local times

Agenda

Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
Announcements
Update from the Release manager (23.05)
Updates from the Release Maintainers
Updates from the QA team
Status of roadmap projects
Actions from last meeting
- tuxayo: Open tickets on KTD for the basic stuff needed to easily work on the non-root user.
  - Done
- tuxayo: Call for a volunteer on mailing lists to open the bidding for KohaCon24 and confirm the task list for that.
  - Done
- tcohen: To schedule/call a "CSRF day" to work on related patches together (previously deferred until after the 22.11 release).
- tcohen: To draft proposal for master→main change and draft of action list (previously deferred until after the 22.11 release).
- oleonard ashimema: Draft in the developer handbook how to form our modals. With template of a simple case and a case with form inside. Update: focus is currently on staff interface redesign changes, see the draft style guide: https://annuel.framapad.org/p/koha-styleguide-draft (previously deferred until after the 22.11 release).
General development discussion (trends, ideas, ...)
- Use of Gitea: We use Gitea for git.koha-community.org. Gitea was "forked" and is now Forgejo - see the links update and related links (sounds eerily familiar 8-(.. ). The community needs to look at what to do next, such as whether to continue to use Gitea, update to Forgejo, do something else.... (David Nind)
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).)
ACK pre vs post processing for background jobs
- Bug 32573 - background_jobs_worker.pl should ACK a message before it forks and runs the job suggests we should ACK of STOMP messages before we begin processing which would avoid the issue 30 minute time issue among other problems. It appears that the STOMP documentation and the RabbitMQ documentation do not agree. We should have a vote if needed.
Set time of next meeting

Apologies

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

...

Minutes

Next meeting

Development_IRC_meeting_25_January_2023