Development IRC meeting 1 July 2020

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
Update from the Release manager (20.11)
Updates from the Release Maintainers
Updates from the QA team
Actions from last meeting
- cait Organise a testing day for "big stuffs"
- open a bug report to introduce the idea of having a "skeleton" template we could copy for new pages
- ashimema to draft the first 'Accessibility' guideline; All OPAC pages require a single 'maincontent' classed block.
- ashimema write a guideline about mandatory 'maincontent' class (OPAC)
- talljoy Propose a guideline for "inclusive langage" (whitelist/blacklist vs allowlist/denylist)
- tuxayo write a proposal for handing over stable branches

General development discussion (trends, ideas, ...)
- Should we start removing 'indirect object notation' calls and advocate direct notation as our standard for consistency (In preparation for perls disabling it by default: [1]) Bug 25898
- Should we advocate consistency in our kohastructure file regarding `COMMENT="this is a thing"` vs `-- this is a thing` syntax... the former appears in schema classes at dump time.
- Should we require a more recent version of Perl ?
  - Which one?
    - 5.14 because it's the minimum for 'r' regex modifier
    - 5.22 because that's the older Perl version shipped with recommended distributions
    - Are there features between 5.14 and 5.24(Debian 9) worthy of upping the required version?
  - Where should the requirements be written (README, INSTALL, release notes, wiki, manual ...) ?
Review of coding guidelines
Set time of next meeting

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

Contents