Development IRC meeting 15 May 2024

From Koha Wiki
Jump to navigation Jump to search

Place

This meeting is held as a video conference using Jitsi:

Jitsi Meeting Link

  • The meetings are not recorded.
  • You don't have to turn your camera on if you prefer not to be seen; but if you are able to use a microphone it will make things easier.
  • To join the meeting, click on the meeting link.
    • If you are on a desktop computer, it will open in a browser window. There is no need to install anything.
    • To join on a mobile device, you will need to download the Jitsi Meet app (Google Play, Apple Store)
    • Supported browsers | Mobile application
  • Browsers will ask for permission to use video and audio devices: check or review these settings if you have audio or video issues.

We will use the #koha IRC channel (IRC server irc.oftc.net) to record the meeting minutes, including #info and #action information. Feel free to login there too (if you don't have an IRC client you can use your web browser.)

Time

Agenda

  • Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
  • Announcements
    • Foundation vote to be opened asap after this meeting, any last questions do still ask.
  • Update from the Release manager (24.05)
    • String Freeze - 17th May
    • Release - 28th May
  • Updates from the Release Maintainers
  • Updates from the QA team
  • Status of roadmap projects
  • Actions from last meeting
    • Martin to look at resorting the PQA push queue to allow enhancement and new feature to sort in passed order - DONE
    • Everyone please mark your roadmap projects as done if they are - MOSTLY DONE
    • Joubu please send for retrieval of mailing list content - DONE
      • The most comprehensive scripts for extracting mailing list content are in Loïc Dachary's Mailman 2 to Discourse import scripts, rezo-import [currently down but I have a tar archive of my git clone]. Rezo-import includes a very comprehensive mailing list retrieval script. Some settings were hard coded for Loïc's use case. The import into Discourse components need a little updating for more recent changes in settings.yml and better tested settings. Much testing is needed to reduce email mangling from the Ruby email and markdown parsing libraries included in Discourse prone to badly mangle email messages and also direct posts and delete much content on import, especially inline email replies. Finding all the import problem cases is difficult by searching even if they are widely reported to be as much as 30 to 40 percent because searching for the absence of content is difficult. - thd
    • thd to inquire about a test-server for testing email-relay
    • tcohen to write a guideline for the API returns when work has gone through QA - Coding Guidelines - API#SWAGGER4: Controller code .5BDRAFT.5D
    • paulderscheid[m] to add a section about JSDoc to the coding guidelines (JS) - Coding Guidelines#JS15: JSDoc
  • General development discussion (trends, ideas, ...)
    • Do we want to use Carton for packaging our dependencies within Koha rather than pinning ourselves to Debian?
    • How to handle new dependencies in SO/QA and push? see Release management#Dependency changes
    • Discussion about table for deleted authorities (Discussion about coding guideline for the abstract case maybe?) See: Bug 30888
      • Additional notes (tuxayo): Turns out a tombstone table like proposed is a legitimate pattern to manage deletions. Now that it's known how to avoid auto-increment issues with tombstone tables, do they have a significant drawback for our use case?
  • Review of coding guidelines
  • Any other business
  • 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_29_May_2024