Development IRC meeting 30 November 2022

From Koha Wiki
Jump to navigation Jump to search

The meeting was deferred - next meeting 14 December 2022

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

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
    • cait Update wiki page for LTS
    • Deferred until after the 22.11 release:
      • tcohen to schedule/call a "CSRF day" to work on related patches together
      • tcohen 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)
  • General development discussion (trends, ideas, ...)
    • Can we claim ES7 support now? (Deferred from previous meeting)
    • 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).)
  • 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

Retrieved from "https://wiki.koha-community.org/w/index.php?title=Development_IRC_meeting_30_November_2022&oldid=31473"