Development IRC meeting 22 April 2020

=== 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 ===
* 22 April 2020, 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 (20.05)
* Updates from the Release Maintainers
* Updates from the QA team
* General development discussion (trends, ideas, ...)
** A new holds table: an approach from Theke to merge reserves and old_reserves link
*** Thinking about this table from scratch, what would be ideal. Generate views for backwards compatibility (reports mostly)
*** If we agree on this, we could use the same approach for other tables that could have new name and keep the names on the views.
*** Questions that need peer thinking:
**** Can we avoid the unwritten coding guideline that states that columns that have FK should be named as their FK? (e.g. can we use patron_id and pickup_library_id instead of borrowernumber and branchcode) Please? Same applies to biblionumber, itemnumber, itemtype...
**** What do we think of using DB triggers for things like C4::Reserves::_FixPriority?
**** Some attribute names on the /holds route are not following the latest discussions, notably: suspended_until should be suspended_until_date, hold_date could be placing_date. Can we consider our API still beta, and go on and fix this remaining bits?
** Release notes for bugs: Please add a release note once your bugs are pushed. This helps the documentation team, but will also make it easier for the Release Manager when preparing the release notes as well. Should this be mandatory and be part of the coding guidelines? An option maybe to add or update it once a bug has passed QA, if it isn't added then the Release Manager won't push the change until this is done? (David Nind)
* Review of coding guidelines
** Terminology: staff client vs staff intranet vs staff interface vs intranet - At the documentation meeting on 9 January 2020 (search for staff to see discussion, starts about 14:26:37) it was agreed to standardise on staff interface so that we are consistent across the manual. See Word usage - A-Z. (David Nind - apologies for not raising this until now....)
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend but cannot make this meeting
* Aleisha Amohia, Catalyst IT, Wellington
* tuxayo/Victor Grousset, independent community worker, France
** Collision with a videoconference, will be here if the videoconference starts late
* David Nind (will try, but may be asleep)
===Minutes===
* Minutes: http://meetings.koha-community.org/2020/development_irc_meeting_22_april_2020.2020-04-22-16.32.html
* Minutes (text): http://meetings.koha-community.org/2020/development_irc_meeting_22_april_2020.2020-04-22-16.32.txt
* Log: http://meetings.koha-community.org/2020/development_irc_meeting_22_april_2020.2020-04-22-16.32.log.html
===Next meeting===
Development_IRC_meeting_6_May_2020
Category:Developers_IRC_Meetings
Category:Developers_IRC_Meetings_2020