Development IRC meeting 7 May 2025

This meeting is held as a video conference using Jitsi:

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 use Hedgedoc to record the meeting minutes, including introductions (formerly #info) and actions (formerly #action) information.

Introductions (the convention is `- <NAME>, <ORG>, <PLACE>`)
Announcements
Update from the Release manager (25.05)
Updates from the Release Maintainers
Updates from the QA team
Status of roadmap projects
- Road map 25.05
Elections for 25.11 roles
Actions from last meeting
- lisette: Add a QA script check for NOTICE1 in the coding guideline.
- oleonard: write developer documentation on the bootstrap 5 upgrade.
- paulderscheid: Reintroduce JS guideline to always use double quotes, update prettier config to enforce for js and vue.
- paulderscheid: file an issue for integrating JS15 into QA scripts
- paulderscheid: to document the new process for chairing and managing meetings on the Wiki
- paulderscheid: write a draft on date/time related naming conventions for discussion.
- arthur: write a QA test for hea system preference changes.

General development discussion (trends, ideas, ...)
Review of coding guidelines
Any other business
- Document the process for reporting and managing security-related bugs (David Nind)
  - Prompted by this chat thread (1 May 2025)
  - We have documentation on coordinated security releases on the release maintenance page
  - We have a link for reporting security bugs on the community website
  - As far as I can tell, we don't have a documented process for dealing with potential security issues - it is mostly "known" to those in the know
  - I'd be happy to work with someone to draft this (process map, and information for each stage of the process), working with those who know the process - from identifying and reporting security issues, fixing the issue, and including in a release
  - (I'm unlikely to be up at 2am to attend the meeting, but you never know 8-))
Set time of next meeting

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

__MINUTES__

__NEXT_MEETING__

Contents